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 21:58:01 2005
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: plz suggest security for DLL functions

> Who said anything about Windows?  The concept of a remote procedure call is
> much older than Microsoft, and Sun had RPC to support NFS while Windows was
> still thinking about how to implement TCP....

Quite right .. I was just in the original mindset of the question. I 
also failed to mention that it need not be RPC that's exposed to 
actually make it work .. it could (should) be wrapped via most any tunnel.

 From a practical standpoint, if you're going to "host" the 
SecretSauce.DLL file, you might as well just offer the whole thing as a 
hosted application.

You're still probably best off with a good EULA and legions of lawyers.

~Mike.