Re: elinks creates file whose name is the contents of elinks.conf

2014-06-02 Thread Stuart Henderson
On 2014/06/01 14:02, Stuart Henderson wrote: On 2014/05/31 13:47, Jérémie Courrèges-Anglas wrote: Stuart Henderson st...@openbsd.org writes: Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back to upstreams though, as they *do* need

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-02 Thread Jérémie Courrèges-Anglas
Stuart Henderson st...@openbsd.org writes: On 2014/06/01 14:02, Stuart Henderson wrote: On 2014/05/31 13:47, Jérémie Courrèges-Anglas wrote: Stuart Henderson st...@openbsd.org writes: Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-02 Thread Stuart Henderson
On 2014/06/02 13:24, Jérémie Courrèges-Anglas wrote: The *LibreSSL* documentation does, the original RAND_load_file.pod doesn't advise against using it. argh. In that case, this fix won't be sufficient for upstream (assuming they care about Windows). Also our rand.pod (RAND(3)) still

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-02 Thread Jérémie Courrèges-Anglas
Stuart Henderson st...@openbsd.org writes: On 2014/06/02 13:24, Jérémie Courrèges-Anglas wrote: The *LibreSSL* documentation does, the original RAND_load_file.pod doesn't advise against using it. argh. In that case, this fix won't be sufficient for upstream (assuming they care about

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-01 Thread Edd Barrett
On Sat, May 31, 2014 at 01:47:12PM +0200, Jérémie Courrèges-Anglas wrote: Stuart Henderson st...@openbsd.org writes: Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back to upstreams though, as they *do* need this with OpenSSL. [...] I

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-01 Thread Stuart Henderson
On 2014/06/01 12:47, Edd Barrett wrote: On Sat, May 31, 2014 at 01:47:12PM +0200, Jérémie Courrèges-Anglas wrote: Stuart Henderson st...@openbsd.org writes: Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back to upstreams though, as they

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-01 Thread Stuart Henderson
On 2014/05/31 13:47, Jérémie Courrèges-Anglas wrote: Stuart Henderson st...@openbsd.org writes: Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back to upstreams though, as they *do* need this with OpenSSL. [...] I agree that more

Re: elinks creates file whose name is the contents of elinks.conf

2014-06-01 Thread Ted Unangst
On Sun, Jun 01, 2014 at 13:43, Stuart Henderson wrote: An alternative would be to implement stubs in libressl returning -1... We've decided these APIs are simply too poisonous to remain, in any form.

Re: elinks creates file whose name is the contents of elinks.conf

2014-05-31 Thread Jérémie Courrèges-Anglas
Stuart Henderson st...@openbsd.org writes: Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back to upstreams though, as they *do* need this with OpenSSL. [...] I agree that more lines should be deleted. Is this clear enough? Index: Makefile

Re: elinks creates file whose name is the contents of elinks.conf

2014-05-30 Thread Edd Barrett
On Thu, May 22, 2014 at 12:07:33AM +0100, Zé Loff wrote: I know, that subject's line is too long, but I didn't manage to phrase that in a shorter form. On the upside, it pretty much tells the whole story: elinks is creating a file on ~ whose name is the contents of ~/elinks/elinks.conf. I

Re: elinks creates file whose name is the contents of elinks.conf

2014-05-30 Thread Stuart Henderson
Awesome! We probably need to delete more lines. Not sure a good way to feed this sort of change back to upstreams though, as they *do* need this with OpenSSL. On 2014/05/30 18:15, Edd Barrett wrote: On Thu, May 22, 2014 at 12:07:33AM +0100, Zé Loff wrote: I know, that subject's line is too

Re: elinks creates file whose name is the contents of elinks.conf

2014-05-22 Thread Edd Barrett
Ouch, I'll look at that as soon as I find some time. On 22 May 2014 00:08, Zé Loff zel...@zeloff.org wrote: I know, that subject's line is too long, but I didn't manage to phrase that in a shorter form. On the upside, it pretty much tells the whole story: elinks is creating a file on ~ whose

elinks creates file whose name is the contents of elinks.conf

2014-05-21 Thread Zé Loff
I know, that subject's line is too long, but I didn't manage to phrase that in a shorter form. On the upside, it pretty much tells the whole story: elinks is creating a file on ~ whose name is the contents of ~/elinks/elinks.conf. $ cat .elinks/elinks.conf set