[Bug 1278285] Re: git send-email fails SSL certificate verification

[Sedat Dilek]

I am using git (1:1.9.1-0ppa1~precise1) here on Ubuntu/precise AMD64 and
was not able to send a patch to linux-fsdevel via GoogleMail.

The above workaround helped me (for the sake of completeness the snippet
from my dot-gitconfig):

[ ~/.gitconfig]
...
[sendemail]
smtpserver = smtp.gmail.com
smtpserverport = 587
smtpencryption = tls
smtpuser = sedat.di...@gmail.com
smtpsslcertpath = '/etc/ssl/certs'
...

Anders can you offer a backport, please. THX in advance.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278285

Title:
  git send-email fails SSL certificate verification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1278285/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1278285] Re: git send-email fails SSL certificate verification

[Sedat Dilek]

Reading and verifying above bug-reports I have here in 'git-send-
email.perl':

[ /usr/lib/git-core/git-send-email ]
...
sub ssl_verify_params {
...
if (!defined $smtp_ssl_cert_path) {
# use the OpenSSL defaults
return (SSL_verify_mode => SSL_VERIFY_PEER());
...

So, the real problems seems to be to have a higher version of libio-
socket-ssl-perl (here on precise: 1.53-1).

>From git (1.9.1-1) changelog:
...
  [ Jonathan Nieder ]
  * git-email: Recommends: libio-socket-ssl-perl (>= 1.951) since
earlier versions do not use OpenSSL's defaults when ca_path
and ca_file are unset.
...

- Sedat -

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278285

Title:
  git send-email fails SSL certificate verification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1278285/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1278285] Re: git send-email fails SSL certificate verification

[Sedat Dilek]

What is your suggestion?
Fix local/global gitconfig?

Or revert that change?
...
-   $smtp_ssl_cert_path = "/etc/ssl/certs";
+   # use the OpenSSL defaults
+   return (SSL_verify_mode => SSL_VERIFY_PEER());
...

I can understand your concerns in case of a higher version of libio-
socket-ssl-perl, but a user-friendly solution would be kind for git-
precise-ppa users.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278285

Title:
  git send-email fails SSL certificate verification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1278285/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1278285] Re: git send-email fails SSL certificate verification

[Sedat Dilek]

Without the smtpsslcertpath-line in my local ~/.gitconfig and the new
git-core packages everything works like expected.

[ /etc/apt/sources.list.d/git-core-candidate-precise.list ]
   deb http://ppa.launchpad.net/git-core/candidate/ubuntu precise main
deb-src http://ppa.launchpad.net/git-core/candidate/ubuntu precise main

$ dpkg -l | grep git-core
ii  git-core  1:1.9.1-1~ppa0~precise2   
  fast, scalable, distributed revision control system 
(obsolete)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278285

Title:
  git send-email fails SSL certificate verification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1278285/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1278285] Re: git send-email fails SSL certificate verification

[Sedat Dilek]

Hmm, your changelog has no reference to this bug-no.
And I would name the Ubuntu package libio-socket-ssl-perl instead of 
IO::Socket::SSL.

[ Snip ]
  * Revert commit v1.8.5.5~5^2 (send-email: /etc/ssl/certs/ directory may
not be usable as ca_path), which requires IO::Socket::SSL 1.951, and
remove the associated versioned Recommends.
[Snap]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278285

Title:
  git send-email fails SSL certificate verification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1278285/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] [NEW] Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat-dilek]

Public bug reported:

Hi,

I am observing a lot of "ICMPv6 RA: ndisc_router_discovery() failed to add 
default route" in my logs.
After a fresh reboot:

$ dmesg | grep "ICMPv6 RA: ndisc_router_discovery() failed to add default 
route." | wc -l
46

First, I thought this is a kernel issue, but than I found a bug-report
in the Red Hat BTS in [1].

Just FYI: I am on Linux-3.4-rc4 - with the original Ubuntu/precise
kernel I haven't seen this which is linux-image-3.2.0-23-generic
(3.2.0-23.36).

- Sedat -

