search for: forkbomb

Everyone, Progress was slow today. I started out well, but then I ran into Documentation.htm. Progress slowed considerably, as I analyzed the document structure. I''m up to /etc/shorewall/hosts Configuration. I hope to finish Documentation.xml by tomorrow evening. Converted documents: 6to4.xml CorpNetwork.xml FAQ.xml Please post feedback, if you see any problems with the converted

...s down to DNS? I blame it on the vague log files ;-) I'm running my server chroot on Gentoo as well (see thread: [icecast] Icecast server YP Woes... take 2). Could this be a Gentoo specific problem? Without changing topic...my question: Can IceCast be built static? -- (o- Paul <snafu@forkbomb.dhs.org> /\ BLOG: http://forkbomb.dhs.org/bs/ v/_ GPG Key: http://forkbomb.dhs.org/bs/snafu.asc "If at first you don't succeed, destroy all evidence that you tried." --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ T...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 three-interface.xml is done. I am completing the cleanups and "look and feel" changes. It will be checked in shortly. - -- "If at first you don''t succeed, destroy all evidence that you tried." Paul <snafu@forkbomb.dhs.org> BLOG: http://forkbomb.dhs.org/bs/ GPG Key: http://forkbomb.dhs.org/bs/snafu.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQE//DSWNQvzkbg+TpsRArn3AJ94PcM0KhddoD3nGmLFOUZ3ibqYygCeLpO2 G2iE122udccBjYZhyOuuU/Y= =Kc/j -----END PGP SIGNATURE-----

Hi again, I was reading from the net http://www.kriptopolis.org/node/4067 about a forkbomb and ran it from a root console in a non-critical machine running CentOS4.4 and the serevr goes down... the command I ran was :(){ :|:& };: Please, does anyone knows how to aboid this on CentOS? regards, Israel

Hello everyone, Assuming this is the right place to post potential bug reports, try this : (Apologies if it's been posted/covered somewhere else, but your lists don't seem to have a search facility...) nmbd had a good go at fork bombing my "server" just now, with a setup as follows : Samba 2.2.0a on Slackware Linux v8.0, linux kernel 2.4.16. i586 with 500ish mb of ram.

Of the remaining HTML files in the Shorewall-docs/ project, the only ones that I want to convert to HTML are: standalone.htm two-interface.htm three-interface.htm Paul -- while file(s) are you working on? -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

On Wed, 23 Oct 2002 08:22:38 -0700 shorewall-devel-request@shorewall.net wrote: > Shorewall-devel -- confirmation of subscription -- request 915994 > > We have received a request from > cpe014500117825.cpe.net.cable.rogers.com for subscription of your > email address, <snafu@forkbomb.dhs.org>, to the > shorewall-devel@shorewall.net mailing list. To confirm the request, > please send a message to shorewall-devel-request@shorewall.net, and > either: > > - maintain the subject line as is (the reply''s additional "Re:" is > ok), > > -...

