Bug 222910 - security/sslscan: Add openssl-unsafe option
Summary: security/sslscan: Add openssl-unsafe option
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Gavin Atkinson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-10 19:07 UTC by Bernard Spil
Modified: 2017-11-05 21:18 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (gavin)

Attachments
svn diff for security/sslscan (780 bytes, patch)
2017-10-10 19:07 UTC, Bernard Spil 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bernard Spil freebsd_committer freebsd_triage 2017-10-10 19:07:25 UTC 
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.
Comment 1 commit-hook freebsd_committer freebsd_triage 2017-11-05 21:15:44 UTC 
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