-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tls grade: cryptcheck.fr or ssllabs ? #10
Comments
I don't think there is a consensus around Qualys SSL labs, it's probably due to the fact that ssllabs is more popular than cryptcheck. SSL Labs really lacks of SSL/TLS good practices, it's just in 2020 that they started giving a lower score for using TLS 1.0 & TLS 1.1: https://blog.qualys.com/ssllabs/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols We shouldn't trust SSL Labs for measuring the quality of the encryption of a Searx instance. aeris himself agree that nobody should use Qualys SSL Labs: https://mastodon.social/@fschaap/5000393 As for the arguments against cryptcheck:
I find this completely normal, the owner of the Searx instance has to correctly configure his website. We shouldn't follow the fallback to IPv4 mechanism. Try to SSH to a domain that have a miss-configuration for its IPv6 record but the IPv4 record is valid, it will just timeout without falling back to IPv4.
I only encountered one, a case where a scan wouldn't finish. If that's becoming more and more frequent, it's better to open an issue marked as a bug. EDIT: I saw a bunch of question mark on searx.space and I think that's what you related to "other cases". |
For some hosts, I think it is a timeout:
For some other hosts, it is the IPv6 configuration problem. Anyway, it seems that if the process stops for some reason, it is not possible to restart even using the Example with search.mdosch.de:
So I end up thinking it is better to run |
Maybe you could use podman instead? This way you don't have to run a docker daemon all the time and you can launch the container with a non-root account: https://github.com/containers/python-podman I was also thinking of running our own cryptcheck on Heroku for example? Maybe the official cryptcheck just have too much load to handle? EDIT: Temporary solution to have full non-root in podman python: containers/python-podman#16 (comment) |
I've tried podman:
A quick and dirty using docker & flask: #!/usr/bin/env python3
import docker
import docker.errors
import json
import logging
from flask import Flask
logger = logging.getLogger('cryptcheck')
PORT = 50000
IMAGE = 'aeris22/cryptcheck:latest'
COMMAND = 'https $HOSTNAME --quiet --json'
app = Flask(__name__)
@app.route('/<hostname>')
def index(hostname):
logging.debug('cryptcheck %s', hostname)
try:
client = docker.from_env()
c = client.containers.run(image=IMAGE,
command=COMMAND.replace('$HOSTNAME', hostname),
auto_remove=True,
network_mode='host')
return c.decode('utf-8')
except docker.errors.ContainerError as e:
return str(e), 500
except Exception as e:
return str(e), 503
def run():
logger.debug('starting webserver on port %s', PORT)
app.run(
port=PORT,
host='127.0.0.1',
threaded=True
)
if __name__ == "__main__":
run() Note:
|
WIP: https://github.com/dalf/cryptcheck-backend (perhaps it is clunky: I've never written Ruby code).
Using this docker image, it is possible to call cryptcheck without the root permission. |
cryptcheck-backend is reliabled since it has been used, so I've merged the PR #15 |
Being the one first criteria to sort the instance list, the tls grade measure has to be reliable, otherwise the order will be "blinking". Unfortunately, this is not the case right now using cryptcheck:
It is possible to run cryptcheck locally using docker and / or send pull request to the git repository.
But, it seems there is a consensus around ssllab, at least in the current instance list.
Here some information ssllab:
Extract :
The text was updated successfully, but these errors were encountered: