OpenWall kernel 2.2.16 patch example
Hi has anyone got a small example of applying the openwall patch to kernel 2.2.16. SuSE 6.4 eg. do you apply the diff files individually. Thanks in advance Steven Thompson
Hi has anyone got a small example of applying the openwall patch to kernel 2.2.16. SuSE 6.4 eg. do you apply the diff files individually. as far as i remember there is only one diff file and i patch with
cd /usr/src patch -p0 </tmp/linux-2.2.16.ow.patch (can't remember the exact file name) maybe it's also started from /usr/src/linux .... Markus -- _____________________________ Markus Gaugusch ICQ 11374583 markus@gaugusch.dhs.org 160
-----BEGIN PGP SIGNED MESSAGE----- I did that succesfully. Try to unpack the archive. From the archive take linux-2.2.16-ow1.diff and apply patch -p0 <linux-2.2.16-ow1.diff - --- Bogdan Zapca System Administrator SC EcoSoft SA Internet Service Provider 1-7 Deva st, Cluj-Napoca, Romania Tel: +40 64 199696 PGP: http://www.itotal.ro/lupe@admin2.ecosoft.ro.pgp http://www.ecosoft.ro On Thu, 24 Aug 2000, Steven Thompson wrote:
Hi has anyone got a small example of applying the openwall patch to kernel 2.2.16. SuSE 6.4 eg. do you apply the diff files individually.
Thanks in advance
Steven Thompson
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
-----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQCVAwUBOaUFHdPv6ylvTc6pAQF+QgP+IXRMPY0HB/ucuQfUQDIHkP2qfd+u/gaH NQolyUAkeZik7tEvNC5LG/gl3s8B7e2Yd1Rry/RAYXGJwxPXjvjVh21Q+bjZsnrm a8CltK+IpdDBJ28svnoNU959XBp/8AMRPMDTOXaXohiPJoQE3MZF5GfhXnS3GH+k KsFgrTC90Ak= =1HRd -----END PGP SIGNATURE-----
Hi, we have a problem with qmail. I know it's not directly a security issue but it's a problem with spam attacks, so it's not really OT I think. The problem: A spammer uses random generated addresses at one of our domains. Lot's of the spam mails get rejected (invalid addresses etc.), and a bounce is sent to the random address at our hosts. QMail smtp accepts this mail, finds out that the receipient does not exists, and generates a bounce for that bounce (new mail generated). This bounce bounces too, and a mail is sent to postmaster. Now we got around 7200 Mails[bounces]/hour, resulting in 7200 bounces of bounces plus 7200 triple bounces (to local postmaster). The server cannot send so many mails, and in the queue there are currently around 50K mails, getting more and more. It's a pitty that qmail-smtpd accepts a mail if the target domain is in rcpthosts without checking virtualdomains, and thus a lot of bounces become generated. Now I spool all unknown addresses to a trash file. This is a lot faster than bouncing of course, and now the queue gets smaller, and the mailserver is working (slow, but working). Does anybody have an idea how to handle such problems? oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
participants (4)
-
Bogdan Zapca
-
Markus Gaugusch
-
Steffen Dettmer
-
Steven Thompson