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

Date: Fri Jul  1 15:10:04 2005
From: upbupb at gmail.com (upb)
Subject: plz suggest security for DLL functions

Hi.

Try signing the hash of all your function arguments with a private key
and then in the function calculating the hash and verifying the
signature...
The public key could be extracted from the dll or the dll could be
reverse enginereed to remove the checks but this is still a good
method to prevent totally clueless people from using your dll.

btw MS does something like this :)


On 7/1/05, Gaurav Kumar <gkverma@...il.com> wrote:
> friends,
> 
> We are developing a software that makes use of a COM DLL. The whole
> logic lies in the dll. The User Interface is in VC++. DLL exposes
> functions, application calls it and displays result. Now, we found
> that anybody can copy the DLL, register it and make use of those
> functions.
> 
> Please guide us in making those functions secret or encrypted so that
> others cannt use our functions.
> 
> thanks and regards,
> gaurav
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>