ports/91047: ipsec-tools syslogs at 'daemon.info' which doesn't go anywhere
Brian Candler
B.Candler at pobox.com
Fri Dec 30 12:10:10 UTC 2005
The following reply was made to PR ports/91047; it has been noted by GNATS.
From: Brian Candler <B.Candler at pobox.com>
To: VANHULLEBUS Yvan <vanhu at netasq.com>
Cc: bug-followup at FreeBSD.org
Subject: Re: ports/91047: ipsec-tools syslogs at 'daemon.info' which doesn't go anywhere
Date: Fri, 30 Dec 2005 12:07:30 +0000
On Fri, Dec 30, 2005 at 11:34:42AM +0100, VANHULLEBUS Yvan wrote:
> I'll also try to improve racoon's reaction when having such a weak psk
> file (send a more explicit message in debug ? refuse to start ? read
> anyways the file but send explicit warnings ?).
Duplicating all ERRORs at DEBUG level is another option I hadn't considered,
but seems rather wasteful.
I have no issue with the quality of error messages produced by racoon - in
fact they're excellent. The problem was simply that I couldn't see them :-)
I don't think making 'weak psk security' errors a special case is the
solution. Rather, I think it's necessary to make _all_ error messages
properly visible.
Regards,
Brian.
P.S. another option: make the ipsec-tools port log errors to a file by
default, rather than syslog, by appropriate choice of default racoon_flags.
More information about the freebsd-ports-bugs
mailing list