[1] https://bugzilla.redhat.com/show_bug.cgi?id=785772

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu3
Uname: Linux 3.4.0-rc4-4-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
Date: Wed Apr 25 08:40:50 2012
ExecutablePath: /usr/sbin/NetworkManager
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
IpRoute:
 default via 192.168.178.1 dev wlan0  proto static 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.22  
metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
 myCastle-WLAN WPA (Wireless LAN) a74880ae-a336-4133-9454-b0376557cb6c   
802-11-wireless   1335335775   Mi 25 Apr 2012 08:36:15 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth0   802-3-ethernetunmanaged 
/org/freedesktop/NetworkManager/Devices/1  
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.4.0connected   enabled   enabled 
enabledenabled enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat-dilek]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat Dilek]

I found the upstream commit which points to the RH-Bug:

commit  77de91e5a8b1c1993ae65c54b37e0411e78e6fe6
core: don't fight with the kernel over the default IPv6 route

[1]
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=77de91e5a8b1c1993ae65c54b37e0411e78e6fe6

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat Dilek]

I have rebuilt a new NM package which includes the upstream fix.
It fixes here WLAN (IPv6) dis-/reconnects and log-files aren't spammed anymore.

Thanks RAOF for vital help in Ubuntu's way of packaging on IRC.
Also RAOF encouraged me to add my debdiff to this BR.

Have fun!

** Patch added: "debdiff to network-manager-0.9.4.0 (0.9.4.0-0ubuntu3)"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+attachment/3103279/+files/network-manager-0.9.4.0.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat Dilek]

Hmm, network-manager (0.9.4.0-0ubuntu4) seems not to have the (upstream)
patch from here.

What's status? Especially wireless + wired (with 3.2.0 precise-kernel)? 
( OK, Ubuntu developers are visiting UDS, so... :-) )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat Dilek]

debdiff against network-manager (0.9.4.0-0ubuntu4) from precise-proposed

** Patch added: "network-manager-0.9.4.0-0ubuntu4.1~dileks1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/988183/+attachment/3141579/+files/network-manager-0.9.4.0-0ubuntu4.1%7Edileks1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 344053] Re: I/O warning : failed to load external entity

[Sedat Dilek]

I hit the same problem after "ubuntu" (unity-3d) profile was BROKEN here.
To workaround this, I used "unity-2d".

compiz-session-ids are stored at different places.
unity-2d: ~/.compiz/session/
ubuntu (unity-3d): ~/.compiz-1/session/

When switching at the X-login-manager (LightDM) from "unity-2d" to "ubuntu" 
(unity-3d) you will hit the warning.
NOTE: ~/.compiz/ dir gets removed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344053

Title:
  I/O warning : failed to load external entity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/344053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 344053] Re: I/O warning : failed to load external entity

[Sedat Dilek]

The profiles in LightDM are called "Ubuntu" and "Ubuntu-2d".

NOTE: Check ~/.dmrc file!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/344053

Title:
  I/O warning : failed to load external entity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/344053/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Original /etc/pam.d/login"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505727/+files/login.orig

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Refreshed /etc/pam.d/login (v2)"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505728/+files/login_pam_umask_so-umask-v2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Refreshed /etc/pam.d/common-session (v2)"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505730/+files/common-session_pam_umask_so-umask-v2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Refreshed /etc/pam.d/login (v3)"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505735/+files/login_pam_umask_so-umask-v3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Patch added: "Diff pam_umask man-page (rebuild latest pam (1.1.3-7ubuntu2))"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505731/+files/pam_umask-man8.diff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Original /etc/pam.d/common-session"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505729/+files/common-session.orig

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Refreshed /etc/pam.d/login (v4)"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3505753/+files/login_pam_umask_so-umask-v4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Hi Steve,

Thanks for taking care!

First of all, this was never a "real" bug-report... more an
investigation and understanding how pam_umask is working and how someone
can influence the default UMASK settings.

Can you tell me to which of Ubuntu's MLs I should start such a
discussion next time (opening a BR was IMHO not the very best idea :-))?

> I don't see anything here that's a bug in the pam package.

Of course, there is... not on 1st view.

