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.541010
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

Bevan commented on 2015-08-09 18:52

I disown this package so that goll can take it back. So if you are not goll: Please do not take this package. Thanks :)

Bevan commented on 2015-07-08 12:22

I just migrated this package to AUR4. If the original maintainer (goll) wants it back I will transfer the ownership back of course. Otherwise I will keep maintaining it.

fabianz commented on 2015-03-24 23:34

I just uploaded the package sslyze-git to AUR which manages to compile nassl from source. Since the current releases (v0.10) date back to Sep. 2014, I preferred to create a git package instead.
Since nassl has to be identical in version to sslyze and states "Do NOT use for anything serious" on its github page, I refrained from making it a separate package for now.
You should nonetheless be able to gain some hints on how to compile nassl from my PKGBUILD in order to use the source release tarballs instead of the binary releases for this package.

fabianz commented on 2015-03-24 22:33

I just uploaded the package sslyze-git to AUR which manages to compile nassl from source. Since the current releases (v0.10) date back to Sep. 2014, I prefered creating a git package instead.
Since nassl seems to be only used for sslyze and states "Do NOT use for anything serious" on the github page, I refrained from making it a separate package.
You should nonetheless be able to gain some hints on how to compile nassl from my PKGBUILD in order to use the source release tarballs instead of the binary releases for this package.

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:

pkgname='sslyze'
pkgver=0.10
pkgrel=1
pkgdesc="Fast and full-featured SSL scanner."
arch=('i686' 'x86_64')
url=('https://github.com/nabla-c0d3/sslyze')
license=('GPLv2')
depends=('python2')
source_i686=("https://github.com/nabla-c0d3/sslyze/releases/download/release-${pkgver}/${pkgname}-${pkgver/./_}-linux32.zip")
source_x86_64=("https://github.com/nabla-c0d3/sslyze/releases/download/release-${pkgver}/${pkgname}-${pkgver/./_}-linux64.zip")
sha1sums_i686=('d9ed490681d44c4c9d69a03ecb0bf4283c0de7c1')
sha1sums_x86_64=('5b17aee4802f3c4bbc74b8e10f131522a4dbb320')

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
#!/bin/bash
cd /opt/sslyze && python2 sslyze.py \$@
EOF
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.

[1]: http://allanmcrae.com/2014/12/pacman-4-2-released/

fxbru commented on 2013-10-31 10:48

@azrdev:
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. http://nabla-c0d3.blogspot.fr/2013/01/sslyze-v06.html)