On Thu, Dec 01, 2005 at 03:32:45AM +0200, Mikko Rapeli wrote:
fakeroot combined with dpkg-source uses original source package permissions.
If the original source has insecure permissions on files and/or directories
dpkg-source -x should override them with umask, but:
snip
What I ment to
Mikko Rapeli wrote:
On Thu, Dec 01, 2005 at 03:32:45AM +0200, Mikko Rapeli wrote:
fakeroot combined with dpkg-source uses original source package permissions.
If the original source has insecure permissions on files and/or directories
dpkg-source -x should override them with umask, but:
On Thu, Dec 01, 2005 at 11:34:15AM +0100, Martin Schulze wrote:
Thanks for your report, but I'd rather consider this a
if-use-user-wants-to-shoot-in-both-feet-they-should error. Why would
anybody would want to run dpkg-source inside a fakerooted shell?
You can't exploit root or another user,
Package: dpkg
Version: 1.13.11.0.1
Severity: important
I try to create a package that would provides another one.
To test the case, you can get a package, change its name and make it
provide the original one.
When my package is created, I try to install it, but I get some
dependency problem :
On Sat, Aug 20, 2005 at 11:32:07PM +0400, Nikita V. Youshchenko wrote:
Package: dpkg-cross, devscripts, dpkg-dev
Severity: normal
If dpkg-cross is installed, it provides it's own dpkg-buildpackage,
which potentially replaces the *_${arch}.changes file with
*_source+${arch}.changes.
5 matches
Mail list logo
