On Mon, Jul 14, 2014 at 4:25 AM, Gustav Fransson Nyvell gus...@nyvell.se
wrote:
I'm looking at 5.5-current. I'm forking inside a lib and I want to change
the forks cmd or argv[0]. I mean, what you see as command in ps or top.
I've looked at setproctitle.
There are two different things that
On Sat, Jul 12, 2014 at 01:10:38PM -0400, Ted Unangst wrote:
On Fri, Jul 11, 2014 at 08:11, Ted Unangst wrote:
I also think there's one simple case that can be added: the MMAP call
at the bottom of map().
On further inspection, I think this needed a slight reordering to be
safe.
I
Anyway, I still like the idea, but I wonder if now right after the
hackathon is the right time. But please continue experimenting with
this during my vacation ;-) Changing the error message would be a good
thing, to distinguish the various calls to munmap.
Timing is bad. We need to fix the
Hello,
I recently tried to rebuild a complete gentoo system with libressl, if
you haven't seen, I've blogged about it:
https://blog.hboeck.de/archives/851-LibreSSL-on-Gentoo.html
One of the issues that popped up was in dovecot. Compilation failed due
to missing constants of the compression
Hi hanno, we've been discussing it extensively here. It's been out
and back in and out and back in ;)
the problem is there are multiple pieces of software, all of which
test for this stuff rather badly. and either
way we do it seems to break things.
On Mon, Jul 14, 2014 at 6:55 AM, Hanno Böck
Ted Unangst tedu at tedunangst.com writes:
Any system that actually uses egd is so hopelessly broken you
are better off just turning around and walking away. No software in
2014 should be using egd; no software in 2014 should support using egd
by accident.
This is wrong. The egd protocol is
The C standard mandates that static be first.
From ISO/IEC 9899:1999 and 9899:201x,
6.11.5 - Storage-class specifiers:
The placement of a storage-class specifier other than at the
beginning of the declaration specifiers in a declaration is
an obsolescent feature.
and -Wextra
Sorry to break the threading, but I already expunged the original
message..
Re: http://marc.info/?l=openbsd-techm=140529530814733w=2
The second and third hunk should use mallocarray() instead of malloc()
in my eyes.
sizeof(Elf_Phdr) as type just doesnt make sense to me.
Hope not everyone is
Hi Jan,
On Sun, Jul 13, 2014 at 08:30:38PM +0200, Jan Engelhardt wrote:
On Sunday 2014-07-13 13:07, Bob Beck wrote:
We have released an update, LibreSSL 2.0.1
As noted before, we welcome feedback from the broader community.
Something that I have noticed is that the shared libraries
On Monday 2014-07-14 20:16, Toni Mueller wrote:
Hi Jan,
On Sun, Jul 13, 2014 at 08:30:38PM +0200, Jan Engelhardt wrote:
On Sunday 2014-07-13 13:07, Bob Beck wrote:
We have released an update, LibreSSL 2.0.1
As noted before, we welcome feedback from the broader community.
Something that I
What problem are you trying to solve here.
On Mon, Jul 14, 2014 at 12:28 PM, Jan Engelhardt jeng...@inai.de wrote:
On Monday 2014-07-14 20:16, Toni Mueller wrote:
Hi Jan,
On Sun, Jul 13, 2014 at 08:30:38PM +0200, Jan Engelhardt wrote:
On Sunday 2014-07-13 13:07, Bob Beck wrote:
We have
If you look at the diff that went in already, it's using mallocarray.
It wouldn't even compile otherwise.
To answer a number of questions about this all at once. No. we don't sign
releases with GnuPG or OpenPGP.
GnuPG alone is a compressed tarball of 4.2 MB of code I have occasionally
had to glance at. I do not have enough
energy in my life to clean up two poorly written crypto code bases. The
world
On Monday 2014-07-14 20:34, Bob Beck wrote:
What problem are you trying to solve here.
Pristine libtool does not pass -m 644, and default (GNU) install
defaults to mode 755 when not specifying anything else.
I am trying to figure out why OpenBSD would be patching libtool
and adding
+case
2014-07-14 21:30 GMT+02:00 Jan Engelhardt jeng...@inai.de:
On Monday 2014-07-14 20:34, Bob Beck wrote:
What problem are you trying to solve here.
Pristine libtool does not pass -m 644, and default (GNU) install
defaults to mode 755 when not specifying anything else.
I am trying to figure
Hey Ted,
I should have been more clear in my previous email, but would it be
possible
to also revert OPENSSL_VERSION_NUMBER back to 0x1000107fL (or
0x1000108fL)?
This way LibreSSL would work as a drop-in replacement without
applications
needing to add explicit support for LibreSSL.
Ideas
Something I forgot about during the discussion about the diff for dump:
The manpage doesn't mention yet that we can specify the duid on the
command line now.
--- sbin/dump/dump.8.orig Mon Jul 14 23:57:37 2014
+++ sbin/dump/dump.8Mon Jul 14 23:59:09 2014
@@ -288,8 +288,10 @@
is either a
On Wed, Jul 02, 2014 at 10:36:25PM -0700, Matthew Dempsky wrote:
According to the Intel 64 and IA-32 Architectures Software
Developer's Manual, CPUID.8001H:EDX.Page1GB [bit 26] indicates
whether 1-GByte pages are supported with IA-32e paging.
I think the diff below adds support for
It's also here :)
8--
untrusted comment: LibreSSL Portable public key
RWQg/nutTVqCUVUw8OhyHt9n51IC8mdQRd1b93dOyVrwtIXmMI+dtGFe
On Mon, Jul 14, 2014 at 8:52 PM, Bob Beck b...@obtuse.com wrote:
Once we are back in North America where we can do it (the master signature
box is airgapped) in
On Mon, Jul 14, 2014 at 11:44:30AM -0400, Jean-Philippe Ouellet wrote:
The C standard mandates that static be first.
Of course I forgot something... This is the hunk that made me
notice in the first place. Found while porting signify to osx.
Index: lib/libc/hash/sha2.c
20 matches
Mail list logo
