Re: ports/189208: Add a mention of WITH_OPENSSL_PORT to the pkg-descr of security/openssl

2014-05-03 Thread Scot Hetzel
On Sat, May 3, 2014 at 11:35 AM, Paul Hoffman wrote: > Note that the description below does *not* match what people were saying last > week about how things work. My reading of the earlier thread was that, unless > you had WITH_OPENSSL_PORT=yes in /etc/make.conf, a port needing OpenSSL would >

Re: ports requiring OpenSSL not honouring OpenSSL from ports

2014-04-27 Thread Scot Hetzel
On Sun, Apr 27, 2014 at 10:08 AM, Jamie Landeg-Jones wrote: > One of the first things I do on installing a new machine is install > OpenSSL from ports. I do build with base OpenSSL due to the many programs > that depend on it, but using ports OpenSSL for ports makes things easier > to patch/update

Re: misc/187307: Security vulnerability with FreeBSD Jail

2014-03-05 Thread Scot Hetzel
On Wed, Mar 5, 2014 at 5:39 PM, Xin Li wrote: > So the solution would be to change your configuration such that: > : > 2) Do not make host's sshd to listen on all addresses, instead, only > listen to the designated host IP address. This is not a security > measure but avoids confusion. > You wil

Re: SSL is broken on FreeBSD

2011-04-06 Thread Scot Hetzel
On Tue, Apr 5, 2011 at 5:30 PM, Frank J. Cameron wrote: >> So it looks like /etc/ssl/cert.pem link just isn't "magic enough" to >> be used by the ''openssl s_client" command by default (without -CAfile >> command line argument). > > http://curl.haxx.se/mail/archive-2003-07/0036.html >        Unfor

Re: freebsd and snort

2008-05-27 Thread Scot Hetzel
On 5/27/08, Nigel Houghton <[EMAIL PROTECTED]> wrote: > On 5/27/08 2:51 AM, "gahn" <[EMAIL PROTECTED]> wrote: > > > Hello all: > > > > I tried to install snort under /usr/ports/security and have some problems. > > with "make all", I checked every item on the menu but I got error messages: > >

Re: freebsd and snort

2008-05-27 Thread Scot Hetzel
On 5/27/08, gahn <[EMAIL PROTECTED]> wrote: > Hello all: > > I tried to install snort under /usr/ports/security and have some problems. > with "make all", I checked every item on the menu but I got error messages: > > // > > laptop# make all > ===> snort-2.8.1_1 is

Re: SSH scans vs connection ratelimiting

2006-08-19 Thread Scot Hetzel
On 8/19/06, Pieter de Boer <[EMAIL PROTECTED]> wrote: This works as expected, IP-addresses are added to the 'lamers'-table every once in a while. However, there apparently are SSH bruteforcers that simply use one connection to perform a brute-force attack: Aug 18 00:00:01 aberdeen sshd[87989]:

Re: pam_radius fail open?

2005-08-19 Thread Scot Hetzel
On 8/19/05, Sean P. Malone <[EMAIL PROTECTED]> wrote: > $ cat /etc/pam.conf > # > # $FreeBSD: src/etc/pam.d/sshd,v 1.15 2003/04/30 21:57:54 markm Exp $ > # > # PAM configuration for the "sshd" service > # > > # auth > > #sshd auth required pam_radius.so -update -/usr/local/etc/radius > #auth