there is a problem with
in setup-1.9.2-1 package.
selecting what umask to set
002 or 022
it checkes for iser id and group id.
If a process has effective user id or effective group id
different a wrong pernission may be set.
(for example if a user does
root will get 002 umask)
A fix to this problem is to test effective UID and effective
GID, not UID and GID as it is now.
Um, id already does that.
If you just invoke 'su', it's not a login shell, so
/etc/profile is never read, so the umask is inherited
from the parent process.