On Wednesday, 28 de September de 2016 15:36:27 Marc Singer escribió: > Just this week, I saw a similar error from shellinabox. I was replacing > the default self-signed certificates with letsencrypt certificates.
I used a certificate I have for the same machine for other uses :) > > It appears, from your messages, that shellinabox is unable to create or > unable to read the self-signed certificates. In this case, the problem was creating it. > > The first thing to do is look at the /var/lib/shellinabox directory. > What is the ownership? Is there a certificate.pem? For example: > > # ls -ld /var/lib/shellinabox/ > drwxr-xr-x 2 shellinabox shellinabox 4096 Sep 25 20:00 /var/lib/shellinabox > # ls -l /var/lib/shellinabox/certificate.pem > -rw------- 1 shellinabox shellinabox 2811 Sep 6 18:04 > /var/lib/shellinabox/certificate.pem root@host:~# ls -ld /var/lib/shellinabox/ drwxr-xr-x 2 shellinabox shellinabox 4096 sep 28 13:18 /var/lib/shellinabox/ root@host:~# ls -l /var/lib/shellinabox/certificate.pem -rw-r--r-- 1 root root 7655 sep 28 13:01 /var/lib/shellinabox/certificate.pem Note that this certificate.pem was the one I copied there. Directory was empty after installation. > > The most likely culprit for your messages is that shellinabox cannot > write or read the certificate. Let us know what you find. Thanks Noel er Envite -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? OpenPGP key: 1586 50C8 7DBF B050 DE62 EA12 70B4 00F3 EEC7 C372 Spiral galaxies always have at least TWO arms.
signature.asc
Description: This is a digitally signed message part.
