Your message dated Wed, 06 Aug 2008 12:17:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#489835: fixed in seccure 0.3-2
has caused the Debian Bug report #489835,
regarding seccure-* FATAL: Cannot obtain memory lock
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
489835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489835
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: seccure
Version: 0.3-1
Severity: important
I have a couple of files encrypted and whe I need to decrypt the programs file
misserably...
FATAL: Cannot obtain memory lock: Cannot allocate memory.
That seems strange any ideas?
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages seccure depends on:
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr
seccure recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: seccure
Source-Version: 0.3-2
We believe that the bug you reported is fixed in the latest version of
seccure, which is due to be installed in the Debian FTP archive:
seccure_0.3-2.diff.gz
to pool/main/s/seccure/seccure_0.3-2.diff.gz
seccure_0.3-2.dsc
to pool/main/s/seccure/seccure_0.3-2.dsc
seccure_0.3-2_i386.deb
to pool/main/s/seccure/seccure_0.3-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
James Westby <[EMAIL PROTECTED]> (supplier of updated seccure package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 06 Aug 2008 11:33:27 +0100
Source: seccure
Binary: seccure
Architecture: source i386
Version: 0.3-2
Distribution: unstable
Urgency: low
Maintainer: James Westby <[EMAIL PROTECTED]>
Changed-By: James Westby <[EMAIL PROTECTED]>
Description:
seccure - tools for using algorithms based on elliptic curve cryptography (
Closes: 489835
Changes:
seccure (0.3-2) unstable; urgency=low
.
* Make failure to mlock all memory only a warning, and re-enable gcrypt's
memory locking. Changes in pam since etch mean that the kernel's defaults
for memory locking are now respected, and seccure tries to lock more
memory than that, which means that the program can't be started. The patch
is from the upstream author, who considers it a stop-gap, but doesn't
anticipate having a proper fix before lenny. (Closes: #489835)
* Don't ignore "$(MAKE) clean" errors. The normal reason for this is the use
of autotools leading to the makefile not necessarily being present when
the clean target is run, be this package doesn't use autotools, so that
won't happen.
* Add a description to debian/patches/10-man-hyphen.dpatch.
* Update the standards version to 3.8.0 (no changes required).
* Release team: this isn't the diff that I sent you, I apologise. My sponsor
suggested that fixing these small things wouldn't be a problem.
Checksums-Sha1:
33d79ba64142e172579a80a9b88ffbb3d14e78a7 964 seccure_0.3-2.dsc
3f46a1a656b65c0a2160b104db8fe25114f16df0 4379 seccure_0.3-2.diff.gz
b835d24a4c500b6255e0eb1c55c7a99575fdb333 27060 seccure_0.3-2_i386.deb
Checksums-Sha256:
20b3a2997f47d17c5fc982f48aacb7bee0977ffb5208751e08056f9f70fac3b9 964
seccure_0.3-2.dsc
d063f64497294b48d693b00d0126ef287fcc13d9b4c2db24dbd96d3ec56cadb1 4379
seccure_0.3-2.diff.gz
5237e52dff029fbc96cc63c1df969d89dcc0098bd40f703a9b846c1a4291bfd4 27060
seccure_0.3-2_i386.deb
Files:
51b3fd8718547723f0483cbda0ccdf39 964 utils optional seccure_0.3-2.dsc
ba7b58bc4f4874b62426e7d2de7d516b 4379 utils optional seccure_0.3-2.diff.gz
a3a8e5efcc0b0e7a8d73353b285a0399 27060 utils optional seccure_0.3-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkiZlNYACgkQeGfVPHR5Nd1zmQCfUuxCPG8t0G+cEDIeFonzxoso
X4QAn1Y6MbzFh8iqhvsAKqKGOAcfaoFM
=GbbC
-----END PGP SIGNATURE-----
--- End Message ---
