TLS-Check | Check – a security/encryption scanner | TLS library

by tls-check Perl Version: v1.0.2-Release License: Non-SPDX

X-Ray Key Features Code Snippets(3)Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | TLS-Check Summary

TLS-Check is a Perl library typically used in Security, TLS applications. TLS-Check has no bugs, it has no vulnerabilities and it has low support. However TLS-Check has a Non-SPDX License. You can download it from GitHub.

Its primary goal is to get key figures about SSL/TLS connections. It can count how many servers support encryption or not, good or weak SSL/TLS-Versions, good or weak cipher suites, how many websites or mailservers are vulnerable to security problems like Heartbleed, how many support IPv6, how many support all recommendations of the BSI or Bettercrypto project and much much more. TLS-Check comes with a lot of checks. But it is very easy to add more tests. It is highly modular and each part of the code can be replaced (e.g. input or output). Development contracted by Chamber of Commerce and Industry of the Stuttgart (Germany) Region and its committee of information technology, information services and telecommunication.

Support

Quality

Security

License

Reuse

Support

TLS-Check has a low active ecosystem.

It has 41 star(s) with 4 fork(s). There are 11 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 1 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of TLS-Check is v1.0.2-Release

Quality

TLS-Check has 0 bugs and 0 code smells.

Security

TLS-Check has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

TLS-Check code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

TLS-Check has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

TLS-Check releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 6 lines of code, 0 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

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 TLS-Check

Get all kandi verified functions for this library.

TLS-Check Key Features

No Key Features are available at this moment for TLS-Check.

TLS-Check Examples and Code Snippets

TLS-Check – Collect information about domains and their servers,Example Usage,More detailed usage

Perl

Lines of Code : 30

License : Non-SPDX (NOASSERTION)

Copy

tls-check.pl
tls-check-parallel.pl
tls-check               (symlink to tls-check-parallel.pl)

> tls-check-parallel.pl --help
usage: tls-check-parallel.pl [-?h] [long options...]
  --configfile STR          Configuration file
  --jobs INT

TLS-Check – Collect information about domains and their servers,Installation,Manual installation on Linux, Solaris, AIX, OS X, …:

Perl

Lines of Code : 10

License : Non-SPDX (NOASSERTION)

Copy

# install perlbrew and the latest stable perl
sudo cpan App::perlbrew        # or, if you trust them: wget -O - https://install.perlbrew.pl | bash
perlbrew init
perlbrew install stable --Doptimize='-O3 -march=native -mtune=native' --switch 

perl -MM

TLS-Check – Collect information about domains and their servers,Installation,Install as packages

Perl

Lines of Code : 5

License : Non-SPDX (NOASSERTION)

Copy

# Fast binary install from packages 
pkg install security/tls-check

# or: flexible individual install from ports
cd /usr/ports/security/tls-check && make install clean

Community Discussions

Trending Discussions on TLS-Check

Istio: Can not access service with gateway over HTTP/HTTPS

Istio mTLS working just between some services even though tls-check prints STATUS OK for everyone

Istio mTLS issue with bookinfo example application

Create separate file for each result

QUESTION

Istio: Can not access service with gateway over HTTP/HTTPS

Asked 2019-Nov-22 at 13:21

Istio: 1.3 (also tried 1.1 before update to 1.3)
K8s: 1.16.2
Cloud provider: DigitalOcean

I have a cluster setup with Istio. I have enabled grafana/kiali and also installed kibana and RabbitMQ management UI and for all of those I have gateways and virtual services configured (all in istio-system namespace) along with HTTPS using SDS and cert-manager and all works fine. It means I can access these resources in the browser over HTTPS with a sub domain.

Then I deployed a microservice (part of a real application) and created Service, VirtualService and Gateway resources for it (for now it is the only one service and gateway except rabbitmq which uses different sub domain and differend port). And it is located in default namespace.

...

ANSWER

Answered 2019-Nov-22 at 13:21

Issue was really simple and silly. I had enabled global.k8sIngress.enabled = true in Istio values.yml. After changing it to false all starts working.

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

QUESTION

Istio mTLS working just between some services even though tls-check prints STATUS OK for everyone

Asked 2019-Sep-15 at 08:35

I am trying to enable mTLS in my mesh that I have already working with istio's sidecars. The problem I have is that I just get working connections up to one point, and then it fails to connect.

