Em 07-06-2014 00:04, Solar Designer escreveu:
> tools and ethics are separate things
It seems like you got to the real issue now.
Cheers,
--
Giancarlo Razzolini
GPG: 4096R/77B981BC
On 06/06/14 18:20, Stuart Henderson wrote:
> On 2014/06/07 00:04, Alexander Hall wrote:
>> Care to mention the fixed package version, so one knows when it's available
>> at the favourite mirror?
>>
>> cvsync-0.24.19p3, yes?
>
> That is correct. There is a -current snapshot package for i386 at
> h
To clarify and for the record:
Being on the distros list is not mandatory to receive advance
notification of security issues. The list is just a tool. People
reporting security issues to the distros list are encouraged to also
"notify upstream projects/developers of the affected software, other
On 06/06/14 19:29, Stuart Henderson wrote:
On 2014/06/06 11:17, Bob Beck wrote:
If you or someone you love runs an anoncvs server, they need to see this.
We recently added commitid support to our cvs repo. all works fine with
cvs and this.
However, we ran into a problem with cvsync in ports. M
Hello,
I've been doing some work recently on crypto code, and noticed that
there aren't many/any good clean implementations of performant crypto
code out there (or maybe I just don't know of them). Both OpenSSL's
and NSS's code has issues w/ portability and/or cleanliness.
But, I prefer to reuse
On 2014/06/07 00:04, Alexander Hall wrote:
> Care to mention the fixed package version, so one knows when it's available
> at the favourite mirror?
>
> cvsync-0.24.19p3, yes?
That is correct. There is a -current snapshot package for i386 at
http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i3
On 06/06/14 19:29, Stuart Henderson wrote:
On 2014/06/06 11:17, Bob Beck wrote:
If you or someone you love runs an anoncvs server, they need to see this.
We recently added commitid support to our cvs repo. all works fine with
cvs and this.
However, we ran into a problem with cvsync in ports. M
And here's a quick and dirty regression test.
Index: Makefile
===
RCS file: /home/vcs/cvs/openbsd/src/regress/lib/libc/Makefile,v
retrieving revision 1.38
diff -u -p -r1.38 Makefile
--- Makefile29 Dec 2013 01:39:44 - 1.38
If correct, this fixes a 22 year old bug that exists since 4.4BSD alpha :)
In modf, when we go down the Lbig jump, f0:f1 is never set and just
contains gibberish. Usually NAN or 0.0. What we really want is just copy
the input out and be done.
This completely corrupts python when hashing floats fo
On 2014/06/06 20:54, Otto Moerbeek wrote:
> This volumes feel pretty fast, so I suspect caching mode is OK.
>From experience, you definitely wouldn't be saying "pretty fast"
if it was in WT. :)
On Fri, Jun 06, 2014 at 02:46:35PM -0400, Jim wrote:
> On Fri, Jun 06, 2014 at 11:45:49AM +0200, Otto Moerbeek wrote:
> > Hi,
> >
> > I have an PERC 6/i Integrated adapter here:
> >
> > mfi0 at pci2 dev 0 function 0 "Symbios Logic SAS1078" rev 0x04: apic 1 int 0
> > mfi0: "PERC 6/i Integrated",
On Fri, Jun 06, 2014 at 11:45:49AM +0200, Otto Moerbeek wrote:
> Hi,
>
> I have an PERC 6/i Integrated adapter here:
>
> mfi0 at pci2 dev 0 function 0 "Symbios Logic SAS1078" rev 0x04: apic 1 int 0
> mfi0: "PERC 6/i Integrated", firmware 6.2.0-0013, 256MB cache
>
> Which has an OK battery but st
bump.
anybody?
On Sat, 31 May 2014 20:29:42 +0200
Benjamin Baier wrote:
> On Sun, 1 Jun 2014 00:57:43 +1000
> Joel Sing wrote:
> > In this case I think readability wins. I do not believe that there is a lot
> > to
> > gain from overflow protection given the numbers used in these calculations
bump.
anybody?
On Sat, 31 May 2014 16:40:35 +0200
Benjamin Baier wrote:
> While here also stop casting {m,c}alloc return value.
>
Index: inetd.c
===
RCS file: /cvs/src/usr.sbin/inetd/inetd.c,v
retrieving revision 1.137
diff -u -p -r
bump.
anybody care enought to commit?
On Sat, 31 May 2014 13:06:16 +0200
Benjamin Baier wrote:
Index: aicasm.c
===
RCS file: /cvs/src/sys/dev/microcode/aic7xxx/aicasm.c,v
retrieving revision 1.15
diff -u -p -r1.15 aicasm.c
--- aicasm
On 2014/06/06 11:17, Bob Beck wrote:
> If you or someone you love runs an anoncvs server, they need to see this.
>
> We recently added commitid support to our cvs repo. all works fine with
> cvs and this.
>
> However, we ran into a problem with cvsync in ports. Most mirror
> maintianers use cvsyn
If you or someone you love runs an anoncvs server, they need to see this.
We recently added commitid support to our cvs repo. all works fine with
cvs and this.
However, we ran into a problem with cvsync in ports. Most mirror
maintianers use cvsync to fetch the repository from anoncvs.ca - it
had
Please note that we're having an issue with cvsync and some of the
mirrors at this time, so cvs up -rOPENBSD_5_5 may not be a reliable
way to update. Sorry about that. Please use the patches on ftp.
There is also a patch available for 5.4.
untrusted comment: signature from openbsd 5.5 base secret
Please note that we're having an issue with cvsync and some of the
mirrors at this time, so cvs up -rOPENBSD_5_5 may not be a reliable
way to update. Sorry about that. Please use the patches on ftp.
OpenBSD 5.4 is also affected.
untrusted comment: signature from openbsd 5.5 base secret key
RWRGy
Em 06-06-2014 03:49, Fabian Raetz escreveu:
> On Thu, Jun 05, 2014 at 07:39:01PM +0200, Fabian Raetz wrote:
>> Hi tech@,
> Please ignore this thread!
>
> A reboot after rebuilding userland fixed the problem. Sorry!
>
>> when calling ifconfig(8) with a not supported option like below, it
>> segfault
On Sat, May 31, 2014 at 06:22:42PM +, Sébastien Morand wrote:
> Hi,
>
> I finally bought a TL W723N and try.
>
> usbdevs gives:
> port 2 addr 3: high speed, power 500 mA, config 1, 802.11n NIC(0x8179),
> Realtek(0x0bda), rev 0.00, iSerialNumber 00E04C0001
>
> 0x8179 is not present in kernel
Which has an OK battery but still reports itself as being in WT mode:
So what's the status of this WT/WB flag? Can't it be trusted for PERC
6/i and maybe other adapters? If so, a man page blurp would be needed
imo.
Difficult experiences have taught me to mistrust all the sensors
c
On 2014-06-06, Otto Moerbeek wrote:
> So what's the status of this WT/WB flag? Can't it be trusted for PERC
> 6/i and maybe other adapters?
On the old hub.ports (which had a PERC 5/i), the WT/WB flag could
be trusted. Disk performance was noticeably worse in WT mode.
--
Christian "naddy" Weis
Hi,
I have an PERC 6/i Integrated adapter here:
mfi0 at pci2 dev 0 function 0 "Symbios Logic SAS1078" rev 0x04: apic 1 int 0
mfi0: "PERC 6/i Integrated", firmware 6.2.0-0013, 256MB cache
Which has an OK battery but still reports itself as being in WT mode:
# sysctl hw.sensors.mfi0.indicator0
h
On Thu, Jun 05, 2014 at 09:41:03AM -0600, Theo de Raadt wrote:
> > The new malloc has been comitted, so now take the next step.
> >
> > This changes _dl_malloc to a regular non-zeroing _dl_malloc and uses
> > _dl_calloc and _dl_reallocarray.
> >
> > This needs carefull review.
>
> Yes very care
From Quanah Gibson-Mount:
UNKOWN->UNKNOWN
Index: crypto/asn1/asn1_err.c
Please refrain from sending diffs you obviously didn't test.
Miod
Hi All,
>From Quanah Gibson-Mount:
UNKOWN->UNKNOWN
Index: crypto/asn1/asn1_err.c
===
RCS file: /cvs/src/lib/libssl/src/crypto/asn1/asn1_err.c,v
retrieving revision 1.16
diff -u -p -u -p -r1.16 asn1_err.c
--- crypto/asn1/asn1_err.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I do not believe that they, are specifically ignoring OpenBSD, I believe
they are ignoring the BSDS in general. Perhaps someone notified FreeBSD
but nobody notified the DragonflBSD team either.
On 06/05/2014 09:27 PM, Theo de Raadt wrote:
> There are
28 matches
Mail list logo
