similar to: [fbsd] HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On January 31st, FreeBSD 4.11 and FreeBSD 6.0 will have reached their End of Life dates and will no longer be supported by the FreeBSD Security Team. Users of either of these FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date. Discussion concerning FreeBSD

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On January 31st, FreeBSD 4.11 and FreeBSD 6.0 will have reached their End of Life dates and will no longer be supported by the FreeBSD Security Team. Users of either of these FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date. Discussion concerning FreeBSD

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On May 31st, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 5.5 is the last remaining supported release from the FreeBSD 5.x stable branch, support for the FreeBSD 5.x stable branch will also cease at the same point. Users of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On May 31st, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 5.5 is the last remaining supported release from the FreeBSD 5.x stable branch, support for the FreeBSD 5.x stable branch will also cease at the same point. Users of

sthaug at nethelp.no [2016-05-27 08:53 +0200] : > I don't see any problem using ULA with for instance /124 netmask: [...] > 96 bit works too: [...] FreeBSD version? Mine is 10.3-RELEASE-p3. Dunno. Could be that I made some mistake but I also tried the setup with /96 and adding the route to the tap0 interface and it did not work. Niklaas -------------- next part -------------- A

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Users of either of those FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date. In addition, the FreeBSD 6.0 End of Life is presently scheduled

I'm trying to understand the newbus and acpi interactions on this Dell R620 that result in the Broadcom adapter board being probed "backwards" or just plain out of order in comparison to the connector layout and the linux tg3 driver. We seem to be detecting PCI0:2:0 before PCI0:1:0. This seems odd to me. When I replace the broadcom daughter card with an intel daughter card, this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On April 30th, FreeBSD 7.0 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of FreeBSD 7.0 are strongly encouraged to upgrade to FreeBSD 7.1 before that date. Note that the End of Life date for FreeBSD 7.0 was originally announced as being February 28, but was delayed by two months in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On April 30th, FreeBSD 7.0 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of FreeBSD 7.0 are strongly encouraged to upgrade to FreeBSD 7.1 before that date. Note that the End of Life date for FreeBSD 7.0 was originally announced as being February 28, but was delayed by two months in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

I would like to load OpenSolaris on my file server. I have previously loaded FBSD using zfs as the storage file system. Will OpenSolaris be able to import the pool and mount the file system created on FBSD or will I have to recreate the the file system. -- This message posted from opensolaris.org

Can anyone share the proper config to get wrappers working in dovecot on FreeBSD? The dovecot examples do not seem to work, and I thought perhaps FBSD needs slightly different configs. I've compiled with: -DHAVE_LIBWRAP which I presume is the first step. The example for dovecot.conf in uncommenting: login_access_sockets = tcpwrap merely causes a log error of "imap-login: Error:

# Space separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } I believe that's all. I had placed it all in /usr/local/etc/dovecot/dovecot.conf. On Mon, Nov 14, 2016 at 11:45 AM, Jim Pazarena

Hi, Recently some security issues with bind have come up. NetBSD patched it's version of 9.3.0: http://mail-index.netbsd.org/source-changes/2005/01/27/0009.html Is the version in RELENG_5 not affected? (ftp://ftp.isc.org/isc/bind/9.3.0/9.3.0-patch1) Bye, Mipam.

Hi, I am trying to impliment OpenSSH v2.9p1 with the Krb5/GSSAPI patches at: http://www.sxw.org.uk/computing/patches/openssh-2.9p1-gssapi.patch On a FreeBSD 4.3-STABLE system (with both the integrated Heimdal libs and the MIT Krb5 package from ports intstalled). I patched the src tree, reconfigured, recompiled, installed, and it works - except for Krb5 passwords or Krb5 tickets. And I really

Does this issue with GDB 5.3 still remain in FreeBSD 4.8? http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/src/gdb/PROBLEMS?con tent-type=text/x-cvsweb-markup&cvsroot=src *-*-freebsd* --------------- Due to a kernel bug (kern/35175), detaching from an attached process will very likely cause the process to be stop or die with a Trace/BPT trap. i386-*-freebsd[34]* -------------------

*That* command would shut it down, same as `upsdrvctl shutdown` but with a better chance to debug what actually happens in the dialog. Actually with NUT v2.8.2 you can also request debug of drivers via `upsdrvctl -d -DDDDDD shutdown ups_bottom` or some such (`-d` tells it to pass debug flags to driver programs it launches). Jim On Tue, Dec 17, 2024 at 9:35?PM Lee Damon <lvd at uw.edu>

Dovecot with libwrap doesn't work on FreeBSD for some reason or another. I have these lines in my /etc/hosts.allow: ALL: LOCAL 127.0.0.1: allow pop3: ALL: allow ALL: ALL: deny Yet when you try to telnet to localhost, port 110 this is what happens: Aug 29 22:48:38 dodo dovecot: pop3-login: Error: connect(tcpwrap) failed: Permission denied I also tried auth_debug=yes to see what's wrong

Hi John, this is my smb.conf-file: # /usr/local/etc/smb.conf # # $Id: smb.conf,v 1.1 2002/11/28 17:53:45 root Exp $ # [global] workgroup = ossa6 netbios name = claire server string = File-services on claire. hosts allow = 192.168.0.0/255.255.255.0 max log size = 0 security = user encrypt passwords = yes smb passwd file = /usr/local/etc/smbpasswd socket options = TCP_NODELAY interfaces =