openssl asks for user input during Gutsy->Hardy

Bug #182446 reported by Ryan Prior on 2008-01-13
Affects Status Importance Assigned to Milestone
openssl (Ubuntu)

Bug Description

During the upgrade from Gutsy to Hardy, I came in to check on my computer's progress and noticed that it had been halted by libssl, which was asking which services I would like to restart in order to take advantage of updates to libssl. The installer should handle this quietly, either restarting all the needed services or just restarting nothing. During a normal package upgrade that behaviour might be wanted, but not during a dist-upgrade which ends with a system reboot anyway.

(The original bug report said libssh instead of libssl, but as discussed below, it seems that I took incorrect notes during install and wrote libssh incorrectly)

Laurent Bigonville (bigon) wrote :

Are you sure it was libssh? and not libssl?

Changed in libssh:
assignee: nobody → bigon
status: New → Incomplete
Ryan Prior (ryanprior) wrote :

The note I wrote during the process says ssh, but I might have written that down erroneously. However, there is no package called "libssl", so I am somewhat convinced that it is indeed libssh.

Changed in libssh:
status: Incomplete → Confirmed
Laurent Bigonville (bigon) wrote :

the libssh has no such mechanism for restarting services (I'm the debian maintainer of libssh :p)

The question should have been asked by openssl

btw libssh has nothing todo with the ssh deamon

Changed in libssh:
assignee: bigon → nobody
status: Confirmed → New
Ryan Prior (ryanprior) on 2008-01-13
description: updated

I ran into this as well. update manager did not notice the prompt (it was only visible in the "Terminal" output). In the past, we'd altered openssl's prompting levels to auto-restart when running within update-manager. Perhaps that patch was accidentally dropped?

Changed in openssl:
importance: Undecided → Medium
milestone: none → ubuntu-8.04
status: New → Confirmed
James Westby (james-w) wrote :


This appears to be a duplicate of bug 91814. Would that
be correct? Does this need to be fixed in more than
once version of libssl?



Steve Langasek (vorlon) wrote :

yes, same bug report; marking as a duplicate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers