Bug#839067: shellinabox: Cannot read valid certificate

2016-10-18 Thread Noel Torres
On Thursday, 6 de October de 2016 21:42:54 Marc Singer escribió:
> While it is a serious issue that shellinabox is unable to read a
> certificate, we don't have evidence that this is caused by the program.
> 
> To investigate the cause, the OP should review the permissions of the
> cert and all of the directories in the path.  Usually, the problem is
> that the ID of shellinabox cannot read the cert because it is denied
> access somewhere along the path.

The issue is that no cert were installed during installation, so shellinabox 
could not start. Permissions were correct, or they should be, as the directory 
was created by the package.

IF the cert should always be installed by the admin, this should be noted in 
the docs, but that is not written in any file on /usr/share/doc/shellinabox so 
any admin will assume the server should "just start", as any other server like 
sshd or apache does.

Regards

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.



Bug#839067: shellinabox: Cannot read valid certificate

2016-10-06 Thread Marc Singer
While it is a serious issue that shellinabox is unable to read a 
certificate, we don't have evidence that this is caused by the program.


To investigate the cause, the OP should review the permissions of the 
cert and all of the directories in the path.  Usually, the problem is 
that the ID of shellinabox cannot read the cert because it is denied 
access somewhere along the path.




Bug#839067: shellinabox: Cannot read valid certificate

2016-09-28 Thread Noel David Torres Taño
Package: shellinabox
Version: 2.14-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Just installing the package

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   * What was the outcome of this action?
Server did not start, with message:
Cannot read valid certificate from "/var/lib/shellinabox/certificate.pem". 
Check file permissions and file format.

ls of that file shows that it doesn't exist

   * What outcome did you expect instead?
Server starting in default port (to be changed later on).

*** End of the template - remove these template lines ***


-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 1.0 (jessie)
Release:1.0
Codename:   jessie
Architecture: x86_64

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages shellinabox depends on:
ii  adduser  3.113+nmu3
ii  libc62.23-1
ii  libpam0g 1.1.8-3.1+deb8u1+b1
ii  libssl1.0.0  1.0.2d-1
ii  lsb-base 4.1+devuan2
ii  zlib1g   1:1.2.8.dfsg-2+b1

shellinabox recommends no packages.

Versions of packages shellinabox suggests:
ii  openssl  1.0.1k-3+deb8u5

-- Configuration Files:
/etc/default/shellinabox changed [not included]

-- debconf information:
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at 
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm line 
30.