lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba64666b04111605132b8ab2ed@mail.gmail.com>
From: bortvern at gmail.com (Bort Vern)
Subject: AIM saved password storing

This is exactly the kind of shenanigans that worked on old AOL
clients, haven't looked at it in about 5 or so years though.  I
wouldn't be surprised if you couldn't just export the registry for the
AOL client, change the password, then export again and do a diff
between the files to find the encoded password.  However, I wouldn't
install the AOL client long enough to try...


On Mon, 15 Nov 2004 19:00:09 -0500, ntx0f <ntx0f@...euid.com> wrote:
>  
> Anyone ever check out the way AIM stores passwords? The hash is in the
> registry and reusable. I'm not sure there's a good way to save the passwords
> but by copying the hash and making the proper registry keys you can use the
> hash on any other computer. I had some code to do this that would retrieve
> the hash and put it in a registry file or just a text file it could read
> back but I dont feel like looking for it. Nothing too special just figured
> I'd bring it up as I haven't seen this done anywhere. 


-- 
_____________________
Serablue Inc., Nonprofit
http://www.serablue.com


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