Package Details: sslyze 2.0.6-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: 22
Popularity: 0.862456
First Submitted: 2012-11-09 17:23
Last Updated: 2019-02-13 19:31

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3

goll commented on 2015-02-18 14:30

AsamK, thank you for the updated PKGBUILD! I tweaked it a bit and uploaded it.
I started working on it based on ajs124's comment, so I tried to update the sslyze PKGBUILD and build a nassl package but after a lot of debugging and patching it still wouldn't build and it all got backlogged :/

AsamK commented on 2015-02-18 13:16

Here's a version of the PKGBUILD file that deals better with both architectures:

pkgdesc="Fast and full-featured SSL scanner."
arch=('i686' 'x86_64')

prepare() {
find $srcdir/$pkgname/ -type d -exec chmod 755 {} +

package() {
# Install files in /opt
mkdir -p "$pkgdir/opt/sslyze"
cp -a $srcdir/${pkgname}/. $pkgdir/opt/sslyze
find $pkgdir/opt/sslyze -name '*.py' -print0 | xargs -0 sed -i 's/env python/env python2/g'

# Create an indirect launcher in /usr/bin
mkdir -p "$pkgdir/usr/bin"

cat > "$pkgdir/usr/bin/sslyze" << EOF
cd /opt/sslyze && python2 \$@
chmod 755 "$pkgdir/usr/bin/sslyze"

ajs124 commented on 2015-01-17 12:21

There are quite some things wrong with this pkgbuild.
Why does it download the binaries for both architecture? Pacman can deal with that very nicely, now [1].
And why binaries in the first place? This package isn't called sslyze-bin… I know they use nassl, but that's open-source too, so why not create a package for that and depend on it?
unzip isn't necessary either, bsdtar can deal with zips.


fxbru commented on 2013-10-31 10:48

sslyze uses its own OpenSSL wrapper (nassl), which is in a different, untagged git repo. I don't want to make a tagged PKGBUILD depend on an untagged git repo.

Pre-compiled packages are now different for x86 and x86_64, and due to dropbox url management, distributed on two different urls. I'm giving up.

If someone wants to adopt this package, I suggest to create an sslyze-git one, depending on a to-be created nassl-git one.

azrdev commented on 2013-10-30 20:51

Why via dropbox? Github can zip the whole repo for us, you could as well do a simple git clone.

fxbru commented on 2013-01-28 16:42

Updated to version 0.6.

This tool is now distributed via dropbox (cf.