After digging more and more into the matters, it has shown the man-page is not 
very clear.
See also comment #20 and the attached diff when rebuilding latest available pam 
package on precise.

Dunno, if I should open a new bug on this?

>> I am not sure where exactly to change the umask for shell logins
>> GLOBALLY and/or USER-DEFINED.

> In the /etc/pam.d/common-session* include files, where the existing
references to pam_umask are found.

Again, the man-page(s) is not clear enough here, especially man pam_umask has a 
section where an order/ranking is listed.
IMHO this needs to be revised!
There are no references to "/etc/pam.d/common-session*"!

>> when I am working with the Freetz build-system I have this
>> umask/shell problem described in [1].

> It is a bug for any build system to make assumptions about the umask.
If particular permissions are required, it should set them > explicitly
- or set its own umask as part of the build system.

Yeah, the easiest way of "fixing" this is to run 'umask=$UMASK make ...'
in Freetz.

I discussed with the lead developer to change the file permissions before 
packing/modifying the rootfs for the firmware.
Unfortunately, the user gets an abort and the help printed on the shell is not 
helpful.

I agree with you this is a problem in the Freetz build-system and should
be fixed there.

>> The umask is "002" when xterm is started.

> That is the current default, yes.

Where has someone a hint to this GLOBAL change?
The pam package was bumped and the new change done.
AFAICS this 'umask=002' change was not introduced with (means after) precise 
release (correct me if I am wrong)!

>> $ man pam_umask

>> ...recommends:

>> EXAMPLES
>>Add the following line to /etc/pam.d/login to set the user
>> specific umask at login:

> This is an example, not a recommendation. Modifying the /etc/pam.d/login file 
> only affects the login service. As you are not
> using a console login, this does not apply.

Maybe, I misunderstand "console login"... you mean VT-1...VT-7 where
VT-7 is normally X(org)?

>> NOTE-1: common-session is a INCLUDED file, but a
>> dpkg -S /path/to/common-session does NOT refer to any Ubuntu package.

> This is normal for config files modified by the system at runtime, and is not 
> a bug in pam. It is arguably a bug in dpkg, but not
> one that will be fixed any time in the near future.

Yupp, I have seen this afterwards, that the files were generated.
Seeing from a analyst POV it was strange to me that dpkg did not print a status 
"known" or "belongs to pkg X".

>> NOTE-2: session items in common-session file are malformed (tabs)!

> There's nothing malformed about using tabs here.

>From a comestical POV it is... here in Ubuntu/precise's vi with standard tabs 
>settings.
I noticed this when doing a diff after new identation.

>> I am not sure where exactly to change the umask for shell logins
>> GLOBALLY and/or USER-DEFINED.

> In the /etc/pam.d/common-session* include files, where the existing
references to pam_umask are found.

Again, no refs in the man-page(s) and IMHO no correct (new) list of
ranking in 'man pam_umask'.

Last question:

The not up2date pam_umask man-page says:

-UMASK entry from /etc/login\&.defs
+UMASK entry from /etc/login\&.defs (influenced by USERGROUPS_ENAB in 
/etc/login\&.defs)

So, a user should NOT play with USERGROUPS_ENAB settings in /etc/login.defs?
And if YES, what are the consequences for his/her Ubuntu Linux system?

Thanks in advance!

- Sedat -

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1008837] Re: cups fails to install/upgrade with systemd

[Sedat Dilek]

I have placed some informations on how to workaround some known issues
with this experimental systemd package.

Especially, see "Workaround #2: Failures on software-upgrades".

- Sedat -

[1] https://wiki.ubuntu.com/systemd#Workarounds

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008837

Title:
  cups fails to install/upgrade with systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1008837/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1039413] [NEW] package cups 1.5.3-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Sedat Dilek]

Public bug reported:

Problem occured when using systemd from Martin Pitt's PPA archive.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cups 1.5.3-0ubuntu4
Uname: Linux 3.6.0-rc2-next20120820-2-iniza-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
CupsErrorLog:
 
