The fixed version appears to have been synced from Debian, so I am
closing this bug.
** Changed in: sash (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: sash (Ubuntu)
Assignee: (unassigned) => JC Hulce (soaringsky)
--
You received this bug notification because you are a me
** Changed in: sash (Ubuntu)
Status: New => Confirmed
--
sash creates 'sashroot' account
https://bugs.launchpad.net/bugs/234434
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Changed in: sash (Debian)
Status: Unknown => Fix Released
--
sash creates 'sashroot' account
https://bugs.launchpad.net/bugs/234434
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Bug watch added: Debian Bug tracker #410758
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410758
** Also affects: sash (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410758
Importance: Unknown
Status: Unknown
--
sash creates 'sashroot' account
https://bugs.la
Even worse:
harden-environment has sash as dependency.
This is not good.
--
sash creates 'sashroot' account
https://bugs.launchpad.net/bugs/234434
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
I wanted to add that when sash is purged, it does not remove the
sashroot account. -- However the shell gets changed to bash.
This means that if packages are being monitored by regular daily reports
pulled from a dpkg -l list, you can get around this showing up in logs
by installing sash and immed
Correcting the package this affects.
** Changed in: sash (Ubuntu)
Sourcepackagename: friendly-recovery => sash
--
sash creates 'sashroot' account
https://bugs.launchpad.net/bugs/234434
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
