ports/108541: gnupg2 --no-secmem-warning option does not work

[MORISHIMA Akitoshi]

>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 at 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: