The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: upstart (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as Won't Fix.
** Changed in: upstart (Ubuntu Saucy)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've just noticed that all my new files are becoming readable by anybody,
because the default umask is 022, and my personal umask, set in .profile to 027
is getting ignored. Is this a consequence of this bug?
If so, please fix. Exposing data in this way is not nice at all and this is
not a
There may be two different things going on here. The bug was fixed in
upstart 1.11, some time ago.
On the other hand, I noticed (as you did) in the last few days that my
new files were getting a umask of 0027, contrary to the upstart profile
I had installed. Because of the timing, I suspect the
@keibak -- Why do you say it is a hack?
@dav.garcia -- Originally you were reluctant to do this with the package:
Install with:
sudo dpkg -i upstart_1.11-*.deb
Reboot
Do I understand that you were successful with the above install?
--
You received this bug notification because you are a
@bab1
I think that is not a proper way to replace a package. If I install it
manually from another release cycle or even distribution, I bypass any
security updates from the apt repository.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It's straightforward to install packages from another distribution or
release with updates. See https://wiki.debian.org/AptPreferences
This is a relatively minor bug with a straightforward workaround, so it
has not been backported to saucy, which in any case only has a 9-month
life. It is fixed
Well. I didn't (and still don't) think of it as a hack. Thank you
Ubuntu developers (@clint-fewbar et al)for at least updating for Trusty
is such a way that we can just apply the package to earlier versions
(13.10). Boo for creating the problem in the first place.:)
I asked because I am
I didn't say minor error (I would prefer minor problem), I said a
minor bug. The problem is indeed major (in my case, it risked serious
information leakage), but the bug is minor (because it has a simple and
effective workaround).
Note that the fact that the trusty package can be installed in
I didn't say that YOU said any thing in my previous post. In fact I
said: Altering the way umask works in the end is not a minor error at
all.
The altering was by Ubuntu Devs. and I agree it is not a minor issue,
error , problem or bug.
Thanks for the considered thoughts.
--
You received
I didn't say that YOU said any thing in my previous post: by making
the comment Altering the way umask works in the end is not a minor
error at all in a paragraph addressed to an earlier comment of mine,
you implied that I had described it as a minor error.
In any case, I was attempting to
Altering the way umask works in the end is not a minor error at all
in a paragraph addressed to an earlier comment of mine, you implied that
I had described it as a minor error.
Actually I never saw that comment. :-)
Your good, I'm good. I'll shut up too!
--
You received this bug
FWIW I have managed to fix this issue by manually installing upstart
1.11-0ubuntu1 for Trusty, as published here:
https://launchpad.net/ubuntu/trusty/+package/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@dav.garcia
That's not a solution, but a hack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications about this bug go to:
** Changed in: upstart
Status: Fix Committed = Fix Released
** Also affects: upstart (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Excerpts from Keith Baker's message of 2013-12-03 06:13:24 UTC:
Clint Byrum (clint-fewbar) wrote on 2013-12-02:
Please click Nominate for series
There's no such button.
Ahh, this is one of those really weird, annoying launchpad bugs. This is
because you're viewing it in the upstart,
Thanks for the hint, but I'm not eligible to nomiate for the bug.
This is just ridiculous. The damn ubuntu bureaucracy makes me want to
change distribution more and more!
BTW: A bug in the bug tracker. Notice the irony?
--
You received this bug notification because you are a member of Ubuntu
Excerpts from Keith Baker's message of 2013-12-03 19:32:26 UTC:
Thanks for the hint, but I'm not eligible to nomiate for the bug.
This is just ridiculous. The damn ubuntu bureaucracy makes me want to
change distribution more and more!
BTW: A bug in the bug tracker. Notice the irony?
I
Thanks again!
I'd really appreciate the fix in the current release: saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications
Ok Keith, thanks for sticking with it. Note that backporting non-
Critical fixes to Saucy will likely be a low priority for Ubuntu
developers, as it is only supported for 9 months. So if you can isloate
the patch, and build/backport it yourself, that will be much easier as
the developers will just
I'm afraid that that technical hurdle is a bit too high for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications about this
Clint Byrum (clint-fewbar) wrote on 2013-12-02:
Please click Nominate for series
There's no such button.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's
Can someone add the package upstart - 1.11-0ubuntu1 to ubuntu backports?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications
btw. I do not feel this bug as low urgency, if upstart granted other users at a
multiuser os by himself read access to my home directory.
Someone else may not recognize this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Excerpts from asgard2's message of 2013-12-01 10:49:45 UTC:
Can someone add the package upstart - 1.11-0ubuntu1 to ubuntu backports?
We don't use backports for important bug fixes. We use the stable
release updates (SRU) process.
Please click Nominate for series and choose a still supported
Is there a workaround for saucy, since this bug makes it impossible to have a
shared subversion repository for different users. And we cant wait for trusty.
A global workaround, that also works in a KDE environment would be preffered
--
You received this bug notification because you are a
On 19 November 2013 15:21, Andreas Blochberger
1240...@bugs.launchpad.net wrote:
Is there a workaround for saucy, since this bug makes it impossible to have a
shared subversion repository for different users. And we cant wait for trusty.
A global workaround, that also works in a KDE
This bug was fixed in the package upstart - 1.11-0ubuntu1
---
upstart (1.11-0ubuntu1) trusty; urgency=low
[ Dmitrijs Ledkovs ]
* Run as much test-suites as possible, before exiting with failure.
[ James Hunt ]
* New upstream release.
- the global environment is now
Thanks very much for this, all concerned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications about this bug go to:
** Branch linked: lp:~jamesodhunt/ubuntu/trusty/upstart/1.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications about this bug
** Changed in: upstart
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications about this
Where would the override-file have to be placed as a workaround? I tried
~/.config/upstart as per the upstart session documentation and even
/usr/share/upstart/sessions but to no avail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Override file is for X session, e.g. for GNOME: ~/.config/upstart/gnome-
session.override
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage
does this bug also effect settings in /ets/login.defs ?
i specified UMASK 027 there and it has no effect any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart
See above: upstart resets the umask when it starts the user jobs
environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage
This also seems to be the cause of my umask setting being ignored. My
umask is set through pam_umask and the GECOS field of my user.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
** Branch linked: lp:~jamesodhunt/upstart/bug-1240686
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240686
Title:
Upstart overrides the user's umask
To manage notifications about this bug go to:
Actually, '--no-inherit-umask' is not required: the existing '--no-
inherit-env' is sufficient'.
** Changed in: upstart
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Reuben - thank you for reporting this bug and making Ubuntu better!
You are right: Upstart does reset the umask to 022 in a jobs environment
unless the umask stanza has been specified in a job. This is correct
behaviour for Upstart running as PID 1 but when running as a Session
Init it really
39 matches
Mail list logo
