Date: Tue, 30 Jan 2007 06:54:20 GMT From: MORISHIMA Akitoshi<ohm@nanatsumori.net> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/108541: gnupg2 --no-secmem-warning option does not work Message-ID: <200701300654.l0U6sKpD078880@www.freebsd.org> Resent-Message-ID: <200701300700.l0U70aQF036268@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 108541 >Category: ports >Synopsis: gnupg2 --no-secmem-warning option does not work >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jan 30 07:00:35 GMT 2007 >Closed-Date: >Last-Modified: >Originator: MORISHIMA Akitoshi >Release: 6-STABLE >Organization: >Environment: FreeBSD tioga.nanatsumori.net 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Thu Oct 5 08:27:01 JST 2006 root@tioga.nanatsumori.net:/usr/obj/usr/src/sys/TIOGA i386 >Description: The GCRY_SECMEM_FLAG_NO_WARNING and GCRY_SECMEM_FLAG_SUSPEND_WARNING macro defined in secmem.h has been fixed in libgcrypt CVS tree(rev 1014), but not in 1.2 release yet. As a result, the option --no-secmem-warning of gnupg 2 does not work (if not suid root) and cause programs that use gnupg to produce garbled encrypted file. >How-To-Repeat: >Fix: tentatively introduce the fix as patch. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701300654.l0U6sKpD078880>