Re: invalid ELF class 2; expected 1

2019-06-09 Thread Emmanuel Dreyfus
Emmanuel Dreyfus  wrote:

> # ldd /usr/pkg/bin/screen-4.6.2
> ldd: /usr/pkg/bin/screen-4.6.2: invalid ELF class 2; expected 1
> 
> What does that mean? It seems to happen on amd64 but not on i386.

Replying to myself: This is an amd64 binary on a i386 userland, as a
result of a botched update (i386 release unpacker on top of an amd64
system).

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org


invalid ELF class 2; expected 1

2019-06-09 Thread Emmanuel Dreyfus
After upgrading to NetBSD 8.1, a screen binary built for NetBSD 8.0
ceased to work:

As non privilegied user:
$ /usr/pkg/bin/screen-4.6.2
/bin/sh: Can't open /usr/pkg/bin/screen-4.6.2

As root (screen is setuid with mode 4555)
# /usr/pkg/bin/screen-4.6.2
/bin/sh: Cannot execute ELF binary /usr/pkg/bin/screen-4.6.2
# ldd /usr/pkg/bin/screen-4.6.2
ldd: /usr/pkg/bin/screen-4.6.2: invalid ELF class 2; expected 1

What does that mean? It seems to happen on amd64 but not on i386.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org


Re: bozohttpd letsencrypt not working with firefox/chrome

2019-06-09 Thread Mayuresh
On Sun, Jun 09, 2019 at 08:38:39PM +0530, Mayuresh wrote:
> It's a bit strange, but with https enabled, "index.html" is returned by
> default only for the home page, when the URL doesn't specify it. For all
> other pages, different browsers give different errors. Some versions of
> firefox actually work (may be by trying to suffix index.html themselves).

Giving -x index.html option (which I think should not be required) the
problem is solved.

Bug?

Mayuresh


Re: bozohttpd letsencrypt not working with firefox/chrome

2019-06-09 Thread Mayuresh
On Sun, Jun 09, 2019 at 08:09:21PM +0530, Mayuresh wrote:
> Ok, I need -z. Thanks[1].

It's a bit strange, but with https enabled, "index.html" is returned by
default only for the home page, when the URL doesn't specify it. For all
other pages, different browsers give different errors. Some versions of
firefox actually work (may be by trying to suffix index.html themselves).

With explicit index.html all pages work in all browsers.

Is that having some reasoning or is it a bug?

Mayuresh


Re: bozohttpd letsencrypt not working with firefox/chrome

2019-06-09 Thread Mayuresh
On Sun, Jun 09, 2019 at 08:01:23PM +0530, Mayuresh wrote:
> I have started httpd with  -Z   option.

Ok, I need -z. Thanks[1].

[1] https://atomicules.co.uk/2017/07/21/Now-serving-https-as-well.html

Mayuresh


bozohttpd letsencrypt not working with firefox/chrome

2019-06-09 Thread Mayuresh
I am trying to httpsize a NetBSD 8.1 based website.

Got the certificate from letsencrypt using security/py-certbot

I have started httpd with  -Z   option.

When accessing this site firefox says:

An error occurred during a connection to flowervalleywanawadi.in. Cannot
communicate securely with peer: no common encryption algorithm(s). Error
code: SSL_ERROR_NO_CYPHER_OVERLAP 

Tried chrome on android, it says:

server sent an invalid response
ERR_INVALID_REDIRECT

On the other hand, a stock browser on mobile phone is able to connect with
the site with no error!

What could the way out?

Mayuresh