Hi!
On Tue, Oct 25, 2005 at 04:40:53AM -0700, Steve Langasek wrote:
Sorry, what problem are you trying to solve?
Excuse me for the confusion. I talk here about another
issue, similar to what we have in bug #333138.
Now I tend to agree with Robert that this is a bug,
because fact of
On Fri, Oct 21, 2005 at 01:42:05AM +0300, Alexander Gattin wrote:
On Wed, Oct 19, 2005 at 05:36:29PM -0700, Steve Langasek wrote:
Yes, I see this (pre-0.80 version):
1. fprintf(stderr, %s, prompt);
2. tcsetattr(STDIN_FILENO, TCSAFLUSH, ...);
3. read(STDIN_FILENO, ...);
4.
Hi!
On Wed, Oct 19, 2005 at 05:36:29PM -0700, Steve Langasek wrote:
Yes, I see this (pre-0.80 version):
1. fprintf(stderr, %s, prompt);
2. tcsetattr(STDIN_FILENO, TCSAFLUSH, ...);
3. read(STDIN_FILENO, ...);
4. tcsetattr(STDIN_FILENO, TCSADRAIN, ...);
OK. Even having 2, 1, 3, 4
On Wed, Oct 19, 2005 at 02:08:09AM +0300, Alexander Gattin wrote:
On Sun, Oct 16, 2005 at 03:37:57PM -0700, Steve Langasek wrote:
Anyway, this seems to be fixed upstream in Linux-PAM 0.80,
They took getpass() considered obsolete message to
heart and implemented their own getpass()? :)
Hi!
On Sun, Oct 16, 2005 at 03:37:57PM -0700, Steve Langasek wrote:
Anyway, this seems to be fixed upstream in Linux-PAM 0.80,
They took getpass() considered obsolete message to
heart and implemented their own getpass()? :) (shit, I
don't like all these re-inventions of wheel...)
As a consequence, my first reaction is saying that this bug does not
pertain to passws. Am I right?
Yes, unless there's a bug in passwd inside #ifndef USE_PAM
code too. ;)
Well, given that Debian's passwd uses PAM, the bug would then become a
bug in upstream passwd but not in Debian
reassign 182602 libpam0g
thanks
Quoting Christian Perrier ([EMAIL PROTECTED]):
As a consequence, my first reaction is saying that this bug does not
pertain to passws. Am I right?
Yes, unless there's a bug in passwd inside #ifndef USE_PAM
code too. ;)
Well, given that Debian's
Hi!
On Sun, Oct 16, 2005 at 12:05:18AM -0700, Steve Langasek wrote:
On Sat, Oct 15, 2005 at 06:34:03PM +0200, Christian Perrier wrote:
found that the prompting for a new password is not done by passwd
itself but by the pam_unix PAM module
pam_unix -- misc_conv -- IMHO getpass()
oops, I forgot to mention,
On Mon, Oct 17, 2005 at 01:22:00AM +0300, Alexander Gattin wrote:
Hi!
On Sun, Oct 16, 2005 at 12:05:18AM -0700, Steve Langasek wrote:
On Sat, Oct 15, 2005 at 06:34:03PM +0200, Christian Perrier wrote:
found that the prompting for a new password is not done by
On Mon, Oct 17, 2005 at 01:22:00AM +0300, Alexander Gattin wrote:
On Sun, Oct 16, 2005 at 12:05:18AM -0700, Steve Langasek wrote:
On Sat, Oct 15, 2005 at 06:34:03PM +0200, Christian Perrier wrote:
found that the prompting for a new password is not done by passwd
itself but by the
Hi!
On Sat, Oct 15, 2005 at 06:34:03PM +0200, Christian Perrier wrote:
While looking at bug #182606 and then to passwd sources, I finally
found that the prompting for a new password is not done by passwd
itself but by the pam_unix PAM module
As a consequence, my first reaction is saying
11 matches
Mail list logo
