Bug#407068: marked as done (ITP: libpam-rsa -- PAM module for local authentication with RSA keypairs)
Your message dated Tue, 23 Jan 2007 23:34:29 +0000
with message-id <E1H9V9p-0007bz-RI@ries.debian.org>
and subject line Bug#407068: fixed in libpam-rsa 0.8-9-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wnpp
Severity: wishlist
* Package name : libpam-rsa
* Version : 0.8-9
* Upstream Author : Vesa-Matti Kari <pamrsa-bugs@laamanaama.helsinki.fi>
* URL : http://www.helsinki.fi/~vmkari/pamrsa/
* License : LGPL
* Description : (follows)
The libpam-rsa PAM module is for local PAM authentication with RSA
keypairs. pam_rsa will look for user-associated public RSA keys in the
local system and will encrypt a message using the user's public RSA key.
Then it will look for a private key in a portable media like a USB
memory stick and will try to decode the message. This implements a poor
man's smartcard-like functionality.
End of description. My work on this package has already begun (I have a
working, non-Policy compliant package). I've been using this module for
a while in my own laptop (no problems, well integrated code), and as
soon as I solve Linda/Lintian warnings I'll contact an sponsor.
As always, any help and comments will be greatly appreciated. Thank you,
WNPP-people.
Jose
Note: I'm aware of the hyphen in the version number.
--
José M. Parrella -> Debian Sid, k2.6.18
Escuela de Ingenieria Electrica
Universidad Central de Venezuela -> ucvlug.info
--- End Message ---
--- Begin Message ---
Source: libpam-rsa
Source-Version: 0.8-9-1
We believe that the bug you reported is fixed in the latest version of
libpam-rsa, which is due to be installed in the Debian FTP archive:
libpam-rsa_0.8-9-1.diff.gz
to pool/main/libp/libpam-rsa/libpam-rsa_0.8-9-1.diff.gz
libpam-rsa_0.8-9-1.dsc
to pool/main/libp/libpam-rsa/libpam-rsa_0.8-9-1.dsc
libpam-rsa_0.8-9-1_i386.deb
to pool/main/libp/libpam-rsa/libpam-rsa_0.8-9-1_i386.deb
libpam-rsa_0.8-9.orig.tar.gz
to pool/main/libp/libpam-rsa/libpam-rsa_0.8-9.orig.tar.gz
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 407068@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jose Parrella <joseparrella@cantv.net> (supplier of updated libpam-rsa 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 ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 15 Jan 2007 15:26:19 -0400
Source: libpam-rsa
Binary: libpam-rsa
Architecture: source i386
Version: 0.8-9-1
Distribution: unstable
Urgency: low
Maintainer: Jose Parrella <joseparrella@cantv.net>
Changed-By: Jose Parrella <joseparrella@cantv.net>
Description:
libpam-rsa - PAM module for local authentication with RSA keypairs
Closes: 407068
Changes:
libpam-rsa (0.8-9-1) unstable; urgency=low
.
* Initial release (Closes: #407068)
Files:
5b1c7eb86efb57bf6fe99e9a05c6c671 627 admin extra libpam-rsa_0.8-9-1.dsc
323e0d8be3bb1217790af7e2b75e3944 253068 admin extra libpam-rsa_0.8-9.orig.tar.gz
7e12a85cf905f0150652b59e4753887e 7235 admin extra libpam-rsa_0.8-9-1.diff.gz
1444ac98dafa08c63942befc7c7ed6c3 31258 admin extra libpam-rsa_0.8-9-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFFsyyCipBneRiAKDwRAhEkAJwIiu3xNn+8yiHR+7otnhSXvNJ9DQCfU6Mx
WjyY7NcXlG6/nmnSzWkBTjk=
=hm8r
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: