Package Details: sslyze 5.1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: sslyze
Description: Fast and full-featured SSL scanner.
Upstream URL:
Licenses: AGPL3
Submitter: fxbru
Maintainer: goll (Bevan)
Last Packager: Bevan
Votes: 25
Popularity: 0.010451
First Submitted: 2012-11-09 17:23 (UTC)
Last Updated: 2023-04-06 16:50 (UTC)

Latest Comments

1 2 3 4 Next › Last »

s3lph commented on 2021-12-13 12:21 (UTC)

The same game all over again for Python 3.10: nassl (a dependency of sslyze) is not yet available for 3.10. Tracked upstream here:

Bevan commented on 2020-12-02 17:40 (UTC) (edited on 2021-01-19 20:28 (UTC) by Bevan)

[Update] sslyze now is Python 3.9 compatible, so the following comment is obsolete.

Python 3.9 hit the Arch repositories and sslyze (or at least nassl which is a dependency) is not yet compatible with that. There is a version of Python 3.8 in AUR but unless there is strong demand, personally I'd rather just wait for an update of sslyze.

Bevan commented on 2020-01-26 12:35 (UTC)

@jhu: sslyze is not yet compatible with Python 3.8, see

I guess the hope is that this is solved timely. If not, the package needs to be changed to use python37 from AUR.

jhu commented on 2020-01-25 07:53 (UTC)

The package does not run and cannot be built anymore:

==> Starting package()...
Processing /tmp/trizen-jhu/sslyze/src/sslyze-2.1.4
ERROR: Could not find a version that satisfies the requirement nassl<2.3.0,>=2.2.0 (from sslyze==2.1.4) (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)
ERROR: No matching distribution found for nassl<2.3.0,>=2.2.0 (from sslyze==2.1.4)
==> ERROR: A failure occurred in package().
:: Unable to build sslyze - makepkg exited with code: 4

surrealistic commented on 2019-06-17 16:44 (UTC)

Thank you so much @Bevan!

Thanks to your answer I could see that my system was running pip2 by default, I just changed it and I could update sslyze.

Bevan commented on 2019-06-16 08:26 (UTC) (edited on 2019-06-16 08:26 (UTC) by Bevan)

Could you try building the package without yay (as described on

If that does not work, please post the output of

  • /usr/bin/pip --version
  • head -n1 /usr/bin/pip
  • pip list --user

Btw: I just updated the package to 2.1.3.

surrealistic commented on 2019-06-15 23:22 (UTC) (edited on 2019-06-15 23:23 (UTC) by surrealistic)

Hi @Bevan! Thank you for your answer. I haven't change my python configuration and if I remember well Arch runs Python 3 by default, I've checked the commands you said in case that any software did the change:

  • which python:


  • pacman -Qo $(which python):

    /usr/bin/python is owned by python 3.7.3-1

  • python --version:

    Python 3.7.3

Bevan commented on 2019-06-15 17:00 (UTC)

surrealistic: On first glance, this looks to me like is executed by python 2 instead of python 3 (there indeed the open() function had no encoding keyword). Do you have configured your system somehow that python 2 is the default?

If nothing comes to your mind, could you please run the following three commands and post their output here?

  • which python
  • pacman -Qo $(which python)
  • python --version

surrealistic commented on 2019-06-15 14:11 (UTC) (edited on 2019-06-15 14:14 (UTC) by surrealistic)


I'm having an issue while updating sslyze for some days. I saw the new update is available with yay and I'm trying to update it but every time I try to upload it, it throw the next error message:

ERROR: Complete output from command python egg_info:
ERROR: Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/pip-req-build-Bq5MvW/", line 51, in <module>
  File "/tmp/pip-req-build-Bq5MvW/", line 26, in get_long_description
    with open(path.join(root_path, ''), encoding='utf-8') as f:
TypeError: 'encoding' is an invalid keyword argument for this function
ERROR: Command "python egg_info" failed with error code 1 in /tmp/pip-req-build-Bq5MvW/
==> ERROR: A failure occurred in package().
Error making: sslyze

Bevan commented on 2019-02-13 19:31 (UTC)

@Cyber_STX: Should be fixed now.