I assume beta 2 is pretty darn close to what 7.1 release will be. Is
there a list I can look at that details the outstanding issues/items
being tested? I've checked the ERRATA and RELNOTES in the BETA2
directory, and didn't get much info.
The goal is building a multi i/f router (just forwarding
't. I'm thinking of many PHP based
in general, and most of the forum apps in particular. Be sure to
research the security history of web apps (or anything that opens up a
port listener). Sign up for the mailing list of what you install, so
you'll be alerted to security updates.
C
Bruce Burden wrote:
On Mon, Oct 29, 2007 at 04:25:18PM -0700, Jason Slack wrote:
I want to try version 7 as it has items of interest to me, but I am not one
to continually wipe and reload my machine, can you upgrade from the test
releases of 7 available now to the final release when ready?
I'm writing this more as a heads up to those using freebsd as a guest
under virtualpc 2007 on Win XP sp3 host.
I created a fixed size virtual disk (8gig). Just to be sure, I ran the
XP disk check on the underlying disk before hand. I then installed
freebsd 7.1 from cd image. Next I csup'ed to ge
Christer Solskogen wrote:
On Fri, 29 Sep 2006 05:30:05 -0700
Colin Percival <[EMAIL PROTECTED]> wrote:
Do you mean using different mirrors? I'm using a supfile for that. But
if you mean building I used 'make buildkernel buildworld'
But doing a "make includes" did the trick. It compiles as it
FreeBSD Security Officer wrote:
In short:
* FreeBSD is a volunteer project, and we don't want to volunteer to support
FreeBSD 4.x beyond the scheduled EoL date of January 31st, 2007;
* Even if we did want to support FreeBSD 4.x beyond that date, I'm not certain
that we would be abl
Quoting Michael Lednev <[EMAIL PROTECTED]>:
Hello, secmgr.
On 12 ìàðòà 2005 ã., 1:52:50 you wrote:
you can look here http://www.freebsd.org/cgi/query-pr.cgi?pr=75540
this patch adds support for nforce3 and 4 sata controllers, i think
with little modification it will do for nforce2
Michael,
Many
ing attacks from filling up your periodic security mail.
> > Are you sure about that? I only allow PublickeyAuthentication ssh2
> > connections but I get lots of security mail messages like:
> >
> > Nov 16 01:44:08 maxwell sshd[70067]: Invalid user marcos from 202.54.49.7
&
Stephen Clark wrote:
> Hello List,
>
> We have a network appliance that is currently based on 4.9. We are in
> the process of releasing
> a new version based on 6.1 stable.
>
> In our testing using nttcp thru the appliance we see insignifant
> difference in thruput between the 2
> versions in a con
Vinny Abello wrote:
>
> OK, I've enabled polling in my kernel and did ifconfig bge0 polling and
> it accepted it and shows that polling is enabled on bge0 when checking
> with ifconfig. Unfortunately, this did not resolve the packet loss issue
> I wrote about originally. I still have the same loss.
Gregory Neil Shapiro wrote:
I've a feeling it's documented somewhere else, but can't remember
right now.
The rc.conf(5) man page points to rc.sendmail(8) man page.
And the rc.sendmail(8) under 5.4 stable says that "NONE" is deprecated
and will be removed in a future release. Accordin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
On February 28th, FreeBSD 7.1 will reach its End of Life and will no longer be
supported by the FreeBSD Security Team. (This was initially scheduled to occur
today, but in light of the imminent arrival of FreeBSD 7.4 I decided to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been updated to
reflect the EoL (end-of-life) of FreeBSD 7.1. The new list of supported
branches is below and at < http://security.freebsd.org/ >.
Users of FreeBSD 7
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been updated
to reflect the EoL (end-of-life) of FreeBSD 7.2. The new list is below
and at http://security.freebsd.org/ >.
Users of FreeBSD 7.2 are advised to upgr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their
End of Life and will no longer be supported by the FreeBSD Security Team.
Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD
6.x stable
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been updated to
reflect the EoL (end-of-life) of FreeBSD 6.4 and FreeBSD 8.0. Since FreeBSD
6.4 was the last remaining supported release from the FreeBSD 6.x stable
branch, support for the FreeBSD 6.x stable branch has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
On January 31st, FreeBSD 6.3 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 a newer release before that date -- more conservative
users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been updated
to reflect the EoL (end-of-life) of FreeBSD 6.3. The new list is below
and at http://security.freebsd.org/ >.
Users of FreeBSD 6.3 are advised to upgr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
In keeping with the FreeBSD Security Team policy concerning the EoL dates for
"Normal" support releases,
"a minimum of 12 months after the release, and for sufficient additional
time (if needed) to ensure that t
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been updated
to reflect recent EoL (end-of-life) events. The new list is below and
at http://security.freebsd.org/ >. FreeBSD 5.5, FreeBSD 6.1, and
FreeBSD 6.2 h
May 2008.
FreeBSD users should plan on upgrading to either FreeBSD 6.3 or FreeBSD 7.0 once
those have been released (hopefully by the end of December). FreeBSD 6.3 will
be supported until the end of 2009, while FreeBSD 7.0 will be supported until
the end of 2008.
Colin Percival
FreeBSD Security
-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
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been updated
to reflect the EoL (end-of-life) of FreeBSD 7.0. The new list is below
and at http://security.freebsd.org/ >. Please note that FreeBSD
7.0 was originally announced with an EoL date of February 28, 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
On January 31st, FreeBSD 6.3 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 a newer release before that date -- more conservative
users
-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
, I'd like to offer some background and explanation.
The concept of "security branches" in the FreeBSD CVS tree was introduced with
FreeBSD 4.3, about five years ago. At the time, support was only guaranteed for
the most recent FreeBSD release and one -STABLE branch (either the lat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been
updated to reflect recent EoL (end-of-life) events. The new list is
below and at http://security.freebsd.org/ >. FreeBSD 5.3 and
FreeBSD 5.4 have `expired' an
[1]Wells Fargo
[2]Wells Fargo Credit Card Dear valued WellsFargo ® member:
Due to concerns, for the safety and integrity of the wellsfargo
account we have issued this warning message :
We have noticed that your Wells Fargo online account needs to be
updated once again, pleas
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been
updated to reflect recent EoL (end-of-life) events. The new list is
below and at http://security.freebsd.org/ >. FreeBSD 4.11 and
FreeBSD 6.0 have `expired' an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
The branches supported by the FreeBSD Security Officer have been
updated to reflect recent EoL (end-of-life) events. The new list is
below and at http://www.freebsd.org/security/ >. FreeBSD 4.10
has `expired' and is n
34 matches
Mail list logo
