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 19:37:25 2005
From: tim-security at sentinelchicken.org (Tim)
Subject: plz suggest security for DLL functions

> Give them a DLL that just tosses an RPC call to a secured server that you
> manage.

And how would your server differentiate between a "good" RPC call and a
"bad" one?

> Another, even better, idea is to give them a click-through EULA that contains
> a line of the form "misusing or reverse-engineerng our usage of jalepenos will
> result in a $MOBY surcharge and/or other legal action...."

Yes, this is probably all you'll be able to do. (Besides code
obfuscation that doesn't make your code significantly harder to "steal".)

It is trivial for any attacker to throw a brick through my window and
steal all of my furniture while I am not home.  Why don't they do it on
a daily basis?  The risk and consequences of getting caught vs. the
rewards of fencing my crappy furniture.

tim