is this another bug?
___
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hello out there,
Implementing the SNI extension, to permit encrypted virtual web domain service,
seems to be spreading.
I hope I'm not too far OT in asking this list for advice on making this
transition on FreeBSD.
The first server to be migrated is currently running:
7.1-RELEASE-p13
is thread.
Can you at least prepended [OT RANT] to the subject?
Some people monitor this list to be informed of possible FreeBSD security
issues, of which this isn't.
Please, get a motel room or something...
johnea
___
freebsd-security@freeb
Hello Freebsd-security,
I've got portaudit alarm on perl-5.8.9_7 with regard to
perl -- denial of service via algorithmic complexity attack on hashing routines.
Reference:
http://portaudit.FreeBSD.org/68c1f75b-8824-11e2-9996-c48508086173.html
But on the other server I have perl-thr
Thank you. Now it's fixed.
RS> On (03/15/13 17:30), free...@tern.ru wrote:
>>Hello Freebsd-security,
>>
>>I've got portaudit alarm on perl-5.8.9_7 with regard to
>>
>>perl -- denial of service via algorithmic complexity attack on hashing
>>routi
and motivated people.
johnea
_______
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
Hi all,
regarding xz… have you seen this?
https://github.com/libarchive/libarchive/pull/1609
regards
On 3/30/24 00:47, Alan Somers wrote:
A malicious developer added a backdoor to xz 5.6.0 and 5.6.1, and
snuck it into Fedora builds. That's the same version that FreeBSD
CURRENT uses.
Hi, freebsd-security.
I have FreeBSD 5.3-STABLE.
When I try to change user's password (via passwd) I recieve the
following:
passwd: entry inconsistent
passwd: pam_chauthtok(): error in service module
passwd: in pam_sm_chauthtok(): pw_copy() failed
and password stays unchanged.
There a
those times when you
do want scrollback.
alternatively,
alias clear='for i in {1..SC_HISTORY_SIZE} ; do echo "" ; done'
-Jason
___
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hi,
I'm having trouble getting an answer to the following problem on -questions
- I hope someone here has done something similar and can help.
I'd like to compile support for FreeBSD OPIE into sshd. Presently I have
to use PAM to achieve one-time password support. On a 4.x system I ha
t.org.au
Qld 4072 Australia | Email: [EMAIL PROTECTED]
___
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
please?
thanks,
-- Joel Hatton --
Security Analyst| Hotline: +61 7 3365 4417
AusCERT - Australia's national CERT | Fax: +61 7 3365 7031
The University of Queensland| WWW: www.auscert.org.au
Qld 4072 Australia | Email: [EMAIL PROTECTED]
_
nalyst| Hotline: +61 7 3365 4417
AusCERT - Australia's national CERT | Fax: +61 7 3365 7031
The University of Queensland| WWW: www.auscert.org.au
Qld 4072 Australia | Email: [EMAIL PROTECTED]
_______
freeb
As an administrator, time is always an issue. FreeBSD has proven
itself time and again. Having said that, one "wish" would be to have
a default/built-in security update mechanism.
Since time is always and issue, if the system could by default
(without an admin havin
wintel and other *nix worlds, not every administrator updates their
servers. Ok, maybe only a few FreeBSD administrators don´t update...
What I am trying to suggest is a mechanism that incorporates all
security fixes and specified (or installed) ports/packages for a given
server, wi
Hi Colin,
On Fri, 30 Jun 2006 20:13:44 -0700, Colin Percival wrote:
>Dolan- Gavitt, Brendan F. wrote:
>> I've been trying for the past few days to come up with a method for
>> checking a FreeBSD system to see if it is vulnerable to an issue
>> described by a FreeBSD
On Sun, 25 Feb 2007 12:14:24 +0100 (CET), "Johan Berg" wrote:
>The FreeBSD Handbook also have some good tips:
>
>http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/security.html
>
>
>Regards,
>
>-- Johan Berg
Al
Hi,
I am just new to the FreeBSD system and look forward to take active part in
contributing.
Can someone please guide where can I find OCF source code in FreeBSD and
also is there IKE implementation and OpenSWAN ?
Regards,
Raja
___
freebsd
imate users out,
etc.
-Jason
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)
Comment: See https://private.idealab.com/public/jason/jason.gpg
iD8DBQFI0PwqswXMWWtptckRAqLsAJ9taCFEPfVGwY6Rrt3qtLuHVvmNDwCfatyl
S++ho4Gf4Zl/3E6Vjkks26o=
=gGZG
-END PGP SIGN
popper : x.x.x.0/255.255.255.0 : allow (your directly-connected users)
qpopper : all : deny
RossW
_______
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
> As of now:
>
> - SVN is *the* source of truth.
Would it be possible to publish FreeBSD's Subversion repository using
HTTPS, instead of HTTP?
--
I FIGHT FOR THE USERS
_______
freebsd-security@freebsd.org mailing list
http://lists.freeb
me out when they do something prohibited.
Black holes and null routes have their place, such as in response to an active
denial of service attack, but not in the primary traffic control policy.
--
I FIGHT FOR THE USERS
___
freebsd-security@freebsd.
___
freebsd-security@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
opy into a FreeBSD system.
I think the best way to do it would be to call random_harvest_queue(...),
but what do I use as the source enum (see /usr/include/sys/random.h)?
ENTROPYSOURCE, I guess?
I believe it's also possible to open /dev/random for write to inject
entropy, and I'm sure I
Am Thu, 4 Apr 2024 01:14:52 -0500
Kyle Evans schrieb:
> On 4/4/24 00:49, FreeBSD User wrote:
> > Hello,
> >
> > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1:
> >
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:01.telnet Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:02.sendfile Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:03.amd64 Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:04.ifconf Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:05.cvsSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:06.iirSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:07.ldtSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:08.kmem Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:06.iirSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:08.kmem Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:09.httSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:09.httSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:10.tcpdumpSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:11.gzip Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:12.bind9 Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:13.ipfw Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:14.bzip2 Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:15.tcpSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:16.zlib Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:17.devfs Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:18.zlib Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:19.ipsec Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:20.cvsbug Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:20.cvsbug Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-05:21.opensslSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:01.texindex Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:02.ee Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:03.cpio Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:04.ipfw Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:01.texindex Security Advisory
The FreeBSD Project
Topic
Thank you very much for your problem report.
It has the internal identification `bin/91622'.
The individual assigned to look at your
report is: freebsd-bugs.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=91622
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:05.80211 Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:06.kmem Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:07.pf Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:08.sack Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:09.opensshSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:10.nfsSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:09.opensshSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:11.ipsec Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:12.opie Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:13.sendmail Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:14.fpuSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Everyone,
On June 1st, 21 days from now, FreeBSD 4.10 will have reached
its two year End of Life and will no longer be supported by
the FreeBSD Security Team. While some security fixes may be
merged to the RELENG_4_10 security branch after the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:15.ypserv Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:16.smbfs Security Advisory
The FreeBSD Project
Topic
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:17.sendmail Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:08.pppSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:08.pppSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:19.opensslSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:20.bind Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:21.gzip Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:23.opensslSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:23.opensslSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:22.opensshSecurity Advisory
The FreeBSD Project
Topic
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There has been a lot of discussion on these two mailing lists about the upcoming
EoL of FreeBSD 4.x which I mentioned in my email entitled "HEADS UP: FreeBSD
5.3, 5.4, 6.0 EoLs coming soon". Now that everybody (hopefully) has had their
say
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:24.libarchive Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:25.kmem Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-06:26.gtar Security Advisory
The FreeBSD Project
Topic
-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
=
FreeBSD-SA-07:01.jail Security Advisory
The FreeBSD Project
Topic
-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
=
FreeBSD-SA-07:02.bind Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:03.ipv6 Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:04.file Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:04.file Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:05.libarchive Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:01.jail Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:06.tcpdumpSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:07.bind Security Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:08.opensslSecurity Advisory
The FreeBSD Project
Topic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
=
FreeBSD-SA-07:08.opensslSecurity Advisory
The FreeBSD Project
Topic
Hello Everyone,
In light of the longer-than-expected window between 6.2-RELEASE and 6.2-RELEASE,
the End-of-Life date for FreeBSD 6.2 has been adjusted from January 31st, 2008
to May 31st, 2008. As a result, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will
all cease to be supported at the end of
1 - 100 of 639 matches
Mail list logo
