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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri Jul  1 21:38:52 2005
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: plz suggest security for DLL functions 

On Fri, 01 Jul 2005 14:37:18 EDT, Tim said:
> > 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?

Well - you *do* have some idea of what sort of abuse you're trying to stop, right?

If they're not allowed to call it more than X times/hour, rate limit your RPC
server.  Or apply whatever other checks you want to.

At least you (hopefully) don't have to worry about the user running your
server under a debugging tool to reverse engineer it. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050701/c14e39da/attachment.bin