Your message dated Wed, 5 Mar 2014 12:53:36 -0600
with message-id <[email protected]>
and subject line 
has caused the Debian Bug report #740875,
regarding libpam-barada: When configuring a user with a PIN that starts with 
'0', the saved PIN omits the initial '0'
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.)


-- 
740875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740875
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam-barada
Version: 0.5-1+b1
Severity: important


% barada-add {user} 01234

Expected:
/etc/barada.d/{user}/pin = 01234

Observed:
/etc/barada.d/{user}/pin = 1234


-- System Information:
Debian Release: 6.0.9
  APT prefers oldstable-proposed-updates
  APT policy: (980, 'oldstable-proposed-updates'), (900, 'oldstable'), (105, 
'proposed-updates'), (102, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-barada depends on:
ii  libboost-filesystem1. 1.42.0-4           filesystem operations (portable pa
ii  libboost-system1.42.0 1.42.0-4           Operating system (e.g. diagnostics
ii  libc6                 2.13-38+deb7u1     Embedded GNU C Library: Shared lib
ii  libgcc1               1:4.7.2-5          GCC support library
ii  libpam0g              1.1.1-6.1+squeeze1 Pluggable Authentication Modules l
ii  libssl0.9.8           0.9.8o-4squeeze14  SSL shared libraries
ii  libstdc++6            4.7.2-5            GNU Standard C++ Library v3

libpam-barada recommends no packages.

libpam-barada suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
The two strings 01234 and 1234 are functionally equivalent because apparently 
the application converts the PIN parameter to UINT32 before using. 

--- End Message ---

Reply via email to