[Bug 841672] Re: ssh-add does not always unlock ssh keys
Scratch my last workaround (#13). It didn't work. This one does though Stop gnome-keyring ssh-agent from starting. Then ssh-agent and ssh works as expected. To stop gnome-keyring ssh-agent from starting do: sudo mv /etc/xdg/autostart/gnome-keyring-ssh /etc/xdg/autostart /gnome-keyring-ssh.desktop.disabled I first posted this, plus a load of stuff about trying to work through the problem at http://askubuntu.com/questions/122824/how-to-manually- trigger-ssh-add-dialog-box/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 841672] Re: ssh-add does not always unlock ssh keys
I found a way to trigger the gnome dialog box directly, so I only have to enter the ssh password once. I created ~/bin/gssh-add and put the following in it: SSH_ASK_PASS=/usr/bin/ssh-askpass ssh-add I then make it executable: chmod +x ~/bin/gssh-add And then I launch it using Alt+F2. That triggers the gnome dialog box. Note that if you run gssh-add from the terminal it will not trigger the gnome dialog box. See the ENVIRONMENT section of the ssh-add man page for details as to why. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 841672] Re: ssh-add does not always unlock ssh keys
My use case is that I have a script (using tmuxinator) that opens several shells inside tmux and executes ssh in them, all at once. I run ssh-add before starting the script, so that I only have to enter the passphrase once. However with this behaviour I have to enter the passphrase into the gui dialog box multiple times. After that ssh and the agent work as expected. But I can't seem to unlock the ssh key properly before starting an actual ssh session. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/841672 Title: ssh-add does not always unlock ssh keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/841672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 50385] Re: samba does not support private dir option (qemu related)
Hi, work-around for user accounts you trust as administrators, if you don't want to run everything as root, but are not so insane as to use `chmod a+rw`: essentially just give the user permission to the files in the /var/lib/samba dir as noted by others earlier. (as root) # disable samba startup at boot: (so only qemu's one will be running) update-rc.d -f samba remove adduser $YOU adm chgrp adm /var/lib/samba/*.tdb chmod g+rw /var/lib/samba/*.tdb I also applied that to /var/lib/samba/perfmon and the parent dir but I don't know if that is really necessary. note that cd /tmp/qemu-smb.1234-0 /usr/sbin/smbd -i -s smb.conf ends with: ... Failed to open group mapping ldb '/var/lib/samba/group_mapping.ldb' - '(null)' ... Abnormal server exit: open_sockets_smbd() failed BACKTRACE: ... ... but C:\ net use e: \\10.0.2.4\qemu in the WinXP guest works. shrug. tested in Debian/squeeze + samba 2:3.5.6~dfsg-3squeeze2 :-/ Hamish -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/50385 Title: samba does not support private dir option (qemu related) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown)
Hi Tom I installed Karmic Beta the other day and no longer get this error (with the entries in the /etc/fstab as I originally described). Hamish -- Network is brought down before network filesystems are unmounted (CIFS timeout at shutdown) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
I am commenting here to keep this thread alive, and wondering if any of the wpasupplicant team are looking at it? More than happy to keep experimenting and chatting about it! Thanks. Hamish -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
/var/log/messages from last startup [EMAIL PROTECTED]:~$ uname -r 2.6.24-15-generic ** Attachment added: /var/log/messages http://launchpadlibrarian.net/13194682/messages%20log.txt -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
dmesg look for [ 62.697883] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 62.697948] CIFS VFS: cifs_mount failed w/return code = -101 then after that wlan0 is configured i think the timing of these operations is the problem how do i get the shutting down logs so I can show you the errors there? Hamish ** Attachment added: dmesg log http://launchpadlibrarian.net/13194695/dmesg.txt -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS issue (was not resolved on #207441)
...although I have included the error message in the original description above: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid this number changes eventually after 2-3 minutes this times out and the computer restarts, but it isn't really good enough Hamish -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] [NEW] CIFS/SMBFS issue (was not resolved on #207441)
Public bug reported: I installed smbfs, and then put some entries into /etc/fstab, so they automount on startup. An example of this is here: //ip address of nas box/share name /home/hamish/directory name cifs credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000 0 0 ** note the use of cifs in the lines above ** (The username and password are in the .smbcredentials file) On startup, for each entry in the /etc/fstab file, I get the following in dmesg: [ 70.495504] CIFS VFS: Error connecting to IPv4 socket. Aborting operation [ 70.495569] CIFS VFS: cifs_mount failed w/return code = -101 But the shares are mounted, and a nautilus session opens up (which is also annoying...) Also logging off with CIFS shares mounted in /etc/fstab, it sits with an error message: CIFS VFS: server not responding CIFS VFS: no response for cmd 50 mid this number changes And takes about 2 minutes to timeout. This also happened with Gutsy Should the timing of the mounting and dismounting be changed so that it works? It is related to the starting of network-manager and CIFS shares trying to connect on startup *before* the network is up, and dismounting the shares *after* network-manager is stopped. Hamish PS: note to Chuck Short. I am using cifs. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- CIFS/SMBFS issue (was not resolved on #207441) https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
