DevGex Search

This article provides a detailed overview of various methods to obtain the SHA1 fingerprint of signing certificates in Android development, focusing on Eclipse export wizard, command-line keytool utility, and Gradle signingReport command. It distinguishes between debug and production certificates, offers complete code examples, and guides developers through OAuth 2.0 client registration.

This article provides an in-depth analysis of common issues when setting the trustStore path in Java SSL connections, particularly those caused by typographical errors. Through practical code examples, it demonstrates how to correctly use the System.setProperty method and -D command-line parameters to configure the trust store. Drawing on reference cases, the article also discusses considerations for certificate setup in different environments (e.g., Jenkins) and offers comprehensive solutions and debugging techniques.

This paper provides an in-depth exploration of network binding configuration for embedded Tomcat servers in Spring Boot applications. Addressing the common developer scenario where services are only accessible via localhost but not through other IP addresses, it systematically analyzes the root causes and presents two effective solutions: configuring the server.address property in application.properties files, and programmatic configuration through the EmbeddedServletContainerCustomizer interface. The article explains the implementation principles, applicable scenarios, and considerations for each method, comparing the advantages and disadvantages of different configuration approaches to help developers choose the most suitable network binding strategy based on actual requirements.

This article explores technical solutions for automatically executing scripts after Docker container startup, with a focus on initializing Elasticsearch with the Search Guard plugin. By analyzing Dockerfile ENTRYPOINT mechanisms, process dependency management strategies, and container lifecycle in Kubernetes environments, it proposes a solution based on overriding entrypoint scripts. The article details how to create custom startup scripts that run initialization tasks after ensuring main services (e.g., Elasticsearch) are operational, and discusses alternative approaches for multi-process container management.

This article provides an in-depth analysis of server name resolution mechanisms in SSL/TLS certificates, focusing on the requirements specified in RFC 6125 and RFC 2818 for hostname verification. By comparing the different behaviors of browsers and Java implementations, it explains why Java strictly relies on Subject Alternative Names (SAN) extensions. Detailed methods for adding SAN extensions using keytool and OpenSSL are presented, including configurations for IP addresses and DNS names, along with practical solutions for resolving Java certificate validation failures.

This technical article provides an in-depth analysis of port usage in Apache Cassandra database systems. Based on official documentation and community best practices, it systematically explains the mechanisms of core ports including JMX monitoring port (7199), inter-node communication ports (7000/7001), and client API ports (9160/9042). The article details the impact of TLS encryption on port selection, compares changes across different versions, and offers practical configuration recommendations and security considerations to help developers properly understand and configure Cassandra networking environments.

This article comprehensively examines the common error "No subject alternative names matching IP address ... found" encountered in Java applications when establishing SSL/TLS connections with self-signed certificates. It begins by analyzing the root cause of the exception: the absence of matching Subject Alternative Names (SAN) for the target IP address in the certificate. By comparing the certificate validation mechanisms between web browsers and the Java Virtual Machine (JVM), it explains why the same certificate works in browsers but fails in Java. The core section presents two primary solutions: modifying the certificate generation process to include the IP address as an IPAddress-type SAN, and bypassing strict hostname verification through a custom HostnameVerifier. The article also discusses the security implications and applicable scenarios of these methods, providing detailed code examples and configuration steps to help developers fundamentally resolve IP address validation issues.

This article provides a comprehensive exploration of the technical process for generating APK files from Android App Bundles (AAB), with a focus on command-line operations using the bundletool utility. It covers the architectural differences between AAB and APK, downloading and configuring bundletool, commands for generating debug and release APKs, methods for extracting universal APKs, and steps for direct device installation. Through in-depth analysis of bundletool's working principles and parameter configurations, it offers developers a complete solution for APK generation from AAB.

This technical paper provides an in-depth examination of different keystore types within the Java security framework. Through detailed analysis of mainstream formats including JKS, PKCS12, PKCS11, and BKS, it elucidates their respective advantages and limitations in cross-platform compatibility, key management, and certificate storage. Special focus is given to the functional evolution of PKCS12 before and after Java 8, offering professional guidance for keystore selection in practical development projects.

This article provides an in-depth analysis of various certificate file formats generated by OpenSSL, including core concepts such as PEM, CRT, KEY, and PKCS12. Through comparative analysis of file structure differences, it elaborates on public-private key encryption principles and certificate signing mechanisms, while offering a complete operational guide from self-signed certificate generation to JKS keystore conversion. With specific command examples, the article helps developers accurately identify different file formats and master essential SSL/TLS certificate management skills.