Date: Tue Aug 21 10:22:26 2012
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH
Papersize: a4
ProcKernelCmdLine: 
BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc2-next20120820-2-iniza-generic 
root=UUID=001AADA61AAD9964 loop=/ubuntu/disks/root.disk ro 
init=/lib/systemd/systemd
SourcePackage: cups
Title: package cups 1.5.3-0ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 09XK
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 530U3BI/530U4BI/530U4BH
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr09XK:bd08/03/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3BI/530U4BI/530U4BH
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package precise third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039413

Title:
  package cups 1.5.3-0ubuntu4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1039413/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1039413] Re: package cups 1.5.3-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Sedat Dilek]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039413

Title:
  package cups 1.5.3-0ubuntu4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1039413/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat Dilek]

Hi, I have rebuilt  0.9.4.0-0ubuntu5 for quantal on my precise/amd64
system and thus I do not see the errmsgs no more. As usually I tested in
an IPv6 WLAN only environment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1156363] Re: Fwd: Ralink RT3290 card not supported

[Sedat Dilek]

On Thu, Mar 28, 2013 at 10:03 AM, Stanislaw Gruszka  wrote:
> On Thu, Mar 28, 2013 at 08:18:37AM +, Ali Ustek wrote:
>> >> The wi-fi chip Ralink RT3290 is common in notebooks but is not
>> >> supported by linux-kernel
>
> This device is supported since 3.7 . You most likely compile kernel
> without CONFIG_RT2800PCI_RT3290.
>

Hi Ali,

your kernel-config (self-compiled or the one of your $distro) and
dmesg logs are always helpful, the same to lspci/lsusb outputs.
And... informations to your $distro plus used your
$network-userspace-apps like network-manager (NM), wpa-supplicant etc.
are helpful... if you want your issue be tracked... successfully :-).

Check also docs section for debugging the different wifi-drivers on
.

Hope this helps you!

Regards,
- Sedat -

> Stanislaw
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156363

Title:
  Ralink RT3290 card not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1155601] [NEW] Bump to v1.9.1.5

[Sedat Dilek]

Public bug reported:

After a private conversation with Colin Watson I am doing this BR.

Here, I am on Ubuntu/precise an using a self-compiled v1.8.2.
Colin wanted to keep v1.8.1.x series sn not doing a major-bump.
So, this version-bump request is for latest Ubuntu/raring release.

Unfortunately, I had to downgrade my local git-version to be able to do
this BR, g.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: git 1:1.7.9.5-1
Uname: Linux 3.9.0-rc2-next20130315-3-iniza-small x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Fri Mar 15 13:36:07 2013
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: git
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: git (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug precise running-unity

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1155601

Title:
  Bump to v1.9.1.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1155601/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 988183] Re: Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add default route"

[Sedat Dilek]

Thanks, kolya.
See also thread on linux-wireless ML [1] for more details.

[1] http://marc.info/?t=13370042821&r=1&w=2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988183

Title:
  Logs full with "ICMPv6 RA: ndisc_router_discovery() failed to add
  default route"

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/988183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] [NEW] [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Public bug reported:

[ Resending via 'ubuntu-bug libpam-modules' ]

Hi,

when I am working with the Freetz (a small Linux router project based
on buildroot mainly for MIPS arch) build-system I have this
umask/shell problem described in [1].

NOTE-1: I am using the xterm app from the Unitiy dock.
NOTE-2: I am currently working with a self-compiled Linux v3.8-rc2
kernel (if this matters - not sure if Eric Biedermann's namespace
changes result in a different behaviour), but I have seen the issue
also with any Ubuntu-kernels I ran here, so it should be independent).

The umask is "002" when xterm is started.

After hitting the problem so many times when doing for example:

$ cd ~/src/freetz/freetz-git/

$ make dist-clean

So, I wanted to eliminate this problem forever and now!

My first approach was to follow the advices in Ubuntu Bug #379341 (see
[2]), especially the hint to...

$ man pam_umask

...recommends:

EXAMPLES
   Add the following line to /etc/pam.d/login to set the user
specific umask at login:

   session optional pam_umask.so umask=3D0022

NOTE: pam_umask.so is provided by libpam-modules Ubuntu package (see
[3]).

Unfortunately, something like this did NOT work and had to be
enhanced...

