Re: [AMaViS-user] amavisd-new 2.6.x does not run chrooted on *BSD
Henrik K [EMAIL PROTECTED] wrote: On Thu, May 29, 2008 at 08:50:15AM +0300, Tuomo Soini wrote: Mark Martinec wrote: | Indeed, thanks for a bug report, amavisd-new-2.6.0 drops privileges too early. Until I have this fixed, please provide a chroot directory through a command line using option -R, e.g.: | Another problem with 2.6.0 is that it drops privileges too early and can't open pid file in /var/run. Why /var/run? By default it's $MYHOME/amavisd.pid. From securitys point of view, there is no reason to write files as root. Or to even start amavisd as root if you are not chrooting. The directory a process is chrooted to should *never* be writable by the process itself due to security reasons! I suggest changing $MYHOME/amavisd.pid to something like $MYHOME/var/run/amavisd.pid. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] FW: [Clamav-announce] Sourcefi re¹s rejection of unsolicited bid
I am confused, this press release says barracuda networks tried to buy sourcefire, not that sourcefire tried to buy clamav. Anyone know what is going on? Did sourcefire buy clamav or not? -- Michael Scheidell, CTO |SECNAP Network Security Winner 2008 Network Products Guide Hot Companies FreeBSD SpamAssassin Ports maintainer Sourcefire Rejects Unsolicited Acquisition Proposal COLUMBIA, Md.--(BUSINESS WIRE)--May 30, 2008--Open source innovator and SNORT(R) creator, Sourcefire, Inc. (Nasdaq: FIRE), a leader in Enterprise Threat Management, today announced that its Board of Directors has carefully reviewed privately-held Barracuda Networks, Inc.'s unsolicited acquisition proposal and has concluded that the proposal is not in the best interests of Sourcefire and its stockholders. The Board believes that the proposal substantially undervalues Sourcefire. -- Forwarded Message From: Tomasz Kojm [EMAIL PROTECTED] Organization: ClamAV Reply-To: [EMAIL PROTECTED] Date: Fri, 30 May 2008 18:38:59 +0200 To: [EMAIL PROTECTED] Subject: [Clamav-announce] Sourcefire¹s rejection of unsolicited bid Dear ClamAV users, as you may have heard, Sourcefire received an unsolicited offer to acquire the company. This morning Sourcefire announced that our board has rejected that offer. The complete press release is available at: 'http://investor.sourcefire.com/phoenix.zhtml?c=204582p=irol-newsArticleID =1152071' Best regards, -- oo. Tomasz Kojm [EMAIL PROTECTED] (\/)\. http://www.ClamAV.net/gpg/tkojm.gpg \..._ 0DCA5A08407D5288279DB43454822DC8985A444B //\ /\ Fri May 30 18:31:31 CEST 2008 ___ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-announce -- End of Forwarded Message _ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com _ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] FW: [Clamav-announce] Sourcefi re¹s rejection of unsolicited bid
Michael Scheidell wrote: I am confused, this press release says barracuda networks tried to buy sourcefire, not that sourcefire tried to buy clamav. Anyone know what is going on? Did sourcefire buy clamav or not? http://investor.sourcefire.com/phoenix.zhtml?c=204582p=irol-newsArticleID=1041607 cite COLUMBIA, Md.--(BUSINESS WIRE)--Aug. 17, 2007--Open source innovator and SNORT (R) creator, Sourcefire, Inc. (Nasdaq:FIRE), today announced that it has acquired ClamAV(TM), a leading open source gateway anti-virus and anti-malware project. Sourcefire's first acquisition since its Initial Public Offering in March 2007, ClamAV will broaden the company's open source footprint while providing the technology foundation for new products and services that will extend the company's Enterprise Threat Management network security portfolio. /cite - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
[AMaViS-user] banned_namepath_re VS banned_filename_re
I'm doing some file blocking with amavisd and i noticed amavisd 2.6.0 can done file blocking on two different variables: banned_filename_re and banned_namepath_re (yes, use only one at a time, i know) banned_namepath seems to me very complex. banned_filename is not that simple, but at least not as complex as banned_namepath. question being banned_namepath the 'new' way of doing this, is banned_filename scheduled to be removed on future releases, or both ways will continue to exist on amavisd-new ? what are the main advantages of banned_namepath aginst banned_filename .. i couldnt get them ... the only difference i can note is that banned_namepath is pretty much more complex -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email [EMAIL PROTECTED] My SPAMTRAP, do not email it - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
Re: [AMaViS-user] The usual UTF8 content checker Problem
On 5/29/08, Max Ferstl wrote: Der Mailinglist users, due to people violating the rfc concerning 7bit ascii headers, and subjects I got regulary complaints concerning the 8bit header check in amavis. --- snip --- Our content checker found Non-encoded 8-bit data (char E4 hex): X-Spam-Report: --- snip --- I tried google, and searched for a documentation for a clean way to just turn off the 8-bit checking, but I failed. This might possibly be what you are looking for: http://marc.info/?l=amavis-userm=116344627214918 -- Gary V - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