This article provides a comprehensive guide on identifying the keystore used to sign an Android application, covering methods such as extracting certificate fingerprints with keytool, using Gradle signing reports, and handling Play App Signing scenarios. It explains the principles of certificate matching and step-by-step procedures to ensure secure app updates, along with best practices for key management and troubleshooting common issues.

This article delves into the core differences and applications of cacerts and keystore in Java security. cacerts serves as a truststore, used to verify certificates of remote servers or clients, ensuring the trustworthiness of communication parties; while keystore acts as a keystore, storing local private keys and certificates for proving identity to others. Through practical examples of SSL/TLS connections, the article details their distinct roles in client and server authentication, supplemented with additional technical insights to help developers correctly configure secure communication in Java distributed systems.

This paper provides a comprehensive technical analysis of the 'Keystore was tampered with, or password was incorrect' error encountered when using Java keytool. It examines the root causes, default keystore locations, password verification mechanisms, and presents multiple solutions including deleting default keystore files and creating new keystores. Through detailed command-line examples and code demonstrations, the article offers complete troubleshooting guidance for developers, comparing the differences between -genkey and -genkeypair commands.

This article provides an in-depth exploration of securely handling self-signed SSL certificates in large Java applications, focusing on configuration for specific connections rather than global settings. By analyzing the root causes of SSL handshake exceptions, it presents a customized solution based on SSLSocketFactory, detailing key technical aspects such as keystore creation, TrustManager configuration, and SSLContext initialization. The article compares the advantages and disadvantages of various implementation approaches, emphasizing security assurance while minimizing impact on other parts of the application, offering comprehensive practical guidance for developers dealing with third-party self-signed certificates in real-world projects.

This technical paper provides an in-depth exploration of Java Keytool's critical role in Android development, particularly for generating digital signatures required by MapView controls. Starting with installation locations and fundamental concepts, the article systematically covers keystore management, certificate generation, signature verification, and practical implementation through code examples. The content addresses path configuration across Windows and Unix systems, command parameter analysis, and development best practices, offering Android developers a complete technical reference for secure application deployment.

This article provides an in-depth analysis of the root causes of the Java SSLHandshakeException "no cipher suites in common" error, based on the best answer from the Q&A data. It explains the importance of KeyManager during SSLContext initialization, offers complete code examples, and debugging methods. Topics include keystore configuration, cipher suite negotiation mechanisms, common pitfalls, and best practices to help developers resolve SSL/TLS connection issues effectively.

This article provides a detailed exploration of two primary methods for building signed APKs for Flutter applications within the Android Studio environment: using the IDE's graphical interface and command-line tools. It begins by explaining the importance of signed APKs in app distribution, then walks through the step-by-step process of utilizing Android Studio's "Generate Signed Bundle/APK" feature, including creating new signing keys and configuring build variants. Additionally, the article covers alternative approaches via modifying build.gradle files and executing Flutter commands, comparing the scenarios where each method is most effective. Emphasis is placed on key security management and build optimizations to ensure developers can efficiently and securely deploy Flutter apps.

This paper delves into the interaction between custom trust managers and Java's default trust store (cacerts) when using Apache HttpClient for HTTPS connections. By analyzing SSL debug outputs and code examples, it explains why the system still loads the default trust store even after explicitly setting a custom one, and verifies that this does not affect actual trust validation logic. Drawing from the best answer's test application, the article demonstrates how to correctly configure SSL contexts to ensure only specified trust material is used, while providing in-depth insights into related security mechanisms.

This article provides an in-depth analysis of SSL certificate binding mechanisms, explaining how certificates are associated with domain names or IP addresses through the Common Name (CN). Based on a real-world case of LDAP server SSL certificate issues in WebSphere environments, it details the certificate trust problems that arise when multiple physical servers use the same FQDN but different IP addresses. The article covers certificate serial numbers, fingerprint verification mechanisms, and offers solutions such as unified certificate deployment and local DNS overrides, while discussing the rare application scenarios and limitations of IP address-bound certificates.

This article provides an in-depth analysis of the common CertificateException: No name matching error in Java SSL connections, which stems from server certificate hostname mismatches. Starting from the HTTPS hostname verification mechanism, it explains the verification rules for DNS Subject Alternative Names and Common Names as per RFC 2818. Through practical case studies, it contrasts Plesk default certificates with target hostnames and presents three solutions: modifying server certificates, implementing custom HostnameVerifiers, and using trust-all-certificate methods. The article emphasizes security best practices, highlighting appropriate scenarios for temporarily bypassing verification in development environments while warning against such practices in production. Finally, code examples demonstrate proper SSL context and hostname verifier configuration, helping developers fundamentally understand and resolve SSL handshake failures.