ssltest | SSL/TLS cipher testing tool | TLS library

 by   stephenbradshaw Perl Version: Current License: No License

kandi X-RAY | ssltest Summary

kandi X-RAY | ssltest Summary

ssltest is a Perl library typically used in Security, TLS applications. ssltest has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

SSLTest is a command line tool used to test SSL based servers to determine the SSL ciphers and protocols they support. These types of tests are commonly performed during penetration tests and compliance reviews (DSD ISM, PCI-DSS) that include a SSL server in scope. It is a Perl program, that works on Linux, Windows and Mac OS X, and is originally based on Cryptonark by Chris Mahns. It uses OpenSSL to make SSL connections, and test for supported ciphers and protocols.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              ssltest has a low active ecosystem.
              It has 5 star(s) with 1 fork(s). There are 1 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              ssltest has no issues reported. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of ssltest is current.

            kandi-Quality Quality

              ssltest has no bugs reported.

            kandi-Security Security

              ssltest has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              ssltest does not have a standard license declared.
              Check the repository for any license declaration and review the terms closely.
              OutlinedDot
              Without a license, all rights are reserved, and you cannot use the library in your applications.

            kandi-Reuse Reuse

              ssltest releases are not available. You will need to build from source code and install.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ssltest
            Get all kandi verified functions for this library.

            ssltest Key Features

            No Key Features are available at this moment for ssltest.

            ssltest Examples and Code Snippets

            No Code Snippets are available at this moment for ssltest.

            Community Discussions

            QUESTION

            How do I connect Route 53 subdomain to EC2 load balancer? (SSL mismatch issue)
            Asked 2021-Jun-02 at 10:54

            I want to have a subdomain (api.mysite.com) which makes calls to an EC2 classic load balancer (load-balancer-123456789.us-east-2.elb.amazonaws.com). Everything is hosted on AWS, to (theoretically) make it as straightforward as possible.

            I created a domain and subdomain in AWS Route 53, as per the instructions here, and created an "A" record in the subdomain that links to my load balancer as an alias. That works fine, I can make calls to the load balancer through api.mysite.com, as long as I use HTTP.

            But when I try to use HTTPS, I get ERR_SSL_PROTOCOL_ERROR. If I try to open the API in a browser, the security icon says that it's "not secure". I think the problem might be that the certificate is connected to the main domain (mysite.com) instead of the subdomain (api.mysite.com), but I can't figure out how to get it to resolve properly.

            This SSL checking site shows the EC2 server itself (the one that the load balancer points to) and reports "Certificate not valid for domain name". It's an Ubuntu server, though I'm not sure if that should matter.

            ...

            ANSWER

            Answered 2021-Jun-02 at 10:54

            The SSL certificate needs to specify the subdomain as well as the main domain. The easiest way to do this is through AWS's Certificate Manager, by requesting a new certificate.

            Make sure to specify each relevant domain and subdomain in the certificate (in this case, both mysite.com and api.mysite.com.)

            After creating the certificate, go to the Load Balancer, open up the Listeners tab, and select the HTTPS port. Then, change the SSL certificate for that port to the certificate that includes the relevant subdomain. If you use AWS Certificate Manager, it can be selected from the dropdown menu.

            Source https://stackoverflow.com/questions/67801936

            QUESTION

            Adding Cipher suite to TLS1.2 of HttpClient of dotnetcore 3.1
            Asked 2021-Apr-16 at 06:12

            I encounter the folowing exception when connecting to the website of Western digital:

            website of Western digital

            ...

            ANSWER

            Answered 2021-Apr-07 at 13:22

            .NET Core uses the ciphers supported by the native TLS stack, i.e. SChannel. Which ciphers are supported depend on the version of Windows. Which ciphers are supported by your OS (is documented in TLS Cipher Suites in Windows 7. As you can see, none of the ciphers offered by the server are supported by your OS.

            With Firefox or Chrome browser the situation is different. These come with their own stack and are thus not limited on what the OS offers. That's why they work.

            Source https://stackoverflow.com/questions/66976212

            QUESTION

            ZeroSSL Certificate Mismatch
            Asked 2021-Mar-23 at 16:54

            I just downloaded a certificate from ZeroSSL and got it working, but when I try to access the site, Google Chrome prevents me from visiting because of an invalid certificate error. I tried running the SSL Labs server test (https://www.ssllabs.com/ssltest/) on my site, and got that I have a mismatched name in my certificate.

            I'm confused about what the names should be.

            Subject, common names, alternative name, and issuer are all listed as my private IPv4 DNS address, and under the alternative names it says 'MISMATCH'. What are these expected to be? The domain I supplied to ZeroSSL is my correct domain name, so what is causing this mismatch?

            ...

            ANSWER

            Answered 2021-Mar-23 at 16:54

            I found the issue. I'm running an Apache server on an AWS EC2 instance, and the path to the certificate that I specified inside of in my httpd.conf wasn't the path being used -- instead, the path specified as SSLCertificateFile inside of /etc/httpd/conf.d/ssl.conf was being used, which was set to be the certificate of the EC2 instance, not my certificate for my server. Everything is working now.

            Source https://stackoverflow.com/questions/66757509

            QUESTION

            HTTP request fails even if the connection is active
            Asked 2021-Mar-12 at 16:58

            I'm facing a problem with an http request done in HTTP.java.

            On desktop all works fine (that request is not performed because it's necessary only on Android).

            In Android all works without that http request.

            After that that http request is made, all others fail after timeout with UnknownHostException error, as if they no longer have access to the internet connection, even if it is active. Also after minutes and after the onResume all http requests fail. Although the app cannot get an http response, the AdMob ad appears in my App, so I think that probably the connection works (or does the AdMob library cache some ads and show them when needed?).

            Often, in these cases sometimes it works again:

            • uninstalling and reinstalling the App from Android Studio
            • closing the App, waiting some minutes and reopening it
            • clearing App data from the device
            • waiting an undefined amount of time

            After several attempts I discovered that as soon as the problem occurs, almost every time, if I activate the airplane mode and then disable it, the data connection is deactivated and then reactivated, and the App can immediately execute all subsequent http requests without having to do anything else on your device and without even having to reopen the application.

            • tested with wifi on a 1GB fibra network: same error
            • I checked the connection: it is stable, in wifi and also with SIM
            • in the manifest there is the permission for using internet (otherwise it would never have worked)
            • at the same time, the same App on desktop works perfectly and at the best speed, receiving http responses in less than 1 second, so the server isn't the problem
            • I tested also with the url https://www.google.it: same error, the same url is reachable in the device via browser in less than 1 second
            • as in the line .timeout(10000) I'm using a timeout of 10 seconds, the server has timeout set to 60 seconds
            • checked the server SSL "quality" at https://www.ssllabs.com/ssltest: got "A" in "Overall Rating"
            • done the SIM "reboot" directly with a Vodafone operator

            I'm testing on a real device with a flat 4G connection and with wifi, with "NetGuard - no-root firewall" VPN App installed.

            This VPN works very well with all the other apps and probably mine too, but I can't rule out that it's the problem, although I hardly think it is (I use it since years without problems).

            There is something wrong in my code? Or at least, how can I know the exact cause of this error?

            Thanks.

            AndroidLauncher.java:

            ...

            ANSWER

            Answered 2021-Mar-02 at 03:51

            That error maybe relate to VPN connect, please close the application, off VNP if it was connected, re-connect to VPN and restart you application.

            In all case, you must be connect the VPN before open the application.

            Source https://stackoverflow.com/questions/66303303

            QUESTION

            Why is my k8s Nginx ingress controller serving two certificates (one of which is a Kubernetes Fake Certificate)?
            Asked 2021-Feb-04 at 14:48

            We are running a AKS Kubernetes cluster on Azure. I'm using the "NGINX Ingress Controller" and "cert-manager" for routing and certificate generation (through Let's Encrypt). I followed the basic setup advice from the Microsoft documentation: https://docs.microsoft.com/en-us/azure/aks/ingress-tls

            When visiting our page in a web-browser, we notice nothing out of the ordinary at first - HTTPS was working fine. The browser can validate the Let's Encrypt certificate. However, we noticed later on that the ingress controller actually serves two certificates (one of which has a common name: "Kubernetes Ingress Controller Fake Certificate" and an Alternative name: "ingress.local"): https://www.ssllabs.com/ssltest/analyze.html?d=test-aks-ingress.switzerlandnorth.cloudapp.azure.com&hideResults=on

            Long story short - yesterday, I tried everything from re-installing the Nginx-ingress and cert-manager to starting a new Azure Kubernetes Service from scratch, but every time I end up in the same situation.

            I have read many of the discussions from people experiencing similar problems. Typically, they are a bit different though, as they don't actually see a valid certificate at all. I confirmed that we are using the production Let's Encrypt ClusterIssuer:

            ...

            ANSWER

            Answered 2021-Feb-04 at 10:25

            It is expected behavior. By default Ingress controller creates self-signed certificate with CN indicating it's fake one. This is used when a request doesn't match to rules defined in Ingress. So when we access this URL from browser, it returns correct certificate but with openssl s_client without servername field, it doesn't match the rule defined in Ingress and goes to default backend and returns self-signed certificate.

            You can also specify default certificate for Ingress. Refer https://github.com/kubernetes/ingress-nginx/issues/4674 for more details.

            Source https://stackoverflow.com/questions/66041215

            QUESTION

            certbot --nginx generates PR_END_OF_FILE_ERROR
            Asked 2020-Nov-18 at 09:28

            a Ubuntu 16.04.6 LTS VPS running nginx is presently bricked in terms of serving pages through port 443. This happened unexpectedly, I assume when a renewal kicked in automatically.

            Following are twice replicated steps.

            I removed all site definitions in sites-enabled and reduced the server to its simplest expression: one application in http mode only. The output of nginx -T is at bottom. the unencrypted pages serve as expected.

            I then ran sudo certbot --nginx and selected 1 for the only 3rd level domain available to nginx

            ...

            ANSWER

            Answered 2020-Nov-18 at 09:28

            QUESTION

            Supply Let's Encrypt certificate chain to the client on IIS
            Asked 2020-Oct-06 at 16:45

            To the people that close vote this post: it doesn't help if you don't comment why. We're all trying to learn here.

            I want to have wildcard certificates for 2 domains of mine using Let's Encrypt. Here's what I did:

            In Chrome it all works. In Firefox I get the error below:

            So I tested here: https://www.ssllabs.com/ssltest/analyze.html?d=gamegorilla.net

            I also checked this other post.

            There's talk on making sure that "the server supplies a certificate chain to the client, only the domain certificate". I found validating the certificate chain here.

            I then took these steps found here:

            1. Open the Certificates Microsoft Management Console (MMC) snap-in.
            2. On the File menu, click Add/Remove Snap-in.
            3. In the Add or Remove Snap-ins dialog box, click the Certificates snap-in in the Available snap-ins list, click Add, and then click OK.
            4. In the Certificates snap-in dialog box, click Computer account, and then click Next.
            5. In the Select computer dialog box, click Finish.

            I already see "Let's Encrypt Authority X3" in the Intermediate Certification Authorities. So that should already be handling things correctly I'd presume.

            How can I ensure the Let's Encrypt certificate chain is supplied to the client so it works in Firefox too?

            UPDATE 1

            Based on @rfkortekaas' suggestion I used "all binding identifiers" instead of supplying the search pattern. When Win-acme asked Please pick the main host, which will be presented as the subject of the certificate, I selected gamegorilla.net. After this gamegorilla.net now works in Firefox, however, on www.karo-elektrogroothandel.nl I now get an insecure certificate.

            UPDATE 2

            Alright, that seems to fix it. I do see that bindings for smtp/mail (e.g. smtp.gamegorilla.net) are now also added to IIS automatically: Should I leave those or delete those mail+smtp records here?

            Also, the certificate is now [Manual], does that mean I need to renew manually (which woud be weird since nowhere during the certificate creation steps did I see an option for auto-renewal):

            ...

            ANSWER

            Answered 2020-Jun-15 at 14:31

            The issue is that you only generate the certificate for www.gamegorilla.net and not gamegorilla.net if you select all binding identifiers instead of supplying the search pattern I think it should work.

            To also get certificates for other names that are not hosted by IIS you cannot use the import from IIS function. You need to supply them all, starting with the common name.

            After starting wacs select M for a new request and select option 2 for manual input. After that enter the comma separated list with the common name first: gamegorilla.net,www.gamegorilla.net,smtp.gamegorilla.net,karo-elektrogroothandel.nl,www.karo-elektrogroothandel.nl,smtpkaro-elektrogroothandel.nl (without any spaces). Or when you want to generate a wildcard certificate you can use: gamegorilla.net,*.gamegorilla.net,karo-elektrogroothandel.nl,*.karo-elektrogroothandel.nl.

            Please be aware that for generating wildcard certificates you need to be able to use the DNS-01 challenge. The HTTP-01 challange doesn't support wildcard certificates.

            For the certificate renewal you should run wacs --renew from time to time (for example via a schedules task).

            Source https://stackoverflow.com/questions/62345427

            QUESTION

            Ruby openssl SSLContext cipher
            Asked 2020-Sep-03 at 15:02

            I wrote following code in Ruby with the OpenSSL library which fetches the certificate chain from cloudflare.com. But Cloudflare has a hybrid system where old browser receive the RSA cert and the new clients receive the ECDSA cert (see https://www.ssllabs.com/ssltest/analyze.html?d=cloudflare.com&s=104.17.176.85). In my case I want to get the older RSA certificate, that is why I set ctx.ciphers = 'aRSA'. But somehow I always receive the ECDSA certificate. Following command works though openssl s_client -cipher aRSA -connect cloudflare.com:443 -showcerts.

            ...

            ANSWER

            Answered 2020-Sep-03 at 15:02

            TLS 1.3 changes how ciphersuites are defind. From the OpenSSL Wiki:

            The new ciphersuites are defined differently and do not specify the certificate type (e.g. RSA, DSA, ECDSA) or the key exchange mechanism (e.g. DHE or ECHDE). This has implications for ciphersuite configuration.

            In your case, even though you are specifying aRSA, OpenSSL is still including the 1.3 ciphers, which will work with EC certificates.

            I don’t know if it is possible to specify the cipher list to exclude these ciphers (I couldn’t get it to work), but you can simply set the max version to 1.2:

            Source https://stackoverflow.com/questions/63705024

            QUESTION

            Secure websocket connection fails on iOS due to BoringSSL certificate verification failure
            Asked 2020-May-27 at 07:30

            I'm unable to connect to a secure websocket connection due to the following error on iOS (12 & 13).

            It seems there is a failure validating the certificate for the end-point but I can't find a way to determine the reason. I can connect to the websocket end-point from a browser client. I also verified the certificate using https://www.ssllabs.com/ssltest/ and don't see any issues. The SSL certificate is issued from Let's Encrypt.

            Below is the console output I could capture from the device and console app on my mac laptop:

            XCODE DEBUG CONSOLE

            ...

            ANSWER

            Answered 2020-May-02 at 03:03

            I just wrote a class to help with sockets and the new apple TLS restrictions (see my readme). You are most likely misconfiguring your certificates. Along with my helper class that handles the socket, I tried to also layout how to create certificates that will work as of the new iOS TLS restrictions.

            https://github.com/eamonwhiter73/IOSObjCWebSockets

            Source https://stackoverflow.com/questions/61513555

            QUESTION

            Shell script to make site https using certbot and nginx
            Asked 2020-May-27 at 00:46

            I know how to install ssl certificate using command-line. But i need a shell script this time to do this task.

            Generally while doing this manually i first execute the fowllowing:-

            ...

            ANSWER

            Answered 2020-May-27 at 00:46

            Though i am very late here but finally i did as suggested by @JohnHanley in the comments. I went through the documentation and here is what i needed to execute the above mentioned steps in the question by command line.

            Source https://stackoverflow.com/questions/58626546

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install ssltest

            You can download it from GitHub.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/stephenbradshaw/ssltest.git

          • CLI

            gh repo clone stephenbradshaw/ssltest

          • sshUrl

            git@github.com:stephenbradshaw/ssltest.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular TLS Libraries

            mkcert

            by FiloSottile

            v2rayN

            by 2dust

            acme.sh

            by acmesh-official

            nginxconfig.io

            by digitalocean

            v2ray

            by 233boy

            Try Top Libraries by stephenbradshaw

            vulnserver

            by stephenbradshawC

            hlextend

            by stephenbradshawPython

            pentesting_stuff

            by stephenbradshawPython

            breakableflask

            by stephenbradshawPython

            pygdbdis

            by stephenbradshawPython