Package Details: sslyze 2.0.1-1

Git Clone URL: (read-only)
Package Base: sslyze
Description: Fast and full-featured SSL scanner.
Upstream URL:
Licenses: AGPL3
Submitter: fxbru
Maintainer: goll (Bevan)
Last Packager: Bevan
Votes: 20
Popularity: 0.009265
First Submitted: 2012-11-09 17:23
Last Updated: 2018-09-25 16:43

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

1 2 3 Next › Last »

ahinrichs commented on 2018-08-27 08:50

Just recognized: It was pure luck, I stumbled on this three hours after 2.0.0 was released

ahinrichs commented on 2018-08-27 08:43

Upstream 2.0.0 works for me (PKGBUILD patch here )

Bevan commented on 2018-08-13 14:41

Seems like sslyze / nassl is not yet compatible with Python 3.7:

I guess there is not much we can do here but wait…

Cyber_STX commented on 2018-08-13 14:35


Package cannot be installed properly.

Here is the error:

""" Could not find a version that satisfies the requirement nassl<1.2.0,>=1.1.0 (from -r /home/s7x_dcase/.cache/yay/sslyze/pkg/sslyze/opt/sslyze/requirements.txt (line 1)) (from versions: 0.13.4.win32, 0.13.1, 0.13.2, 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.14.0, 0.14.1, 0.14.2, 0.15.0, 0.15.1, 0.16.0, 0.16.1, 0.16.2, 0.16.3, 0.17.0, 1.0.1, 1.0.2, 1.0.3) No matching distribution found for nassl<1.2.0,>=1.1.0 (from -r /home/s7x_dcase/.cache/yay/sslyze/pkg/sslyze/opt/sslyze/requirements.txt (line 1)) """

goll commented on 2016-03-09 13:14

@sja1440: That's strange, here is how the permissions should look like:

$ namei -om /opt/sslyze/
f: /opt/sslyze/
drwxr-xr-x root root /
drwxr-xr-x root root opt
drwxr-xr-x root root sslyze
-rwxr-xr-x root root

Everybody has read and execute permissions by default. How did you install the package? You should use an AUR helper (

sja1440 commented on 2016-03-09 12:39

After installation of sslyze 0.13.4-1 I had issues with the permissions of the installed files under /opt. Only root had read or execute access.

I had to fix these manually, in order to run sslze.

Many thanks

fabianz commented on 2016-03-05 19:23

@goll: As you elaborate, this package is using pip to install nassl, therefore it is actually packaging binaries compiled by upstream. See nassl repository, especially the bin directory.

Symlinking /opt/sslyze/ to /usr/bin/sslyze works fine for me (see sslyze-git PKGBUILD), apparently no need to package in standard paths here. The advantage clearly is getting rid of an unneeded indirection.

goll commented on 2016-03-05 18:38

@fabianz: The launcher is still here because pip installs nassl under ./lib and I think it's best it stays in a non-standard path such as /opt. I don't see what advantage would be gained by using a symlink.

The last version that had upstream binaries was 0.12.
The package is using upstream release tarballs.

fabianz commented on 2016-03-05 18:24

The indirect launcher is not needed anymore, as was merged upstream.
Also, I want to humbly ask you to consider modifying this PKGBUILD for a full source build (using upstream release tarballs or git tag checkouts) instead of repackaging upstream binaries (working build code is in sslyze-git package). Otherwise, I want to suggest that this package should be renamed to sslyze-bin, and a proper sslyze package be created.

goll commented on 2016-03-04 06:59

@hardfalcon: Arch doesn't use sh by default, it's a symlink to bash:

$ ls -l /usr/bin/sh
lrwxrwxrwx 1 root root 4 Nov 23 21:20 /usr/bin/sh -> bash