Bug 222910
| Summary: | security/sslscan: Add openssl-unsafe option | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Bernard Spil <brnrd> | ||||
| Component: | Individual Port(s) | Assignee: | Gavin Atkinson <gavin> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | Flags: | bugzilla:
maintainer-feedback?
(gavin) |
||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
A commit references this bug: Author: brnrd Date: Sun Nov 5 21:14:59 UTC 2017 New revision: 453562 URL: https://svnweb.freebsd.org/changeset/ports/453562 Log: security/sslscan: Switch to openssl-unsafe - Use new security/openssl-unsafe port for scanning - amd64 only PR: 222910 Approved by: maintainer time-out Changes: head/security/sslscan/Makefile |
Created attachment 187056 [details] svn diff for security/sslscan Hi Gavin, Earlier today I committed security/openssl-unsafe and sslscan was a nice small candidate to see if I could make that work. When UNSAFESSL is enabled, you get an ssl library with 179 ciphers enabled, and support for SSLv2, SSLv3 etc. This is why I changed the all-target so it doesn't display the warning. Cheers, Bernard.