From owner-freebsd-questions@freebsd.org Sat Dec 31 02:01:00 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52626C97017 for ; Sat, 31 Dec 2016 02:01:00 +0000 (UTC) (envelope-from jmciver@lmtribune.com) Received: from spamfw3.salnet.net (mail.lmtribune.com [199.5.221.20]) by mx1.freebsd.org (Postfix) with ESMTP id 3162F1ABA for ; Sat, 31 Dec 2016 02:00:59 +0000 (UTC) (envelope-from jmciver@lmtribune.com) X-ASG-Debug-ID: 1483149652-0850647e4d5b4c50001-jLrpzn Received: from ltmail.lmtribune.com (ltmail.lmtribune.com [192.168.135.45]) by spamfw3.salnet.net with ESMTP id kwppFX6RBcPj7TaL; Fri, 30 Dec 2016 18:00:52 -0800 (PST) X-Barracuda-Envelope-From: jmciver@lmtribune.com X-ASG-Whitelist: Sender Received: from localhost (localhost [127.0.0.1]) by ltmail.lmtribune.com (Postfix) with ESMTP id BCD4323007A; Fri, 30 Dec 2016 18:00:52 -0800 (PST) Received: from ltmail.lmtribune.com ([127.0.0.1]) by localhost (ltmail.lmtribune.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 3df3S8KSWBtT; Fri, 30 Dec 2016 18:00:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by ltmail.lmtribune.com (Postfix) with ESMTP id 243F823025A; Fri, 30 Dec 2016 18:00:51 -0800 (PST) X-Virus-Scanned: amavisd-new at lmtribune.com Received: from ltmail.lmtribune.com ([127.0.0.1]) by localhost (ltmail.lmtribune.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZRHlzGYhZMzj; Fri, 30 Dec 2016 18:00:51 -0800 (PST) Received: from [192.168.0.9] (184-155-237-86.cpe.cableone.net [184.155.237.86]) by ltmail.lmtribune.com (Postfix) with ESMTPSA id ACA2B23007A; Fri, 30 Dec 2016 18:00:50 -0800 (PST) User-Agent: K-9 Mail for Android In-Reply-To: <83EB0B5B-7D94-4FC7-A578-FBA009A17332@gmail.com> References: <1916139826.11461.1483125073411.JavaMail.zimbra@lmtribune.com> <83EB0B5B-7D94-4FC7-A578-FBA009A17332@gmail.com> MIME-Version: 1.0 Subject: Re: freebsd 10 syslog server From: Jim X-ASG-Orig-Subj: Re: freebsd 10 syslog server Date: Fri, 30 Dec 2016 18:00:46 -0800 To: Ben Woods CC: freebsd-questions@freebsd.org Message-ID: <5DA7D9B1-4E17-4E64-8874-89656F1B7C3B@lmtribune.com> X-Barracuda-Connect: ltmail.lmtribune.com[192.168.135.45] X-Barracuda-Start-Time: 1483149652 X-Barracuda-URL: https://192.168.135.20:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 4427 X-Virus-Scanned: by bsmtpd at salnet.net X-Barracuda-BRTS-Status: 1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 02:01:00 -0000 Got it fixed. Had to put entry in TOP of syslog.conf. Thx, On December 30, 2016 5:43:29 PM PST, Ben Woods wrote= : > > > >Sent from my iPhone >> On 31 Dec 2016, at 3:11 am, Jim McIver wrote: >>=20 >> Syslog messages going to /var/log/messages rather than >/var/log/apac.log=20 >>=20 >> Followed documentation from:=20 >>=20 >> https://www.freebsd.org/doc/handbook/configtuning-syslog.html=20 >>=20 >> I found where this is happening to someone else, but no answer.=20 >>=20 >> >https://lists.freebsd.org/pipermail/freebsd-questions/2011-November/2355= 65.html > >>=20 >> I even did debug option and it showed message logging to >/var/log/messages.=20 >>=20 >> Yes the /var/log/apac.log file exists.=20 >>=20 >> As the message in /var/log/messages says " apac jim: >test message" I wonder if the line in the top of the /etc/syslog.conf >that says >"*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err >/var/log/messages" is why they go to /var/log/messages?=20 >>=20 >> It mentions "notice" going to /var/log/messages and that's what shows >in /var/log/messages.=20 >>=20 >> thought?=20 >> -jm > >Hi Jim, > >Can you please provide the contents of your /etc/syslog.conf file, and >also the relevant lines from /etc/rc.conf? What version of FreeBSD are >you running? > >Note that I believe syslog will log a message multiple times if it >matches multiple rules in syslog.conf, but I could be wrong here. > >I also recommend having a read of the syslog.conf(5) man page: >https://man.freebsd.org/syslog.conf > >Regards, >Ben -- jm From owner-freebsd-questions@freebsd.org Sat Dec 31 04:40:56 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60301C9718E for ; Sat, 31 Dec 2016 04:40:56 +0000 (UTC) (envelope-from prvs=1166bc4294=vogelke@pobox.com) Received: from SCOTT-MAIL4.AFNOC.AF.MIL (scott-mail4.afnoc.af.mil [131.9.253.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "SCOTT-MAIL4.afnoc.af.mil", Issuer "DOD ID SW CA-38" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DE91B1E16 for ; Sat, 31 Dec 2016 04:40:55 +0000 (UTC) (envelope-from prvs=1166bc4294=vogelke@pobox.com) Received-PRA: neutral (us.af.mil: 131.9.254.134 is neither permitted nor denied by domain of pobox.com) client-ip=131.9.254.134; envelope-from=vogelke@pobox.com; helo=us.af.mil; Received-SPF: neutral (us.af.mil: 131.9.254.134 is neither permitted nor denied by domain of pobox.com) client-ip=131.9.254.134; envelope-from=vogelke@pobox.com; helo=us.af.mil; Received: from us.af.mil (unknown [131.9.254.134]) by SCOTT-MAIL4.AFNOC.AF.MIL with smtp (TLS: TLSv1/SSLv3,256bits,DHE-RSA-AES256-SHA) id 346b_0042_96da264e_5ad5_4545_9131_08ccac181938; Sat, 31 Dec 2016 04:40:36 +0000 Received: from ([131.9.40.227]) by 52vejx-mr-003.us.af.mil with SMTP id 40Z0FN1.260806936; Fri, 30 Dec 2016 22:40:29 -0600 Received: (qmail 5753 invoked by uid 100); 31 Dec 2016 04:40:28 -0000 From: "Karl Vogel" Date: Fri, 30 Dec 2016 23:40:28 -0500 To: freebsd-questions@freebsd.org Subject: Re: Signatures Message-ID: <20161231044028.GA3648@bsd118.wpafb.af.mil> Reply-To: vogelke@pobox.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Dec 2016 04:40:56 -0000 >> On Fri, Dec 30, 2016 at 05:40:32PM +1100, Felix Friedlander wrote: > To the best of my knowledge, FreeBSD ISO images are not signed. > You can verify their integrity (to a degree) using the checksums [...] > The only "official" PGP key for the project (as far as I'm aware) belongs > to the security officer, and is used for signing security advisories. Would the security officer be willing to sign a file containing the hashes? It should be pretty easy to automate, and that approach made me more confident about using some Google Code stuff. Making the hash list: me% sha1sum a.iso b.iso c.iso > list.sha me% gpg2 -sa -u 0xSOME_KEY_HERE --batch --clearsign list.sha me% rm list.sha me% cat list.sha.asc -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 4108f1183f0816fc0074011da4cf7a45b231b728 a.iso a7a50013af0e4a0605608d1733390bb809ec1c1a b.iso 99d2dcca01881f277152bdbaa5adc46f8951bcfc c.iso -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAG yadda yadda yadda yadda yadda yadda ... =qMgx -----END PGP SIGNATURE----- Verifying it: me% gpg2 --verify list.sha.asc gpg: Signature made Fri Dec 30 23:29:35 2016 EDT using RSA key ID xxxxxxxx gpg: Good signature from "(Signing key)" [ultimate] -- Karl Vogel I don't speak for the USAF or my company Crack-crazed squirrels terrorize New York --National Examiner article, 28 Nov 2005