full-disclosure - M$ - so what should they do?

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]

From: aditya.deshmukh at online.gateway.technolabs.net (Aditya, ALD [ Aditya Lalit Deshmukh ])
Subject: M$ - so what should they do?

>The real reason for the registry is to make it difficult to copy an
> application from one machine to another. In other words, it's a copy
> proctection scheme. Remember in the days of Win 3.1, you could do that? It
> all broke in Win95 with the registry.

now the key to transfering the application from one machine to another is also trasnfering the associated registy entries and values to the new machine also 

-aditya
??????????????????????????????????????????????????????
?b???v?"?.axZ?x??????Gb?*'??.?[kj???.?j)m???r??