This is how the services are set up right now with my failing implementation of mTLS (simplified):

Istio IngressGateway -> NGINX pod -> API Gateway -> Service A -> [ Database ] -> Service B

First thing to note is that I was using a NGINX pod as a load balancer to proxy_pass my requests to my API Gateway or my frontend page. I tried keeping that without the istio IngressGateway but I wasn't able to make it work. Then I tried to use Istio IngressGateway and connect directly to the API Gateway with VirtualService but also fails for me. So I'm leaving it like this for the moment because it was the only way that my request got to the API Gateway successfully.

Another thing to note is that Service A first connects to a Database outside the mesh and then makes a request to Service B which is inside the mesh and with mTLS enabled.

NGINX, API Gateway, Service A and Service B are within the mesh with mTLS enabled and "istioctl authn tls-check" shows that status is OK.

NGINX and API Gateway are in a namespace called "gateway", Database is in "auth" and Service A and Service B are in another one called "api".

Istio IngressGateway is in namespace "istio-system" right now.

So the problem is that everything work if I set STRICT mode to the gateway namespace and PERMISSIVE to api, but once I set STRICT to api, I see the request getting into Service A, but then it fails to send the request to Service B with a 500.

This is the output when it fails that I can see in the istio-proxy container in the Service A pod:

...

ANSWER

Answered 2019-Sep-15 at 08:35

General tips for debugging Istio service mesh:

Check the requirements for services and pods.
Try a similar task to what you are trying to perform from the list of Istio tasks. See if that task works and find the differences with your task.
Follow the instructions in Istio troubleshooting section.

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

QUESTION

Istio mTLS issue with bookinfo example application

Asked 2019-Feb-22 at 01:07

I've installed Istio 1.1 RC on a fresh GKE cluster, using Helm, and enabled mTLS (some options omitted like Grafana and Kiali):

...

ANSWER

Answered 2019-Feb-22 at 01:07

If you are using Istio 1.1 RC, you should be looking at the docs at https://preliminary.istio.io/ instead of https://istio.io/. The preliminary.istio.io site is always the working copy of the docs, corresponding to the next to be Istio release (1.1 currently).

That said, those docs are currently changing a lot day-to-day as they are being cleaned up and corrected during final testing before 1.1 is released, probably in the next couple of weeks.

A possible explanation for the plain text http request returning 200 in you test is that you may be running with permissive mode.

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

QUESTION

Create separate file for each result

Asked 2018-Apr-15 at 17:02

I have a bash script as follows:

...

ANSWER

Answered 2017-Mar-13 at 17:10

I figure form the error that your file contains lines like: www.need_help.com/xyz (with xyz beeing anything, doesn't matter what)

Which means that in the end "$file".txt expends to www.need_help.com/xyz.txt.

So your script tryed to write the output to a file xyz.txt in the folder www.need_help.com and fails because the folder does not exist.

The error message was confusing but accurate: www.need_help.com: No such file or directory

You might want to replace all unwanted characters with something else, as an example only keeping letters numbers and dots

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

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

Vulnerabilities

No vulnerabilities reported

Install TLS-Check

TLS-Check was developed on FreeBSD and OS X, but also works with Linux. It's not tested on Windows. TLS-Check is written in Perl with Moose and uses a lot of CPAN modules.
The most easy way to install TLS-Check is using FreeBSD and install it as port or package. FreeBSD is an UNIX-like operating system similar to Linux, you may read FreeBSD Quickstart Guide for Linux Users as Linux user. You can download installer and virtual machine images.
On Linux, OS X and other operating systems you have to install all dependencies and TLS-Check manually. If you want to use IDN domain names (with characters other then US-ASCII, e.g. äöü.tld), LibIDN is needed. You should install it with the package manager of your OS, e.g. apt-get install libidn11-dev should do this on Debian and Ubuntu. TLS-Check is written in Perl and should work with an old Perl 5.10 and is tested with 5.16 and up.
Perl is usually installed by your OS. Some Linux distributions deliver broken Perl packages and maybe you should install the perl default modules perl-modules. (untested, please report issues here)
If you don't want to (or can't) install all dependencies with the package manager of your OS, it may be better to install your own Perl to avoid conflicts with system packages. The best way is to use perlbrew for this. A latest Perl without ithreads and full optimizations (-O3) is recommended.