On Mon, 05 Apr 2004 12:14:28 -0500, I wrote:
> Perhaps you've got me KF'ed only in some newsgroups?

Another possibility, which I think is remote but worth mentioning: your
news server might be filtering me out as spam in the comp.* hierarchy.
They might use different thresholds for alt.* groups. I think some spam
filter engines might consider a username ending in a digit (rob0) as an
indicator of spam. I know many spam warriors are too eager to filter
what others can read. (IMO of course.)
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

Alexander Bartolich wrote :

> IMHO the only working approach is that of debian/apt.
>
> apt-get install some-cracy-package

From a general Linux group I know that "some-cracy-package" is the main
problem about apt-get. If you don't know the exact magic word then your
more or less lost.
--
Thomas O.

This area is designed to become quite warm during normal operation.

/dev/rob0 <rob0@gmx.co.uk> says...

>I thought I was KF'ed because I have on numerous occasions posted
>additions and corrections to your posts, and they have been ignored. I
>recall threads in c.o.l.security which definitely gave me that
>impression; in fact I have said there that you had KF'ed me.

In my opinion, one should post *plonk* when killfiling so that the
killfiled don't have to wonder.


--
Guy Macon, Electronics Engineer & Project Manager for hire.
Remember Doc Brown from the _Back to the Future_ movies? Do you
have an "impossible" engineering project that only someone like
Doc Brown can solve? My resume is at http://www.guymacon.com/

"/dev/rob0" <rob0@gmx.co.uk> wrote:
> All OS's are equally vulnerable to this sort of attack, wherein the
> attacker has been placed in one's Usenet killfile. You must be VERY
> CAREFUL in choosing whom you allow such inside access, because no killfile
> has a very secure lid or seal.
>
> Try it yourself, you'll see. Make another user account, post something
> in alt.test as that user, and then killfile that user. Switch hats to
> be the KF'ed user again, and push open the lid of the KF from the
> inside. Climb out and look around your $HOME. Scary, eh?

I don't understand this are you saying that somebody can hack into your
machine using your killfile? I use slrn at home and to be totally honest
I couldn't plonk someone if I tried. Hearing this makes me a little more
motivated to learn how to use my killfile properly. Anybody explain to me
what this is all about?

Scott Eberl wrote:
> I don't understand this are you saying that somebody can hack into your
> machine using your killfile?

sure, it's easy. the difficult thing is hacking into someone's machine when
they're reading your usenet posts. but this too can be done.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

> Scott Eberl wrote:
>> I don't understand this are you saying that somebody can hack into your
>> machine using your killfile?

That's precisely what I am saying, except I prefer the term "crack" ...
and that it's not really even that. You have been brought into the
victim's system. Try it out! Get yourself some plonks, then just push
open the lid[s] of the killfile[s] from inside.

Simple to do. Of course it's only a user-level exploit. You don't get
shell access directly, except through perhaps changing a victim's
crontab or something like that. You only get root if they're crazy
enough to read Usenet as root.

For your own safety you should only do this when the victim is not
looking. Once long ago (when using Windows actually) it happened to me:
I saw someone coming up out of my killfile. I turned off the power
switch right away. I don't know if he was hurt or not, but it put his
adventure to an immediate stop.

Since then I have been VERY careful about the use of a killfile.

On Mon, 05 Apr 2004 21:41:54 +0000, Joost Kremers wrote:
> sure, it's easy. the difficult thing is hacking into someone's machine
> when they're reading your usenet posts. but this too can be done.

For this I find the hypnotic approach most effective. Get your reader
into a trance and then tell him to "su -c 'rm -rf /'" -- it gets them
every time. Or if you feel creative, have them use any command you
desire. Enjoy.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

Alan Hicks wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>> 2) You're trolling, however. I never considered you a troll, but now I'm
>> wondering.
>
> /dev/rob0 has never to my knowledge, ever, trolled by any definition of
> the term. You owe him an apology.

I was joking. I know he's not a troll.

>
>> 3) I'm never threatened lol. I could care less if you're going to try to
>> come after me. I've got security measures in place, but honestly, if you
>> can get in after I've hardened Slackware, I'll be looking at using
>> FreeBSD instead.
>
> Dude learn to take a joke for what it is, a joke. First of all,
> /dev/rob0's not the kinda guy to hold grudges. Second, even if he was
> he's not the kinda guy to go after some one's $HOME directory. And
> Third, even if he was both of those, he's not the kind of guy to lower
> himself to that level over petty bickering.

I know, which is why that ended with "", which is a wide-mouthed smile.
Learn your emoticons

>
> And btw, FreeBSD is not that much more secure than Slackware, really.
>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQFAcVPPL3KiNGOqr6ERAikwAJ0XWiHE5Iay0mf0qTp1Eu F9EYGL2wCfRy48
> NXUpmxuujkj9v6t6s4DoyrQ=
> =skn7
> -----END PGP SIGNATURE-----

--
Spouse, n.:
Someone who'll stand by you through all the trouble you
wouldn't have had if you'd stayed single.

/dev/rob0 wrote:
> On Mon, 05 Apr 2004 21:41:54 +0000, Joost Kremers wrote:
>> sure, it's easy. the difficult thing is hacking into someone's machine
>> when they're reading your usenet posts. but this too can be done.
>
> For this I find the hypnotic approach most effective. Get your reader
> into a trance and then tell him to "su -c 'rm -rf /'" -- it gets them
> every time. Or if you feel creative, have them use any command you
> desire. Enjoy.

ah, the artistic method. ;-) i use a much cruder method: malicious
headers. (well, not in this post, obviously...)

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

NeoSadist <neosad1st@charter.net> says...
>
>Alan Hicks wrote:
>
>> /dev/rob0 has never to my knowledge, ever, trolled by any definition of
>> the term. You owe him an apology.
>
>I was joking. I know he's not a troll.

I am unsure concerning your comments about me, which is why I didn't
reply. Were they joking as well?


--
Guy Macon, Electronics Engineer & Project Manager for hire.
Remember Doc Brown from the _Back to the Future_ movies? Do you
have an "impossible" engineering project that only someone like
Doc Brown can solve? My resume is at http://www.guymacon.com/

On Mon, 05 Apr 2004 18:34:04 -0500
"/dev/rob0" <rob0@gmx.co.uk> wrote:

> Since then I have been VERY careful about the use of a killfile.
>
> On Mon, 05 Apr 2004 21:41:54 +0000, Joost Kremers wrote:
> > sure, it's easy. the difficult thing is hacking into someone's
> > machine when they're reading your usenet posts. but this too can be
> > done.
>
> For this I find the hypnotic approach most effective. Get your reader
> into a trance and then tell him to "su -c 'rm -rf /'" -- it gets them
> every time. Or if you feel creative, have them use any command you
> desire. Enjoy.


That's exactly why I always don my Al foil cap when I see /dev/rob0 on
the Subject header.

Mike