$ git diff /etc/pam.d/login /etc/pam.d/login_UMASK-FIXED_NotOK
diff --git a/etc/pam.d/login b/etc/pam.d/login_UMASK-FIXED_NotOK
index f1e43b2..9886f5e 100644
--- a/etc/pam.d/login
+++ b/etc/pam.d/login_UMASK-FIXED_NotOK
@@ -105,3 +105,16 @@ sessionoptional   pam_mail.so standard
 session [success=3Dok ignore=3Dignore module_unknown=3Dignore default=3Dba=
d]
pam_selinux.so open
 # When the module is present, "required" would be sufficient (When SELinux
 # is disabled, this returns success.)
+
+# XXX: Workaround: Explicitly set the user specific umask at (shell)
login to "0022" value
+#
+# For more details see:
+# 1. Changelog of commit in Freetz/trunk SVN revision 9427
+#
+# 2. [Bug 379341] Re: remove/comment /etc/profile umask setting
+#

+#
+# XXX: Unfortunately, this does NOT satisfy the Freetz build-system.
+# XXX: Fixed by adding "umask=3D0022" to the pam_umask.so line in
"/etc/pam.d/common-session".
+# XXX: See includes in "Standard Un*x account and session" section
here in this file.
+#sessionoptional   pam_umask.so umask=3D0022

...in combination with this change WorksForMe=E2=84=A2.

$ git diff /etc/pam.d/common-session /etc/pam.d/common-session_UMASK-FIXED_OK
diff --git a/etc/pam.d/common-session b/etc/pam.d/common-session_UMASK-FIXED_OK
index af9fb77..7a6ac1f 100644
--- a/etc/pam.d/common-session
+++ b/etc/pam.d/common-session_UMASK-FIXED_OK
@@ -24,9 +24,9 @@ session   requiredpam_permit.=
so
 # /etc/login.defs and user settings, solving the problem of different
 # umask settings with different shells, display managers, remote sessions =
etc.
 # See "man pam_umask".
-session optional   pam_umask.so
+session optional   pam_umask.so umask=3D0022
 # and here are more per-package modules (the "Additional" block)
-sessionrequiredpam_unix.so
-sessionoptionalpam_systemd.so
+sessionrequiredpam_unix.so
+sessionoptionalpam_systemd.so
 sessionoptionalpam_ck_connector.so nox11
 # end of pam-auth-update config

NOTE-1: common-session is a INCLUDED file, but a dpkg -S 
/path/to/common-session does NOT refer to any Ubuntu package.
NOTE-2: session items in common-session file are malformed (tabs)!

# LC_ALL=3DC dpkg -S /etc/pam.d/common-session
dpkg-query: no path found matching pattern /etc/pam.d/common-session.

More confusion on dpkg -S:

# LC_ALL=3DC dpkg -S /etc/pam.d/* | sort
dpkg-query: no path found matching pattern /etc/pam.d/common-account.
dpkg-query: no path found matching pattern /etc/pam.d/common-auth.
dpkg-query: no path found matching pattern /etc/pam.d/common-password.
dpkg-query: no path found matching pattern /etc/pam.d/common-session.
dpkg-query: no path found matching pattern
/etc/pam.d/common-session-noninteractive.
dpkg-query: no path found matching pattern
/etc/pam.d/common-session_UMASK-FIXED_OK.
dpkg-query: no path found matching pattern /etc/pam.d/login_UMASK-FIXED_Not-OK.
at: /etc/pam.d/atd
cron: /etc/pam.d/cron
cups: /etc/pam.d/cups
gnome-screensaver: /etc/pam.d/gnome-screensaver
libpam-runtime: /etc/pam.d/other
lightdm: /etc/pam.d/lightdm
lightdm: /etc/pam.d/lightdm-autologin
login: /etc/pam.d/login <--- Here: Shell login + umask-handling???
login: /etc/pam.d/su
openssh-server: /etc/pam.d/sshd <--- Here: SSH login and umask-handling???
passwd: /etc/pam.d/chfn
passwd: /etc/pam.d/chpasswd
passwd: /etc/pam.d/chsh
passwd: /etc/pam.d/newusers
passwd: /etc/pam.d/passwd
policykit-1: /etc/pam.d/polkit-1
ppp: /etc/pam.d/ppp
samba-common: /etc/pam.d/samba
sudo

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Hmm, looks like these common-* files were generated today.

