[Bug 920749] Re: pam configuration for SSH prevents LANG override
I feel like this setup violates the principle of least surprise. As a user, sshing into a machine, I have my ssh client configured to SendEnv LC_* and LANG. Awesome. Look, /etc/ssh/sshd_config, the server is even accepting these in its default configuration! Except some setting that I *personally* never would have thought of in pam configuration, completely outside of the control of a mere mortal (read: non-root user) comes in and sets the locale to whatever the person who set up the machine originally configured. And I have no real control over it. I do recognize the issue raised when there's a difference in client/server locale meanings (my en_US is your en_US.utf8 I think is one someone mentioned), but I feel like that's solveable on the client side by specifying different values to be sent for those variables in their ssh configuration (SetEnv option) Even the ssh_config manpage specifies that... > the Debian openssh-client package sets several options as standard in > /etc/ssh/ssh_config which are not the default in ssh(1): > * SendEnv LANG LC_* So why would it then have a default configuration to stomp all over those environment variables? Am I missing something? I'm not even a non-english user, I was just trying to figure out why emacs when I ssh in shows \u2505 instead of a fancy pipe character, but when I use mosh it works fine, and fell down this rabbit hole :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920749 Title: pam configuration for SSH prevents LANG override To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/920749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046029] Re: Network device not configured correctly
I found a workaround: fix the interface name afterward with nameif(8) it's ugly, and I really hope this bug gets fixed some day, but at least I don't have to play reboot roulette and hope I get the correct device names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046029 Title: Network device not configured correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1046029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046029] Re: Network device not configured correctly
also running into this bug and seeking a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046029 Title: Network device not configured correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1046029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046029] Re: Network device not configured correctly
also running into this bug and seeking a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046029 Title: Network device not configured correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/1046029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1202440] [NEW] support hooks directly in preseed file
Public bug reported: It would be great to be able to define hooks directly in the preseed file: d-i hook/post-base-installer/0 string "in-target adduser foo" Something like that. The use case I have for this is such: I'm building a preseed file to bootstrap a system up to installing puppet and running it. The problem is, I need my puppet uid/gid to be consistent every time. For other users, I just add them to my puppet configuration so when puppet runs the user is created with the appropriate uid, but in order to do that I need to install puppet which will install its own user (with its own, possibly inconsistent) uid. Therefore I need to create the user/group prior to installing puppet. When I asked about doing this on #ubuntu-installer, the response I got from cjwatson (thanks, by the way!) was to use preseed/early_install to add a hook to /usr/lib/post-base-installer.d/ to call "in-target adduser foo". Since there can only be one early_install, having to add this to a potentially long and complex chain of commands could get pretty hairy, so being able to do: d-i hook/post-base-installer/00_add_foo_user string "in-target adduser foo" Would be much much cleaner and also allow for defining multiple hooks, so if you're generating your preseed file with a script it should make it easier to manage multiple parts of your script adding their own hooks. I'm a pretty new user of preseed, so I can't come up with more use cases, but I can't imagine it would be that hard to add this functionality, and I think it could be incredibly useful. ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1202440 Title: support hooks directly in preseed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1202440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1077174] Re: conflict with package 'bundler'
I've run into the same issue. It would appear that bundler and ruby- bundler are duplicate packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1077174 Title: conflict with package 'bundler' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-bundler/+bug/1077174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