...onse -> (0) [2004-04-12 18:37:26] EROR yp/yp_submit_url Got a NAK from yp_add(Unknown) (http://dir.xiph.org/cgi-bin/yp-cgi) Is this not a 'curl' libs problem? I'm using 7.11.0 -- "If at first you don't succeed, destroy all evidence that you tried." Paul <snafu@forkbomb.dhs.org> BLOG: http://forkbomb.dhs.org/bs/ GPG Key: http://forkbomb.dhs.org/bs/snafu.asc --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing o...

oddsock wrote: >can you verfiy that you can connect to dir.xiph.org from the machine >running icecast ? i.e. wget http://dir.xiph.org/cgi-bin/yp-cgi On my end I got communications of sorts via wget, but that's about it. >anything else special network-wise in your setup ? As far as my network setup it too is a standard setup, 1 Dlink NAT/firewall, cable modem and . As for the

Hi: I'dve thought that there'd be no need for the libs in the chroot, as icecast starts up first, then chroots. Even if this isn't strictly the case, wouldn't icecast crash if it couldn't pull in the relevant code? This doesn't seem to be happening, at least in this case. Geoff. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

I'm having a problem getting my stream published on dir.xiph.org using icecast2/ices2-beta4 The output in my log is: [snip] DBUG geturl/curl_print_header_result SID -> () DBUG geturl/curl_print_header_result Message -> () DBUG geturl/curl_print_header_result Touch Freq -> (0) DBUG geturl/curl_print_header_result Response -> (0) EROR yp/yp_submit_url Got a NAK from yp_add(Unknown)

Tom, I was upgrading a remote firewall, when upon restart, shorewall found a rule with a wrong zone and decided to not continue and stop itself. The problem now, is I cannot access that firewall over ssh anymore. One suggestion would be to instead of "shorewall stop" to have a basic emergency rule with only ACCEPT:info all all tcp ssh rule instead with DROP all policy. Shorewall could

At 01:42 PM 4/12/2004, you wrote: >D. Willock wrote: > >>What I saw of the output of tcpdump didn't show any mention of the yp >>url. The communications seem to run only between the client and the >>server and nowhere else. This is the dump I got: > >If I may jump in here since my previous thread/problem went unsolved ;-) > >I've got nothing for a dump

can you provide a dump of the conversation between your icecast server and the YP ? Use something like tcpdump or ethereal...In the dump, look for the URL call to yp-cgi and post what is being sent... oddsock <p>What I saw of the output of tcpdump didn't show any mention of the yp url. The communications seem to run only between the client and the server and nowhere else. This is the

Hi! It seems /bin/sh in 4.8-STABLE has problem with SIGCHLD processing. In short, it often fails to process it correctly, zombies float around, jobs are not marked as finished in jobtab[] that fills memory and takes much CPU to be processed. Run this one-liner using /bin/sh and see hundreds of zombies: #!/bin/sh while :; do : & done A kernel will halt this as soon as it reaches limits and

...ause it requires hacking an expectation file for each target, which must be done with the gui. 5) Intermediate output placement can not be controlled. 6) The output logs are not as clean. 7) Right now we are dependent on a specific version of QMTest. 8) It has several bugs that can cause it to forkbomb when tools are not built correctly. I propose that we switch over to using dejagnu by default, renaming check-dejagnu to check, and deprecate QMTest. We can either remove qmtest for this release or keep it until 1.5. I'd appreciate your opinion or any feedback you may have. Thanks! -Tanya

Topic: strace casues hardlock. no kernel panic. userland tool Category: kernel Program: strace Affects: FreeBSD releases 5.x and later. problem: When a normal user (or root user) users strace on certain binarys, the system will hardlock up, with no kernel panic. (numlock doesnt turn on and off, no ssh or console access). Im using strace from the ports

...nNUDsghArJWfHPigekbtfOBZGWq//V5FYLs8l17DIKzPVKqlZVoXK73/3RN+uUyomfLmP/Ww+4UObkQImC5LwtiziCIrDp5R+cjBF+Jb tzEZ0k36N3dRUAEnter passphrase for key '/home/$user/.ssh/id_dsa': $user@$host's password: I think the key do not work at all. :-/ Regards, -- | kickino.org || logic-bomb.org || forkbomb.ch || herder-gymnasium.de | <Slant> dpkg -i kernel-image-2.4.18_kami.1.0_i386.deb <Sam|foo> ok <Slant> ok, reboot. <Sam|foo> brb * Slant nods. <-- Sam|foo has quit (QUIT: User exited) <FlipTopBox> sucka. he's doomed, isn't he.

...n user tries to connect to the specified host. Host foo ProxyJump foo # or more generic Host * ProxyJump %h I have reproduced this on 7.9p1 on Suse Linux Enterprise Server 15 and on 7.4p1 on Debian Stretch (currently oldstable). Depending on limits configured on the server, this, like any other forkbomb, can cause all kinds of fun behavior on the local server. Perhaps the client could check for this edge case and avoid trying to make an impossible proxy connection. -- You are receiving this mail because: You are watching the assignee of the bug.

I''m beginning to think again about what will be different in 2.0. Here are some thoughts. a) User-defined actions will be emphasized. - A library of actions will be available with names such as: AcceptSSH AcceptDNS DropWindows (drops all SMB noise) DropBroadcasts (Silently drop all Broadcast traffic) ... The possibilities are nearly endless but should