full-disclosure - plz suggest security for DLL functions

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-next>] [day] [month] [year] [list]

Message-ID: <42C596E6.8080401@csuohio.edu>
Date: Fri Jul  1 20:18:34 2005
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: plz suggest security for DLL functions

> Please guide us in making those functions secret or encrypted so that
> others cannt use our functions.

Nope. You can make it marginally more difficult (encrypted) but you
can't "prevent" it entirely .. and the harder you try to make it, the
more fun you make it for crackers to reverse-engineer.

About the best you could do to hide the "super secret sauce" (lol ..
Vladis) is put it on a secure token (eg: SmartCard) and call it from
there. While not foolproof, hardware is [generally] more difficult to hack.

Cheers,

Michael Holstein CISSP GCIA
Cleveland State University