Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #184270 > unrolled thread

Password case reversal on logon

Started bytony mollica <tjm3@threedogs.net>
First post2017-07-26 17:50 +0200
Last post2017-07-26 18:40 +0200
Articles 6 — 3 participants

Back to article view | Back to linux.debian.user


Contents

  Password case reversal on logon tony mollica <tjm3@threedogs.net> - 2017-07-26 17:50 +0200
    Re: Password case reversal on logon Brad Rogers <brad@fineby.me.uk> - 2017-07-26 18:10 +0200
      Re: Password case reversal on logon tony mollica <tjm3@threedogs.net> - 2017-07-26 18:30 +0200
        Re: Password case reversal on logon Brad Rogers <brad@fineby.me.uk> - 2017-07-26 21:00 +0200
          Re: Password case reversal on logon tony mollica <tjm3@threedogs.net> - 2017-07-26 23:40 +0200
    Re: Password case reversal on logon Darac Marjal <mailinglist@darac.org.uk> - 2017-07-26 18:40 +0200

#184270 — Password case reversal on logon

Fromtony mollica <tjm3@threedogs.net>
Date2017-07-26 17:50 +0200
SubjectPassword case reversal on logon
Message-ID<u7wJr-2ak-7@gated-at.bofh.it>
Hello.

Can anyone shed some light on why my logon password got it's upper and 
lower case characters reversed?  I needed the caps lock on then use the 
same password with the shift on the correct characters to log on.  I've 
since reset the password successfully and all is fine (so far) but I'd 
like to know what happened.  The only change I made was installing 
winbind, libnss-windbind and libpam-winbind but I don't find anything 
that explains the upper/lower case reversal on password entry.

A normal password change fixed the problem.

thanks,
tony

[toc] | [next] | [standalone]


#184271

FromBrad Rogers <brad@fineby.me.uk>
Date2017-07-26 18:10 +0200
Message-ID<u7x2N-2we-11@gated-at.bofh.it>
In reply to#184270

[Multipart message — attachments visible in raw view] — view raw

On Wed, 26 Jul 2017 08:43:43 -0700
tony mollica <tjm3@threedogs.net> wrote:

Hello tony,

>Can anyone shed some light on why my logon password got it's upper and 
>lower case characters reversed?  I needed the caps lock on then use the 
>same password with the shift on the correct characters to log on

Sounds to me as though you, inadvertently, had Caps Lock on when setting
the password.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
This is the fifty first state of the USA
Heartland - The The

[toc] | [prev] | [next] | [standalone]


#184273

Fromtony mollica <tjm3@threedogs.net>
Date2017-07-26 18:30 +0200
Message-ID<u7xm9-2CU-5@gated-at.bofh.it>
In reply to#184271
I must have done something like that.  I'd like to find out why so it 
doesn't happen again.  I was working in gadmin-samba with some password 
additions yesterday.  That's the only place I can remember that I did 
any passwords entry.



On 07/26/2017 09:02 AM, Brad Rogers wrote:
> On Wed, 26 Jul 2017 08:43:43 -0700
> tony mollica <tjm3@threedogs.net> wrote:
>
> Hello tony,
>
>> Can anyone shed some light on why my logon password got it's upper and
>> lower case characters reversed?  I needed the caps lock on then use the
>> same password with the shift on the correct characters to log on
>
> Sounds to me as though you, inadvertently, had Caps Lock on when setting
> the password.
>

[toc] | [prev] | [next] | [standalone]


#184281

FromBrad Rogers <brad@fineby.me.uk>
Date2017-07-26 21:00 +0200
Message-ID<u7zHk-3ZT-17@gated-at.bofh.it>
In reply to#184273

[Multipart message — attachments visible in raw view] — view raw

On Wed, 26 Jul 2017 09:21:50 -0700
tony mollica <tjm3@threedogs.net> wrote:

Hello tony,

>I must have done something like that.  I'd like to find out why so it 
>doesn't happen again.  

Can be as simple as a finger slipping on to the wrong key.  Here, it may
go unnoticed for some time as my keyboard has no Caps Lock LED on it.  
Thankfully, the login manager I use throws up a warning if Caps Lock is
enabled.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
Go away, come back, go away, come back
Leave Me Alone (I'm Lonely) - P!nk

[toc] | [prev] | [next] | [standalone]


#184288

Fromtony mollica <tjm3@threedogs.net>
Date2017-07-26 23:40 +0200
Message-ID<u7Ccb-5FZ-31@gated-at.bofh.it>
In reply to#184281
Obviously my own doing.

Thanks for all the info.  I'll be a bit more careful with the keyboard.


Tony



On 07/26/2017 11:35 AM, Brad Rogers wrote:
> On Wed, 26 Jul 2017 09:21:50 -0700
> tony mollica <tjm3@threedogs.net> wrote:
>
> Hello tony,
>
>> I must have done something like that.  I'd like to find out why so it
>> doesn't happen again.
>
> Can be as simple as a finger slipping on to the wrong key.  Here, it may
> go unnoticed for some time as my keyboard has no Caps Lock LED on it.
> Thankfully, the login manager I use throws up a warning if Caps Lock is
> enabled.
>

[toc] | [prev] | [next] | [standalone]


#184275

FromDarac Marjal <mailinglist@darac.org.uk>
Date2017-07-26 18:40 +0200
Message-ID<u7xvP-2Ga-5@gated-at.bofh.it>
In reply to#184270

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jul 26, 2017 at 08:43:43AM -0700, tony mollica wrote:
>Hello.
>
>Can anyone shed some light on why my logon password got it's upper and 
>lower case characters reversed?  I needed the caps lock on then use 
>the same password with the shift on the correct characters to log on.  
>I've since reset the password successfully and all is fine (so far) 
>but I'd like to know what happened.  The only change I made was 
>installing winbind, libnss-windbind and libpam-winbind but I don't 
>find anything that explains the upper/lower case reversal on password 
>entry.

In theory, this should not be possible. Debian, by default, uses
"shadow" passwords. That means that, instead of storing your password in
/etc/passwd, an encrypted version is stored in /etc/shadow.

"man shadow" states that the encryption process is detailed in "man
crypt". That, in turn, states "By  taking the lowest 7 bits of each of
the first eight characters of the [user's password], a 56-bit key is
obtained". The lowest 7 bits of each character IS enough to
differentiate between the case of the letters.

So, for this to happen, something would need to read /etc/shadow, crack
your password (which means scanning 2**56 possibilities - that's 7.2×10^16
or 72 million billion possibilities), perform the case change and
re-store it in /etc/shadow. The chance of this happening by accident
(that is, the chance of /etc/shadow being corrupted such that the new
password is A) valid and B) a case-changed version of your old password)
is ridiculously small.

>
>A normal password change fixed the problem.
>
>thanks,
>tony
>

-- 
For more information, please reread.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web