On Mon, Dec 01, 2014 at 09:52:31AM -0700, Todd C. Miller wrote:
> There were two dead stores found by the llvm analyzer (the value
> is overwritten before it is read). I've also marked functions
> calling done() __dead to avoid false positives.
>
> There are two more warnings from the analyzer b
On 12/01/14 16:38, Maxim Khitrov wrote:
> On Tue, Nov 18, 2014 at 7:43 AM, Theo de Raadt
> wrote:
>>> /var/tmp has been changed to be a symlink to /tmp. Traditionally,
>>> the difference between /tmp and /var/tmp has been that the former is
>>> cleaned after a reboot, while the latter isn't.
Any ideas, should this work?
On Mon, Dec 1, 2014 at 5:39 AM, Abel Abraham Camarillo Ojeda
wrote:
> Hi
>
> Found on OpenBSD/5.5, reproduced in OpenBSD-current:
>
> I have a problem when authenticating a user whose
> username is bigger than 31 chars:
>
> expected - auth longemailabcde@abcdef.ghijkl
fritjof
Index: xmalloc.c
===
RCS file: /cvs/src/usr.bin/rcs/xmalloc.c,v
retrieving revision 1.6
diff -u -p -r1.6 xmalloc.c
--- xmalloc.c 1 Dec 2014 21:58:46 - 1.6
+++ xmalloc.c 1 Dec 2014 23:59:50 -
@@ -60,7 +60,7
Hi list!
With the memcpy change isakmpd's ui.c was aborting.
the buffer is the same so this patch changes it to
memmove.
Thanks!
Index: ui.c
===
RCS file: /cvs/src/sbin/isakmpd/ui.c,v
retrieving revision 1.55
diff -u -p -u -r1.55 ui
On Tue, Nov 18, 2014 at 7:43 AM, Theo de Raadt wrote:
>> /var/tmp has been changed to be a symlink to /tmp. Traditionally,
>> the difference between /tmp and /var/tmp has been that the former is
>> cleaned after a reboot, while the latter isn't. Making /var/tmp a
>> symlink to /tmp means it'
On Thu, Nov 13, 2014 at 5:50 PM, Rafael Zalamena wrote:
>
> Conclusion: (short answer)
> The problem with moving the vlan_input chunk is that we have to do tag
> re-insertion in some cases, might break QinQ and it looks to be a more
> intrusive code change than it is with this diff.
>
Hi,
Is ther
On Mon, 01 Dec 2014 12:23:01 +0100, Otto Moerbeek wrote:
> > (gdb) list
> > 4992sprintf(textptr, "net:");
> > 4993textptr = devicetext + strlen(devicetext);
> > 4994 }
> > 4995
> > 4996 snprintf(buf, sizeof(buf), ":%s", devname);
> > 4997
There were two dead stores found by the llvm analyzer (the value
is overwritten before it is read). I've also marked functions
calling done() __dead to avoid false positives.
There are two more warnings from the analyzer but I'm fairly certain
that they are false positives.
- todd
Index: closu
On Sun, Nov 30, 2014 at 03:40:58PM -0800, Dave Huseby wrote:
>
> Status update...
>
> I've been working on porting Rust over to OpenBSD by building a Rust
> cross-compiler for Linux that can target i386-unknown-openbsd and
> x86_64-unknown-openbsd. The largest roadblock on OpenBSD is the lack
>
Hi
Found on OpenBSD/5.5, reproduced in OpenBSD-current:
I have a problem when authenticating a user whose
username is bigger than 31 chars:
expected - auth longemailabcde@abcdef.ghijklmno:
smtp-in: Authentication failed for user
longemailabcde@abcdef.ghijklmno on session 9b03fc72ca051521
got -
On Mon, Dec 01, 2014 at 10:24:33AM +, Stuart Henderson wrote:
> ports/graphics/xsane crashes at startup with an overlapping memcpy.
> However all it is doing here is an snprintf. Any ideas? Could the
> problem be in snprintf rather than xsane?
>
> (gdb) r
> Starting program: /usr/local/bin/xs
ports/graphics/xsane crashes at startup with an overlapping memcpy.
However all it is doing here is an snprintf. Any ideas? Could the
problem be in snprintf rather than xsane?
[...]
#7 0x08fdaf1b2149 in xsane_device_dialog () at xsane.c:4997
[...]
4997 snprintf(buf, sizeof(buf),
ports/graphics/xsane crashes at startup with an overlapping memcpy.
However all it is doing here is an snprintf. Any ideas? Could the
problem be in snprintf rather than xsane?
(gdb) r
Starting program: /usr/local/bin/xsane
Program received signal SIGABRT, Aborted.
0x09006ef0070a in kill () a
Not sure how much of an issue this would be, WSAPoll() is only
available on Windows Vista and above.
On Mon, 1 Dec 2014 14:10:44 +0800
Dongsheng Song wrote:
> Cool !
>
> I can see you do lot's of update on select->poll conversions.
> The code become more and more complex since you want it works
On Mon, Dec 1, 2014 at 2:25 PM, Brad Smith wrote:
> There is a URL posted at the bottom of that page that points out how it
> is broken and should not be used.
>
I don't think we must distinguish the timeout errors and connection
errors in the OpenSSL(1) tool, report ‘connection failed (or timeou
16 matches
Mail list logo