Perhaps something like this somewhere in make-ssl-cert:
if [ ! -d "$HOME" ]; then
temphome="$(mktemp -d)"
cleanup () {
rm -rf "$temphome"
}
trap cleanup EXIT HUP INT QUIT TERM
export HOME="$temphome"
fi
** Summary changed:
- package ssl-cert 1.0.14-0ub
this has an effect on all packages (eg. lighttpd) that use a ssleay.cnf
and may create or update certificates upon installation/upgrade
--
make-ssl-cert fails if HOME is unset or empty
https://bugs.launchpad.net/bugs/250400
You received this bug notification because you are a member of Ubuntu
Bug
well you can try ... if used in an environment where there is no homedir
set it does fail - no certificate is created or updated.
** Changed in: ssl-cert (Ubuntu Intrepid)
Status: Won't Fix => New
--
package ssl-cert 1.0.14-0ubuntu2.1 failed to install/upgrade:
https://bugs.launchpad.net
Hi,
/tmp is a really bad idea and a security hole, if the name .rnd is
used at least.
I think having it shared between users would perhaps be a security
hole as well.
Having it use a proper tmpfile may be possible, but it may still be at
risk.
I'm not sure the file is required though, so it may
well ... i am sorry - it seems i have made an error here. I don't know
exactly what i did wrong but i retested everything and fixing the path
is not enough.
the real problem is the ssleay.cnf that is being used to generate the standard
pem file
it sets the RANDFILE variable to $ENV::HOME/.rnd
if
Per discussion with james_w on IRC, it's a reasonable expectation for
shells invoking dpkg to have /sbin and /usr/sbin in their path (for
example, openssl will fail to install in the preconfiguration stage if
the path does not include /sbin and /usr/sbin). Marking this as invalid.
Please re-open if
It fails in an automatic upgrade/installation environment because the PATH
variables are different than if you're using a shell. /usr/sbin is not included
if a cron runs the upgrade (or installation) - therefor the command
"make-ssl-cert" fails to create the files (because the file is not execut
** This bug has been marked a duplicate of bug 250399
package update-manager 1:0.87.27 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error
code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
** This bug is no longe
That's because ssl-cert 1.0.14-0ubuntu2.1 fails to install:
Richte ssl-cert ein (1.0.14-0ubuntu2.1) ...
dpkg: Fehler beim Bearbeiten von ssl-cert (--configure):
Unterprozess post-installation script gab den Fehlerwert 1 zurück
** Changed in: ssl-cert (Ubuntu)
Status: New => Confirmed
--
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16207486/Dependencies.txt
** Attachment added: "VarLogDistupgradeAptlog.gz"
http://launchpadlibrarian.net/16207487/VarLogDistupgradeAptlog.gz
** Attachment added: "VarLogDistupgradeApttermlog.gz"
http://launchpadlibra
10 matches
Mail list logo
