This seems to affect 2:4.3.11+dfsg-0ubuntu0.16.04.2 too, as I had
exactly the same issue and I fixed it by downgrading everything sourced
from samba to version 2:4.3.11+dfsg-0ubuntu0.16.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
by invoking the executable with the help of the dynamic Linux loader.
Although you are right, in real world vulnerability exploitation you
often don't control much of the environment, sometimes even the way an
executable gets executed.
The reason most people mount tmp with noexec is that it is
The problem here is not that I never entered a password, is that I've
never been asked to. I fail to understand why this bug is invalid, but I
guess you know better.
Just to be sure you understood the matter correctly, I installed
mythbuntu-control-center, which installed a lot of myth-related
Public bug reported:
The install has been triggered via mythbuntu-control-center, executed in
an existing XUbuntu install. I guess the database (and the correct
access data) should be a dependency, but I'm not sure if this should be
managed by dpkg and how.
ProblemType: Package
DistroRelease:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/804102
Title:
mythexport fails to install because of missing MySQL database
To manage notifications about this bug go to:
Please let the user decide if using a /tmp noexec mount point is more secure or
not.
I think it is, for many reasons, and I'm a security analyst. Of course it can
bring a false sense of security, like everything else, but do we give up
firewalls, IDS and even passwords for the same reason? No
