cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

sync MESSAGE with reality

Browse Source 
from Antoine Jacoutot <ajacoutot at lphp.org>
maintainer timeout
This commit is contained in:
sturm 2005-10-29 14:59:08 +00:00
parent e544fde653
commit 4a1aae3a0f
2 changed files with 7 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
security/gnupg/Makefile
View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.52 2005/05/17 15:08:34 martin Exp $ # $OpenBSD: Makefile,v 1.53 2005/10/29 14:59:08 sturm Exp $
COMMENT= "GNU privacy guard - a free PGP replacement" COMMENT= "GNU privacy guard - a free PGP replacement"
DISTNAME= gnupg-1.4.1 DISTNAME= gnupg-1.4.1
PKGNAME= ${DISTNAME}p0 PKGNAME= ${DISTNAME}p1
CATEGORIES= security CATEGORIES= security
MASTER_SITES= ftp://ftp.gnupg.org/gcrypt/gnupg/ \ MASTER_SITES= ftp://ftp.gnupg.org/gcrypt/gnupg/ \

19
security/gnupg/pkg/MESSAGE
View File

@ -1,16 +1,7 @@
The manpage of GnuPG mentions the need for memory page locking. The manpage of GnuPG mentions the need for memory page locking.
In fact this is not needed as OpenBSD supports swap file encryption. In fact this is not needed as OpenBSD enables swap file encryption
by default.
You can
- enable memory page locking for non-root users if you set the setuid
bit for the gpg binary (most likely 'chmod u+s ${PREFIX}/bin/gpg').
- enable swap encryption by setting vm.swapencrypt.enable=1 with
sysctl(8). This is recommended.
In the latter case you may want to get rid of the misleading 'using
insecure memory' warning. Just put 'no-secmem-warning' to your
~/.gnupg/gpg.conf file or use gpg with the --no-secmem-warning switch.
However you might want to get rid of the misleading 'using insecure
memory' warning. Just put 'no-secmem-warning' into your ~/.gnupg/gpg.conf
file or use gpg with the --no-secmem-warning switch.