Bug#849531: [Logwatch-devel] Bug#849531: Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8
> On Jan 14, 2017, at 7:43 AM, Willi Mann <wi...@debian.org> wrote: > > Hi, > > in order to come closer to a fix for this issue, I propose the following > two patches: > > > 0001-Add-outputencoding-parameter.patch > > This patch allows to configure the value for the charset in the > Content-Type line in mail output. This should address Klaus Ethgen's > original concern. Since most people use UTF-8, I left the default at UTF-8. Sounds good. > > 0002-Use-pager-on-stdout-output-to-terminal.patch > > Use pager less if output is on terminal. This should address the issues > associated with escape sequences in logs that may mess with your > terminal. Less seems to be good at filtering these escape sequences. Sounds good, but I’d make it a config switch and leave the default as is. Some “lazy” destro's let cron handle terminal output to mail directly… :/ -Mike > > > Let me know what you think about these patches. > > Willi > > Am 2017-01-01 um 23:01 schrieb Mike Tremaine: >> >>> >>> The fail-safe default before was ISO-8859-1. So I suggest to use it >>> again. >>> >> >> >> If stream converted output it s require please consider making it a >> configurable module in the code base that can be turned on and off and >> modified (the module) as needed. Leave the default as is, that way DESTRO’s >> and users can configure to their liking. But it will work as intended all >> the way back to the stone-age tools that we started this project with. (I’m >> looking at you Solaris 7/8) >> >> >> -Mike >> > > <0001-Add-outputencoding-parameter.patch><0002-Use-pager-on-stdout-output-to-terminal.patch>-- > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. > http://sdm.link/xeonphi___ > Logwatch-devel mailing list > logwatch-de...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/logwatch-devel
Bug#849531: [Logwatch-devel] Bug#849531: Possible security problem, new logwatch sends mails with charset UTF-8
> > The fail-safe default before was ISO-8859-1. So I suggest to use it > again. > If stream converted output it s require please consider making it a configurable module in the code base that can be turned on and off and modified (the module) as needed. Leave the default as is, that way DESTRO’s and users can configure to their liking. But it will work as intended all the way back to the stone-age tools that we started this project with. (I’m looking at you Solaris 7/8) -Mike
Bug#712681: [Logwatch-devel] Fwd: Bug#712681: logwatch: better support for rsyslog
This has been committed to svn -Mike On Jun 18, 2013, at 8:18 AM, Willi Mann wrote: Hi, attached is another contribution by a Debian user, for rsyslogd messages. thanks WM Original Message Subject: Bug#712681: logwatch: better support for rsyslog Resent-Date: Tue, 18 Jun 2013 14:21:01 + Resent-From: Teemu Ikonen tpiko...@gmail.com Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: tpiko...@gmail.com, Willi Mann wi...@debian.org Date: Tue, 18 Jun 2013 16:19:02 +0200 From: Teemu Ikonen tpiko...@gmail.com Reply-To: Teemu Ikonen tpiko...@gmail.com, 712...@bugs.debian.org To: Debian Bug Tracking System sub...@bugs.debian.org Package: logwatch Version: 7.4.0+svn20130529rev144-1 Severity: wishlist Tags: patch The syslogd service in logwatch seems to support some other syslogd than rsyslogd, which is the default in Debian. Attached are a perl script and a service configuration file which match common logfile entries from rsyslogd. Best, Teemu rsyslogd.scriptrsyslogd.conf-- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Logwatch-devel mailing list logwatch-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/logwatch-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#323919: [Logwatch-Devel] Re: Bug#323919: logwatch: script 'http' has incorrect exploit pattern for /../../../
On Mon, 2005-08-22 at 14:28, Willi Mann wrote: forwarded 323919 [EMAIL PROTECTED] tag 323919 + upstream thanks Taco IJsselmuiden [EMAIL PROTECTED] reports: the script 'http' uses '/../../../' as an exploit-pattern. This causes things like '/dat/cjf/00/20/38/13.js' to match (which aren't exploits). attached patch changes this to '/\.\./\.\./\.\./' which fixes this problem. Should the 3 lines below also get fixed? An (avoidable) false positive seems unlikely, but still possible. Commited to CVS [took Willi's advice and fixed the other .. regex's -- Mike Tremaine [EMAIL PROTECTED] http://www.stellarcore.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