# LC_ALL=C ls -alt /etc/pam.d/common-*
-rw-r--r-- 1 root root  699 Jan  8 13:23 /etc/pam.d/common-session.diff
-rw-r--r-- 1 root root 1435 Jan  8 12:35 
/etc/pam.d/common-session-noninteractive
-rw-r--r-- 1 root root 1515 Jan  8 12:35 /etc/pam.d/common-session.orig
-rw-r--r-- 1 root root 1480 Jan  8 12:35 /etc/pam.d/common-password
-rw-r--r-- 1 root root 1208 Jan  8 12:35 /etc/pam.d/common-account
-rw-r--r-- 1 root root 1249 Jan  8 12:35 /etc/pam.d/common-auth
-rw-r--r-- 1 root root 1532 Jan  8 10:32 /etc/pam.d/common-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

OK, 'dpkg-reconfigure libpam-runtime' (not libpam-modules) invokes 'pam-
auth-update' binary which is able to generate/update "...Local
modifications to /etc/pam.d/common-* ...":

# cd /etc/pam.d

# mkdir COMMON
# mv common-* COMMON/

# dpkg-reconfigure libpam-modules
# LC_ALL=C ls -alt /etc/pam.d/common-*
[ OUTPUT ]
ls: cannot access /etc/pam.d/common-*: No such file or directory

