full-disclosure - simple ltrace trick, was Re: blackfist(posted on request from prophet)

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

Message-ID: <20020919172943.A5002@hamsec.aurora.sfo.interquest.net>
From: silvio at big.net.au (silvio@....net.au)
Subject: simple ltrace trick, was Re: blackfist(posted on request from prophet)

On Thu, Sep 19, 2002 at 10:43:35PM +0200, Mikhail Iakovlev wrote:
> Suggestion to owners of mailing list:
> 
> 
> Configure your sendmail/qmail/whatever to block gobbles@* as blacklisted.
> Lets see how this turkey will fly than. I would love to see this guy 
> having registered every day new email addy just to post it here, subscribe 
> etc. 
> 
> That's where fun comes:)
> 1 line and restart of mail daemon for making him wasting his time, what 
> more precious can we do?:)
> 
> Shame this list is not on my server, otherwise I would play with this guy 
> the way he would love:)
> 
> Mik-

rememeber there exist multiple gobbles@, and i dont think blacklisting
a single name is such a good idea - ever go on irc and see *.au banned etc.
Is that annoying do you think?

ok.. back to ltrace. a simple way of detecting if a specific call is
being traced.. just

do something like this -->

((*(unsigned char *)write) == 0xcc)

umm.. why did i post 0xc3 before?  i think i am on drugs today. 

--
Silvio