The patch just committed to master (258ad0e) fixes CVE-2012-2143. This
bug manifests for UTF-8 encoded passwords that contain a 0x80 byte (for
instance, the À character). This fix restores proper behavior, which
means that authentication will break for such passwords. To our
knowledge, nothing
On 01/17/2012 10:12 AM, Matthias Schmidt wrote:
He guys,
I want to bring the following discussion on the oss-security list to
your attention:
http://www.openwall.com/lists/oss-security/2012/01/16/2
This post and previous posts contain all known details. It seems Solar
contacted Matt
On 08/12/2010 10:30 AM, Dylan Reinhold wrote:
On 08/06/2010 01:27 PM, Matthew Dillon wrote:
:Hi people,
:
:is there a way to easily list all disks and their associated serno's ?
:Something like 'blkid' utility of Linux, if you happen to know it.
:I could happily hack something like that, if
Am 03/07/2010 01:13 μμ, schrieb Johannes Hofmann:
Hi,
what is the reason for creating powerd instead of using sysutils/estd fr
om pkgsrc, which already does ACPI P-states based frequency scaling?
I think the main reason is Matt couldn't find estd so he just hacked up
powerd instead. No idea
On 26/05/2010 12:26 πμ, Alexander Polakov wrote:
2010/5/26, Marc G. Fournierscra...@hub.org:
As of this posting, we are getting reports in from all the *BSD variants:
PCBSD 4 872
FreeBSD1 627
DesktopBSD 154
NetBSD43
OpenBSD
Chris Turner wrote:
Justin C. Sherrill wrote:
- General ideas about the bulk builds and binary installs; I've been
staring at it so long I can't see the forest because there's all these
trees in the way.
Yeah.. Lots of these ideas crossing my mind today as well -
this DNS-in-base thing
Justin C. Sherrill wrote:
So, after seeing that PostgresQL is moving services from FreeBSD to Debian
because of ease of packaging, and seeing Ivan Voras's idea for a stable
branch of ports similar to the quarterly pkgsrc releases, I've been
thinking about the pkgsrc service.
(Here's the
Chris Turner wrote:
Aggelos Economopoulos wrote:
Well, w/o having seen the code, this sounds like a bit of a hack :) Also
I'm not sure what problem you're solving. Pkgsrc already has working
package dependencies. The serious issue is with handling upgrades.
yup. possibly so.
Problem
Chris Turner wrote:
Aggelos Economopoulos wrote:
My by far most important gripe w/ pkgsrc is the inability to do mass
upgrades from binary packages in a straightforward manner. Not even sure
if it's anything the pkgsrc developers are concerned with.
Can't you do this if you have the right
Matthew Dillon wrote:
Actually let me correct that. I changed the name
to mirror-master.dragonflybsd.org.
There seems to be a bit of confusion about this on irc; just to clarify,
this is ONLY for mirrors to pull from.
If you are not running a mirror yourself, please pull from a mirror
Walter wrote:
Aggelos Economopoulos wrote:
Walter wrote:
I got curious about BSD (DragonFly, specifically) security and
wondered why there wasn't a security process that processed all
security-relevant error messages which could then be used to
block IPs, disable user accounts, and kill
Walter wrote:
I got curious about BSD (DragonFly, specifically) security and
wondered why there wasn't a security process that processed all
security-relevant error messages which could then be used to
block IPs, disable user accounts, and kill processes.
Because
a) such a mechanism could be
Max Herrgård wrote:
Den 2010-02-08 09:00:02 skrev Steve O'Hara-Smith st...@sohara.org:
Hi,
I've just done a pkgsrc update and fired off a build of my packages
only to find that bash fails to build because of this bit of code:
# if defined __sferror || defined __DragonFly__ /*
Steve O'Hara-Smith wrote:
Yes. Like I exlained above, I don't think removing the code for
DragonFly is the correct solution. Unless someone takes the time to
audit fpurge(), I suppose using __FILE_public is the safest fix since
it brings us back to how things were.
So this patch
Steve O'Hara-Smith wrote:
So rather more like the one attached then (which is also suitable
for use in localpatches or as a pkgsrc patch file).
Yah. Assuming you've tested it, can you please attach it to Rumko's PR?
Thanks!
Aggelos
Alex Hornung wrote:
[...]
xmlsec1 seems to try to find libdl. This should be fixable; anyone got
more insight and some time to fix that?
On linux libdl is needed for the dl*() functions which are found in libc
in dragonfly. So the solution is not to link with libdl.
HTH,
Aggelos
Aggelos Economopoulos wrote:
commit c40674358ed4bedb23390f50832cadef96754a9c
Author: Jan Lentfer jan.lent...@web.de
Date: Fri Nov 27 10:06:46 2009 +0100
bind - Upgraded vendor branch to 9.5.2-P1
Thanks to Jan Lentfer we have an updated bind in base. Give it some
testing please. Note
Jeremy C. Reed wrote:
Regarding the DNSSEC bug -- does that even matter for DragonFly -- did
the DragonFly ever get built with openssl? (I was working on it last
year, but I don't think I ever committed simple patch before switched to
git.)
Indeed it isn't configured with --use-openssl, so
Our openssl has been updated to version 0.9.8l which works around
CVE-2009-3555 (see for instance http://extendedsubset.com/ or
http://www.securityfocus.com/bid/36935). The vulnerability allows data
injection by man-in-the-middle attackers, so you are advised to upgrade
to the latest version by
Jordan Gordeev wrote:
It's time public testing of the amd64 port begins.
The code is available in my git repo at
git://leaf.dragonflybsd.org/~smtms/dragonfly.git in branches amd64 and
amd64+hacks.
The amd64+hacks branch contains what amd64 contains + some band aid
to keep the system
On Wednesday 16 July 2008, Sepherosa Ziehau wrote:
On Wed, Jul 16, 2008 at 4:41 PM, Simon 'corecode' Schubert No,
we will always stick to -O. GCC is a moving target too, even if
-O2 works now there is a high chance it will break something in future
GCC rolls.
Why should -O2
By now every administrator and/or ssh user should have heard about the
bug in debian's ssl library. If you've been offline for the past few days,
start here:
http://lists.debian.org/debian-security-announce/2008/msg00152.html
http://metasploit.com/users/hdm/tools/debian-openssl
While our OpenSSL
On Friday 16 May 2008, Matthew Dillon wrote:
[...]
I am downloading the key fingerprings debian published and will run it
against all the accounts on leaf, pkgbox, and other machines.
This just in: if you were going to use ssh-vulnkey, debian just announced they
have been told about
Hello all,
I'll be buying parts for an AMD-based system tomorrow and I'd appreciate info
on what motherboards/chipsets you have booted DragonFly on without problems.
Problems you've encountered are helpful also. Hopefully your answers will be
useful to other buyers too (at least for the next
On Sunday 20 May 2007 17:34, Morgan Reed wrote:
[...]
I've tested by exporting / and pointing the client to that and that
works so I figure it's got to be something missing from my target root
fs, either that or my world isn't quite right (rebuilt world with
NOSHARED=no)...
If it's something
25 matches
Mail list logo
