| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Marked broken on 12+ over 2 years ago without anyone fixing it
Upstream project seems inactive
PR: 254938
Reported by: daniel.engberg.lists@pyret.net
|
|
|
|
| |
Reported by: lwhsu
|
| |
|
|
|
|
| |
Notes:
svn path=/head/; revision=516744
|
|
|
|
|
|
|
|
| |
Reported by: pkg-fallout
MFH: 2019Q2
Notes:
svn path=/head/; revision=498244
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have some hacks in the ports tree to detect or to unconditionally disable
IDEA crypto support. These hacks existed because OpenSSL in FreeBSD 9.3 and
earlier was shipped without IDEA support by default but we were allowed to
enable it via WITH_IDEA src.conf(5) option.
https://www.freebsd.org/cgi/man.cgi?query=src.conf&manpath=FreeBSD+9.3-RELEASE
Therefore, we had to implement some hacks to support three different cases,
i.e., a) 9.3 and earlier without IDEA crypto (default), b) 9.3 and earlier
with IDEA crypto (via WITH_IDEA src.conf option), and c) 10.0 and later with
unconditional IDEA support. Now we can safely remove them because 9.3 and
earlier is no longer supported.
PR: 218233
Exp-Run by: antoine
Approved by: antoine (portmgr)
Notes:
svn path=/head/; revision=437668
|
|
|
|
|
|
|
|
|
|
|
|
| |
The FreeBSD 10+ check for IDEA was hardcoded against the base library.
While all ports SSL library options likely have idea.h, extending the
check generically enables the port to build correctly on all platforms
when SSL_DEFAULT is set to something other than "base".
Approved by: SSL blanket
Notes:
svn path=/head/; revision=421784
|
|
|
|
|
|
|
|
| |
- Correct master site
- Adopt port
Notes:
svn path=/head/; revision=361122
|
|
|
|
| |
Notes:
svn path=/head/; revision=361012
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was an errant "-" in a CFLAGS definition that got interpreted as
in input from stdin during one of the conftests. This caused netpgp to
fail configuration for months on DragonFly and presumably any modern
GCC. I'm surprised clang tolerated it.
pointyhat to: bapt@
Notes:
svn path=/head/; revision=346723
|
|
|
|
| |
Notes:
svn path=/head/; revision=336648
|
|
|
|
|
|
|
| |
Fix build on 10 and HEAD
Notes:
svn path=/head/; revision=336149
|
|
|
|
|
|
|
| |
security)
Notes:
svn path=/head/; revision=327769
|
|
|
|
| |
Notes:
svn path=/head/; revision=309732
|
|
|
|
|
|
|
| |
Feature safe: yes
Notes:
svn path=/head/; revision=308003
|
|
|
|
|
|
|
|
|
| |
Handbook)
Approved by: portmgr@ (implicit)
Notes:
svn path=/head/; revision=301960
|
|
|
|
|
|
|
| |
Reported by: QAT
Notes:
svn path=/head/; revision=264255
|
|
|
|
| |
Notes:
svn path=/head/; revision=264252
|
|
|
|
|
|
|
|
|
|
|
| |
- add USE_OPENSSL macros
PR: ports/149812
Submitted by: Julien Laffaye <kimelto _at_ gmail.com>
Approved by: jadawin (co-mentor)
Notes:
svn path=/head/; revision=259644
|
|
|
|
|
|
|
| |
Approved by: jadawin@ (co-mentor)
Notes:
svn path=/head/; revision=258396
|
|
|
|
|
|
|
|
| |
PR: 147433
Submitted by: Bapt <baptiste.daroussin@gmail.com> (maintainer)
Notes:
svn path=/head/; revision=255834
|
|
|
|
|
|
|
|
|
| |
PR: ports/145191
Submitted by: Bapt <baptiste.daroussin@gmail.com> (maintainer)
Approved by: miwi (co-mentor)
Notes:
svn path=/head/; revision=252084
|
|
|
|
|
|
|
|
|
| |
PR: 144210
Submitted by: Bapt <baptiste.daroussin@gmail.com> (maintainer)
Feature safe: yes
Notes:
svn path=/head/; revision=250356
|
|
|
|
|
|
|
|
| |
PR: ports/138395
Submitted by: Bapt <baptiste.daroussin gmail.com>
Notes:
svn path=/head/; revision=240606
|
|
signatures attached to files were signed by a given user identifier.
netpgp can also encrypt files using the public or private keys of
users and, in the same manner, decrypt files which were encrypted.
The netpgp utility can also be used to generate a new key-pair for a
user. This key is in two parts, the public key (which can be used by
other people) and a private key.
In addition to these primary uses, the third way of using netpgp is to
maintain keyrings. Keyrings are collections of public keys belonging
to other users. By using other means of identification, it is
possible to establish the bona fides of other users. Once trust has
been established, the public key of the other user will be signed.
The other user's public key can be added to our keyring. The other
user will add our public key to their keyring.
WWW: http://www.NetBSD.org/
PR: ports/134997
Submitted by: bapt <baptiste.daroussin at gmail.com>
Notes:
svn path=/head/; revision=235963
|