[ Run #1: Keep local mods ]
# dpkg-reconfigure libpam-runtime
[ OUTPUT ]
pam-auth-update: Local modifications to /etc/pam.d/common-*, not updating.
pam-auth-update: Run pam-auth-update --force to override.

[ Run #2: (Re)Generate local mods ]
# dpkg-reconfigure libpam-runtime
# LC_ALL=C ls -alt /etc/pam.d/common-*
-rw-r--r-- 1 root root 1515 Jan  8 16:21 /etc/pam.d/common-session
-rw-r--r-- 1 root root 1435 Jan  8 16:21 
/etc/pam.d/common-session-noninteractive
-rw-r--r-- 1 root root 1208 Jan  8 16:21 /etc/pam.d/common-account
-rw-r--r-- 1 root root 1480 Jan  8 16:21 /etc/pam.d/common-password
-rw-r--r-- 1 root root 1249 Jan  8 16:21 /etc/pam.d/common-auth

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Investigating common-* and where these includes come from...

root# dpkg -S /etc/pam.d/other 
libpam-runtime: /etc/pam.d/other

root# cat /etc/pam.d/other
#
# /etc/pam.d/other - specify the PAM fallback behaviour
#
# Note that this file is used for any unspecified service; for example
#if /etc/pam.d/cron  specifies no session modules but cron calls
#pam_open_session, the session module out of /etc/pam.d/other is
#used.  If you really want nothing to happen then use pam_permit.so or
#pam_deny.so as appropriate.

# We fall back to the system default in /etc/pam.d/common-*
# 

@include common-auth
@include common-account
@include common-password
@include common-session
-EOF-

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

NO changes to pam_umask.so generated by (un)selecting one of these items
(see attached diff):

# pam-auth-update --force

[*] Unix authentication
[*] Register user sessions in the systemd control group hierarchy
[*] GNOME Keyring Daemon - Login keyring management
[*] ConsoleKit Session Management
[*] Inheritable Capabilities Management


** Patch added: "Changes via 'pam-auth-update --force'"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3477042/+files/pam-auth-update--force.diff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

WorksForMe take #2: Side-effects?

$ grep pam_umask.so /etc/pam.d/common-session
#session optional   pam_umask.so <--- COMMENTED!

$ grep pam_umask.so /etc/pam.d/login
sessionoptional   pam_umask.so umask=0022 <--- UNCOMMENTED - setting has 
now an effect!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

NEVER NEVER NEVER... NEVER EVER REMOVE /etc/pam.d/common-session file
!!!

http://grml.org [saves your admin-day!]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "WorksForMe version of /etc/pam.d/common-session"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3477180/+files/common-session_pam_umask_so-fixed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

** Attachment added: "Commented /etc/pam.d/login file"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3477181/+files/login_pam_umask_so-fixed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Another alternative which works here:

root# chfn -o umask=0022 myusername

[ /etc/shadow ]
-myusername:x:1000:1000:WeAreFam,,,:/home/myusername:/bin/bash
+myusername:x:1000:1000:WeAreFamumask=0022:/home/myusername:/bin/bash

root# grep pam_umask.so /etc/pam.d/common-session
session optionalpam_umask.so

root# grep pam_umask.so /etc/pam.d/login
#sessionoptional   pam_umask.so umask=0022

[1] http://ubuntuforums.org/showpost.php?p=8255773&postcount=5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

# egrep 'umask|libpam-umask' -nr /etc/skel/
/etc/skel/.profile:7:# the default umask is set in /etc/profile; for setting 
the umask
/etc/skel/.profile:8:# for ssh logins, install and configure the libpam-umask 
package.
/etc/skel/.profile:9:#umask 022

According to [1] /etc/profile should not be used for "default" umask-ing.
2nd libpam-umask package does no more exist, the shared-lib moved to 
libpam-modules.
These comments should be fixed as well.

[1] https://lists.ubuntu.com/archives/foundations-
bugs/2011-December/056446.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

So the root cause seems to be the USERGROUPS_ENAB setting:

--- /etc/login.defs.orig
+++ /etc/login.defs
-USERGROUPS_ENAB yes
+USERGROUPS_ENAB no

This gives a 0022 umask in xterm.

Not sure what side-effects this change will cause.

[ /etc/login.defs ]
...
#
# Login configuration initializations:
#
#   ERASECHAR   Terminal ERASE character ('\010' = backspace).
#   KILLCHARTerminal KILL character ('\025' = CTRL/U).
#   UMASK   Default "umask" value.
#
# The ERASECHAR and KILLCHAR are used only on System V machines.
# 
# UMASK is the default umask value for pam_umask and is used by
# useradd and newusers to set the mode of the new home directories.
# 022 is the "historical" value in Debian for UMASK
# 027, or even 077, could be considered better for privacy
# There is no One True Answer here : each sysadmin must make up his/her
# mind.
#
# If USERGROUPS_ENAB is set to "yes", that will modify this UMASK default value
# for private user groups, i. e. the uid is the same as gid, and username is
# the same as the primary group name: for these, the user permissions will be
# used as group permissions, e. g. 022 will become 002.
#
# Prefix these values with "0" to get octal, "0x" to get hexadecimal.
#
ERASECHAR   0177
KILLCHAR025
UMASK   022
...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Worth reading why UMASK/USERGROUPS_ENAB changes were done.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583971


** Bug watch added: Debian Bug tracker #583971
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583971

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

The pam_umask man-page is not up2date.

$ zgrep "influenced by USERGROUPS_ENAB" /usr/share/man/man8/pam_umask.8.gz
[ EMPTY ]

$ dpkg -S /usr/share/man/man8/pam_umask.8.gz
libpam-modules: /usr/share/man/man8/pam_umask.8.gz

$ dpkg -l | grep libpam-modules
ii  libpam-modules  1.1.3-7ubuntu2  
Pluggable Authentication Modules for PAM
ii  libpam-modules-bin  1.1.3-7ubuntu2  
Pluggable Authentication Modules for PAM - helper binaries



** Patch added: "Patch from pam (1.1.3-7ubuntu2) debian/patches-applied/"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+attachment/3477419/+files/pam_umask_usergroups_from_login.defs.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1097262] Re: [pam][pam_umask]: Explicitly set the user specific umask at (shell) login to "0022" value

[Sedat Dilek]

Blueprints "Change the default umask to 0002"

https://blueprints.launchpad.net/ubuntu/+spec/umask-to-0002

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262

Title:
  [pam][pam_umask]: Explicitly set the user specific umask at (shell)
  login to "0022" value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs