Package Details: sslyze 2.1.3-1

Git Clone URL: https://aur.archlinux.org/sslyze.git (read-only)
Package Base: sslyze
Description: Fast and full-featured SSL scanner.
Upstream URL: https://github.com/nabla-c0d3/sslyze
Licenses: AGPL3
Submitter: fxbru
Maintainer: goll (Bevan)
Last Packager: Bevan
Votes: 22
Popularity: 0.442045
First Submitted: 2012-11-09 17:23
Last Updated: 2019-06-16 08:25

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Bevan commented on 2018-08-13 14:41

Seems like sslyze / nassl is not yet compatible with Python 3.7: https://github.com/nabla-c0d3/sslyze/issues/325

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

Cyber_STX commented on 2018-08-13 14:35

Hi,

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/sslyze_cli.py
f: /opt/sslyze/sslyze_cli.py
drwxr-xr-x root root /
drwxr-xr-x root root opt
drwxr-xr-x root root sslyze
-rwxr-xr-x root root sslyze_cli.py

Everybody has read and execute permissions by default. How did you install the package? You should use an AUR helper (https://wiki.archlinux.org/index.php/AUR_helpers).

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/sslyze_cli.py 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 https://github.com/nabla-c0d3/sslyze/pull/65 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

hardfalcon commented on 2016-03-04 04:43

Would it be possible to replace #!/usr/bin/bash with #!/bin/sh in the PKGBUILD? The indirect launcher script doesn't use anything that a standard POSIX shell doesn't provide, so bash shouldn't be required.

Bevan commented on 2015-11-13 23:05

@luckdragon: Yeah, dissing peoples work that was made available for free and without any warranty surely is the right way to go…
Seriously, nobody wasted two hours of your life but yourself. Nobody forced you to use this PKGBUILD. If you decide to use it do it at your own risk and don't blame people who made it available initially.

That being said: The issue you reported was valid and the PKGBUILD was changed accordingly. Thanks.