[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#484870: marked as done (partman-crypto: Should warn about weak passphrase before the confirmation of the passphrase)



Your message dated Sat, 7 Jun 2008 09:38:31 +0200
with message-id <200806070938.32351.elendil@planet.nl>
and subject line Re: Bug#484870: partman-crypto: Should warn about weak passphrase before the confirmation of the passphrase
has caused the Debian Bug report #484870,
regarding partman-crypto: Should warn about weak passphrase before the confirmation of the passphrase
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 owner@bugs.debian.org
immediately.)


-- 
484870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484870
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: partman-crypto
Severity: wishlist

When the user chooses a weak passphrase, (s)he is warned about this but only
after confirming the passphrase.

It could be more logical to warn about too short passphrase before the
passphrase confirmation.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
On Saturday 07 June 2008, Christian Perrier wrote:
> When the user chooses a weak passphrase, (s)he is warned about this but
> only after confirming the passphrase.
>
> It could be more logical to warn about too short passphrase before the
> passphrase confirmation.

It cannot because the two questions are essentially asked at the same time 
(as can be seen in the graphical frontend). Therefore closing your 
request.

Cheers,
FJP


--- End Message ---

Reply to: