Re: [PLUG] Login keyring
On Mon, 14 Feb 2022 23:20:59 -0800 John Jason Jordan dijo: >On Mon, 14 Feb 2022 17:23:00 -0800 >wes dijo: > >>if you right-click on the keyring, do you get any options around >>setting a password? > >It just pops up the box to enter the password, and if I leave it blank >and then click on OK it gives an error message that I didn't enter the >right password. It won't take a blank password. > >I can't find an option to launch Seahorse from the menus, but >'seahorse' from the command line did the trick. It provides a window >titled 'Passwords and Keys,' which gives me a panel on the left: > >Passwords > Default keyring > Login >Keys > GnuPG keys > OpenSSH keys >Certificates > System Trust > >Clicking on 'Default keyring' gives me a panel on the right with an >image of some keys, underneath 'Keyring is locked,' and below that a >button 'Unlock.' Clicking on Unlock prompts me to enter my password, >but if I leave it blank it gives an error message that the password was >not correct. > >Clicking on any of the other items gives me a window on the right that >says 'This collection seems to be empty.' > >The Seahorse GUI seems unable to accept an empty password. I should have added that I can right-click on Login and there is an option to change password that pops up a box for the new password. I have to enter the old password first, then Continue, and then the new password. I can leave the new password blank, but then it says if I leave it blank I have no security and anyone can change my password. I left it at that, so maybe I solved this problem.
Re: [PLUG] Login keyring
On Mon, 14 Feb 2022 17:23:00 -0800 wes dijo: >if you right-click on the keyring, do you get any options around >setting a password? It just pops up the box to enter the password, and if I leave it blank and then click on OK it gives an error message that I didn't enter the right password. It won't take a blank password. I can't find an option to launch Seahorse from the menus, but 'seahorse' from the command line did the trick. It provides a window titled 'Passwords and Keys,' which gives me a panel on the left: Passwords Default keyring Login Keys GnuPG keys OpenSSH keys Certificates System Trust Clicking on 'Default keyring' gives me a panel on the right with an image of some keys, underneath 'Keyring is locked,' and below that a button 'Unlock.' Clicking on Unlock prompts me to enter my password, but if I leave it blank it gives an error message that the password was not correct. Clicking on any of the other items gives me a window on the right that says 'This collection seems to be empty.' The Seahorse GUI seems unable to accept an empty password.
Re: [PLUG] Login keyring
On Mon, Feb 14, 2022 at 1:04 PM John Jason Jordan wrote: > I could use some suggestions. This gives a high level summary of what keyring does. https://itsfoss.com/ubuntu-keyring/ For your purposes it gives the suggestion that has already been proposed here. Give the keyring an empty password and it will not bother you. The other possibly useful thing it says is that Seahorse has been renamed on some systems to "Password and Keys" Bill
Re: [PLUG] Login keyring
On Mon, Feb 14, 2022 at 4:57 PM John Jason Jordan wrote: > > > >virbr0 is for virtualization software. virtualbox, vmware, etc. that's > >where the 122 comes from. > > That's interesting. Of course, I spent hours yesterday fiddling with > VirtualBox, and finally got it working. But since last night it > has been shut down. And just to be sure there are no virtual machines > still running, just now I rebooted, but ifconfig still shows virbr0, > with the same funny IP address. Is it possible that VirtualBox running > Windows 10 (the only machine that I ran) created this 'device' for the > machine? And if it did, when I shut down Windows 10 and VirtualBox, why > didn't it delete it? I might add that it doesn't appear on my other two > computers. > > it's not related to the guest OS, or to whether virtualbox is currently running. the interface is created when you install virtualbox and remains available for use as needed. > I also tried to run network-manager, which Synaptic says is installed, > but evidently it never occurred to the writers of the documentation to > tell users HOW TO LAUNCH IT! I tried nm, network-manager, > network-manager-applet (with and without dashes), and numerous others, > all of which return 'no such file.' > > as I recall, it uses capital letters in the executable name. try typing Net and then press tab a few times to see if anything autocompletes. > Meantime, I can ping 192.168.122.1, although the ping command just says > that it connected and the time it took for the response. And I tried to > connect to it by putting it in the URL bar in Chromium, but got > 'refused to connect.' > > 192.168.122.1 is an address on your local machine. it won't help you with any of these issues. >> At this point I was finally able to launch seahorse. I explored it a > >> bit, but couldn't figure out how to use it. One of the buttons that I > >> clicked on displayed 'Keyring Locked.' I could probably have unlocked > >> it, but I left it for now because I want it to be unlocked at login, > >> but that option must be buried someplace that I didn't look at. > > >there isn't a specific option to have the keyring unlocked by default. > >you have to implicitly do this by unlocking the keyring, and then > >setting the password to empty. > > I click on Unlock Login Keyring and it just asks for my password. If I > enter it all it does is unlock the keyring; there is no option to set > the password to empty, although there is an option 'Unlock this keyring > when I'm logged in.' But the checkbox has always been selected, yet it > still asks me repeatedly to unlock the keyring. > if you right-click on the keyring, do you get any options around setting a password? -wes
Re: [PLUG] Login keyring
On Mon, 14 Feb 2022 12:24:09 -0800 wes dijo: >On Mon, Feb 14, 2022 at 11:04 AM John Jason Jordan >wrote: > >> On Sun, 13 Feb 2022 17:14:19 -0800 >> wes dijo: >> >> >On Sun, Feb 13, 2022 at 12:49 PM John Jason Jordan >> >wrote: >> When I ran ifconfig it gave me enx+long-number which was the >> ethernet, and no IP address for it, and it gave me virbr0 with an >> address of 192.168.122.1. This has to be the wifi, but where did the >> 122 come from? My network is192.168.1.x. > > >virbr0 is for virtualization software. virtualbox, vmware, etc. that's >where the 122 comes from. That's interesting. Of course, I spent hours yesterday fiddling with VirtualBox, and finally got it working. But since last night it has been shut down. And just to be sure there are no virtual machines still running, just now I rebooted, but ifconfig still shows virbr0, with the same funny IP address. Is it possible that VirtualBox running Windows 10 (the only machine that I ran) created this 'device' for the machine? And if it did, when I shut down Windows 10 and VirtualBox, why didn't it delete it? I might add that it doesn't appear on my other two computers. I thought it might be a neighbor's wifi, so I tried iwlist. It showed half a dozen wifi networks (including my own), but iwlist doesn't list the IP address of the network, and ifconfig doesn't display the name for 192.168.122.1. Before running iwlist I tried the network icon in the panel, because if you click on it you can see all the networks available. But it's not in the panel on the Latitude, nor is it available to be added to the panel. I can't find it in Synaptic. It's in the panel on my other Xubuntu computers, where it appears in the Notification Area panel plugin. Apparently on Xubuntu 21.10 the Notification Area has been removed. Xubuntu 21.10 does have a penal plugin for the network, called 'Net,' but if you click on it all you get is the name of the connection device and the last four messages - no options to connect to other networks, list of available networks - basically useless. I also tried to run network-manager, which Synaptic says is installed, but evidently it never occurred to the writers of the documentation to tell users HOW TO LAUNCH IT! I tried nm, network-manager, network-manager-applet (with and without dashes), and numerous others, all of which return 'no such file.' Meantime, I can ping 192.168.122.1, although the ping command just says that it connected and the time it took for the response. And I tried to connect to it by putting it in the URL bar in Chromium, but got 'refused to connect.' >> At this point I was finally able to launch seahorse. I explored it a >> bit, but couldn't figure out how to use it. One of the buttons that I >> clicked on displayed 'Keyring Locked.' I could probably have unlocked >> it, but I left it for now because I want it to be unlocked at login, >> but that option must be buried someplace that I didn't look at. >there isn't a specific option to have the keyring unlocked by default. >you have to implicitly do this by unlocking the keyring, and then >setting the password to empty. I click on Unlock Login Keyring and it just asks for my password. If I enter it all it does is unlock the keyring; there is no option to set the password to empty, although there is an option 'Unlock this keyring when I'm logged in.' But the checkbox has always been selected, yet it still asks me repeatedly to unlock the keyring. I mostly agree with points about security from Tomas. The Latitude will be used just for reading electronic books and articles; it has no sensitive information on it, not even my bookmarks for Firefox and Chromium. Security needs are negligible. Yet Ubuntu forces me to give the secret handshake for permission to go to the bathroom. Bah.
Re: [PLUG] Login keyring
On Mon, 2022-02-14 at 11:04 -0800, John Jason Jordan wrote: > Using the Latitude I logged into the D-Link DIR860L B1 and noted that > there is a connection at 192.168.1.171 marked 'Latitude,' that must > be > the ethernet. Of course, 192.168.122.1 did not appear. > > So now I have two questions: > > 1) How to use Seahorse to get rid of the keyring hassle. > 2) What the heck happened to make the wifi on the Latitude think that > its network was 192.168.122.x? > > I could use some suggestions. Connected to someone else's wifi or a hotspot? What does network manager says about your wifi connection? -T
Re: [PLUG] Login keyring
I am not against security, do not get me wrong - This is about freedom to control my computer - that implies that there should be reasonable way to do that and be able to authenticate and/or disable it - simply use it. If the only choice to control ones own audio device is not to install modern linux anymore - that does not seems to be marching in the right direction, IMHO. I could have done that without problems 2 years ago on number of modern distros. That said, I am not sure what lawyers have to do with access to my audio, screen, file system, gpio, etc. and which lawyer's specifically. -Tomas On Mon, 2022-02-14 at 08:43 -0800, Paul Heinlein wrote: > On Sun, 13 Feb 2022, Tomas Kuchta wrote: > > > > security zealots who implemented authentication for just about > > anything > > (filesystem, video, sound, usb, applications, etc.) > > They may be zealots to you, but to many of us they are Lawyer > Avoidance Gurus. The number of people waiting to sue institutions > for > not implementing every last bit of security theater is large and > growing. > > Obviously, my point of view on the subject is not definitive, and > I'm > not trying to justify the situation, but the indisputable fact is > that > there are thousands of IT professionals who -- supporting open > source > software by filing tickets, submitting patches, and writing > documentation -- increasingly answer to their legal departments. >
Re: [PLUG] Login keyring
On Mon, Feb 14, 2022 at 11:04 AM John Jason Jordan wrote: > On Sun, 13 Feb 2022 17:14:19 -0800 > wes dijo: > > >On Sun, Feb 13, 2022 at 12:49 PM John Jason Jordan > >wrote: > When I ran ifconfig it gave me enx+long-number which was the > ethernet, and no IP address for it, and it gave me virbr0 with an > address of 192.168.122.1. This has to be the wifi, but where did the > 122 come from? My network is192.168.1.x. virbr0 is for virtualization software. virtualbox, vmware, etc. that's where the 122 comes from. Well, at least it explains why > apt couldn't download anything. While waiting for my brain to come up > with an explanation for the 122 I plugged in an ethernet cable, and > then I was able to connect, and apt properly installed seahorse and > seahorse-daemon. > answer unclear, ask again later > At this point I was finally able to launch seahorse. I explored it a > bit, but couldn't figure out how to use it. One of the buttons that I > clicked on displayed 'Keyring Locked.' I could probably have unlocked > it, but I left it for now because I want it to be unlocked at login, > but that option must be buried someplace that I didn't look at. > > there isn't a specific option to have the keyring unlocked by default. you have to implicitly do this by unlocking the keyring, and then setting the password to empty. -wes
Re: [PLUG] Login keyring
On Sun, 13 Feb 2022 17:14:19 -0800 wes dijo: >On Sun, Feb 13, 2022 at 12:49 PM John Jason Jordan >wrote: > >> Apparently Xubuntu is supposed to be using seahorse, but it's not >> installed on my Lenovo laptop with 20.04.2 nor on my new Latitude >> with 21.10. I tried the link, but again it says to use seahorse. I >> can install seahorse, but must be something else that is causing the >> problems. >now that you mention it, this triggers my memory. I have always had to >install seahorse to solve this problem. > >I don't think changing your user account's password will help. you >need to change the keyring password (which is frequently the same as >the login password for convenience, but is not necessarily). this is >what seahorse allows you to do Over the weekend I poked at a lot of things, without luck So this morning I installed seahorse, and seahorse-daemon. Not sure id the daemon was required, but I did it anyway. I did this from the command line, and I got a lot of errors, mostly missing packages. I launched Synaptic and did a Reload, which also produced a lot of errors. Back to the command line I entered ifconfig, which produced more strange results. Note that this new Latitude has wifi, but no built-in ethernet port, although I have a USB 3.0 'dock' plugged in that provides an ethernet port. To use it I have to run a cable from another room, and to avoid having a wire to trip over I have always used just the wifi with the Latitude. When I ran ifconfig it gave me enx+long-number which was the ethernet, and no IP address for it, and it gave me virbr0 with an address of 192.168.122.1. This has to be the wifi, but where did the 122 come from? My network is192.168.1.x. Well, at least it explains why apt couldn't download anything. While waiting for my brain to come up with an explanation for the 122 I plugged in an ethernet cable, and then I was able to connect, and apt properly installed seahorse and seahorse-daemon. At this point I was finally able to launch seahorse. I explored it a bit, but couldn't figure out how to use it. One of the buttons that I clicked on displayed 'Keyring Locked.' I could probably have unlocked it, but I left it for now because I want it to be unlocked at login, but that option must be buried someplace that I didn't look at. Using the Latitude I logged into the D-Link DIR860L B1 and noted that there is a connection at 192.168.1.171 marked 'Latitude,' that must be the ethernet. Of course, 192.168.122.1 did not appear. So now I have two questions: 1) How to use Seahorse to get rid of the keyring hassle. 2) What the heck happened to make the wifi on the Latitude think that its network was 192.168.122.x? I could use some suggestions.
Re: [PLUG] Login keyring
On Sun, 13 Feb 2022, Tomas Kuchta wrote: security zealots who implemented authentication for just about anything (filesystem, video, sound, usb, applications, etc.) They may be zealots to you, but to many of us they are Lawyer Avoidance Gurus. The number of people waiting to sue institutions for not implementing every last bit of security theater is large and growing. Obviously, my point of view on the subject is not definitive, and I'm not trying to justify the situation, but the indisputable fact is that there are thousands of IT professionals who -- supporting open source software by filing tickets, submitting patches, and writing documentation -- increasingly answer to their legal departments. -- Paul Heinlein heinl...@madboa.com 45.38° N, 122.59° W
Re: [PLUG] Login keyring
On Sun, Feb 13, 2022 at 12:49 PM John Jason Jordan wrote: > Apparently Xubuntu is supposed to be using seahorse, but it's not > installed on my Lenovo laptop with 20.04.2 nor on my new Latitude with > 21.10. I tried the link, but again it says to use seahorse. I can > install seahorse, but must be something else that is causing the > problems. now that you mention it, this triggers my memory. I have always had to install seahorse to solve this problem. And seahorse is apparently a front end for gnome-keyring or > gnome-keyring-daemon, but those aren't installed either. gnome-keyring may not be in its own distinct package. it may be provided by some other gnome-[something] package that contains a bunch of stuff. I went into > Users and Groups where I am listed, but I couldn't find any settings > for password, so maybe that's not where I should be looking. > > I don't think changing your user account's password will help. you need to change the keyring password (which is frequently the same as the login password for convenience, but is not necessarily). this is what seahorse allows you to do -wes
Re: [PLUG] Login keyring
Apparently Xubuntu is supposed to be using seahorse, but it's not installed on my Lenovo laptop with 20.04.2 nor on my new Latitude with 21.10. I tried the link, but again it says to use seahorse. I can install seahorse, but must be something else that is causing the problems. And seahorse is apparently a front end for gnome-keyring or gnome-keyring-daemon, but those aren't installed either. I went into Users and Groups where I am listed, but I couldn't find any settings for password, so maybe that's not where I should be looking. On Sun, 13 Feb 2022 11:57:23 -0500 Brian Stanaland dijo: >Ubuntu uses the keyring to store passwords for all kinds of things. >It looks like Xubuntu uses seahorse or gnome-keyring as the keyring >manager. I'm running Kubuntu so it uses KDE Wallet. >Anyway, if you open whichever one Xubuntu uses, there should be either >a "login" or "wallet" password stored. By default it uses the user >account password and just opens when you log in. Since you don't enter >the password to log in, the wallet doesn't get opened. Setting the >login password there as blank should fix the problem. >This post is 7 years old but it should still be close to what you'll >see. >https://askubuntu.com/questions/533324/change-keyring-password-on-xubuntu#533326 > >Brian > >On Sun, Feb 13, 2022 at 10:59 AM Tomas Kuchta > wrote: > >> Such is life with desktop/server these days. It is pretty annoying >> that the security zealots who implemented authentication for just >> about anything (filesystem, video, sound, usb, applications, etc.) >> on your system did not think/care of this. >> >> Anyway, the desktop login dialog unlocks keyring for you. If you >> disable it, this is the outcome. I am not familiar with xubuntu - >> there is probably a way to unlock the ring by authenticating with >> some special app... >> >> This of course defeats the purpose of no-login dialog. The easiest is >> probably to enable login and set empty password - that is if the >> security zealots did not enforce password complexity. >> >> Hope that helps, >> -T >> >> PS: Another annoying example: On most systems today, even if you >> arhenticate, you cannot play sounds or display anything remotely. >> Meaning that you cannot practically turn modern linux to a media >> player. One has to turn to not secure, special flake, totally >> unsecured distros >> >> On Sun, Feb 13, 2022, 02:02 John Jason Jordan wrote: >> >> > I have my desktop computer and my new laptop set up to boot Xubuntu >> > without requiring a login. That part works perfectly, but the >> > instant I try to do anything I get a popup: >> > >> > Authentications required >> > The login keyring did not get unlocked when you logged into >> > your computer >> > Password: [ ] >> > >> > What's the point of booting without logging in if I have to log in >> > to do anything? Not only that, if I enter my password to satisfy >> > the login keyring (whatever that is), the next time I try to >> > launch an application I have to login again ... and again ... and >> > again. >> > >> > On my main computer I set it up to require a login, but the >> > desktop and the new laptop don't have anything sensitive on them >> > and they never leave the house. >> > >> > Is there any way to get rid of the stupid keyring requirements?
Re: [PLUG] Login keyring
Ubuntu uses the keyring to store passwords for all kinds of things. It looks like Xubuntu uses seahorse or gnome-keyring as the keyring manager. I'm running Kubuntu so it uses KDE Wallet. Anyway, if you open whichever one Xubuntu uses, there should be either a "login" or "wallet" password stored. By default it uses the user account password and just opens when you log in. Since you don't enter the password to log in, the wallet doesn't get opened. Setting the login password there as blank should fix the problem. This post is 7 years old but it should still be close to what you'll see. https://askubuntu.com/questions/533324/change-keyring-password-on-xubuntu#533326 Brian On Sun, Feb 13, 2022 at 10:59 AM Tomas Kuchta wrote: > Such is life with desktop/server these days. It is pretty annoying that the > security zealots who implemented authentication for just about anything > (filesystem, video, sound, usb, applications, etc.) on your system did not > think/care of this. > > Anyway, the desktop login dialog unlocks keyring for you. If you disable > it, this is the outcome. I am not familiar with xubuntu - there is probably > a way to unlock the ring by authenticating with some special app... > > This of course defeats the purpose of no-login dialog. The easiest is > probably to enable login and set empty password - that is if the security > zealots did not enforce password complexity. > > Hope that helps, > -T > > PS: Another annoying example: On most systems today, even if you > arhenticate, you cannot play sounds or display anything remotely. Meaning > that you cannot practically turn modern linux to a media player. One has to > turn to not secure, special flake, totally unsecured distros > > On Sun, Feb 13, 2022, 02:02 John Jason Jordan wrote: > > > I have my desktop computer and my new laptop set up to boot Xubuntu > > without requiring a login. That part works perfectly, but the instant I > > try to do anything I get a popup: > > > > Authentications required > > The login keyring did not get unlocked when you logged into > > your computer > > Password: [ ] > > > > What's the point of booting without logging in if I have to log in to > > do anything? Not only that, if I enter my password to satisfy the login > > keyring (whatever that is), the next time I try to launch an > > application I have to login again ... and again ... and again. > > > > On my main computer I set it up to require a login, but the desktop and > > the new laptop don't have anything sensitive on them and they never > > leave the house. > > > > Is there any way to get rid of the stupid keyring requirements? > > >
Re: [PLUG] Login keyring
Such is life with desktop/server these days. It is pretty annoying that the security zealots who implemented authentication for just about anything (filesystem, video, sound, usb, applications, etc.) on your system did not think/care of this. Anyway, the desktop login dialog unlocks keyring for you. If you disable it, this is the outcome. I am not familiar with xubuntu - there is probably a way to unlock the ring by authenticating with some special app... This of course defeats the purpose of no-login dialog. The easiest is probably to enable login and set empty password - that is if the security zealots did not enforce password complexity. Hope that helps, -T PS: Another annoying example: On most systems today, even if you arhenticate, you cannot play sounds or display anything remotely. Meaning that you cannot practically turn modern linux to a media player. One has to turn to not secure, special flake, totally unsecured distros On Sun, Feb 13, 2022, 02:02 John Jason Jordan wrote: > I have my desktop computer and my new laptop set up to boot Xubuntu > without requiring a login. That part works perfectly, but the instant I > try to do anything I get a popup: > > Authentications required > The login keyring did not get unlocked when you logged into > your computer > Password: [ ] > > What's the point of booting without logging in if I have to log in to > do anything? Not only that, if I enter my password to satisfy the login > keyring (whatever that is), the next time I try to launch an > application I have to login again ... and again ... and again. > > On my main computer I set it up to require a login, but the desktop and > the new laptop don't have anything sensitive on them and they never > leave the house. > > Is there any way to get rid of the stupid keyring requirements? >
[PLUG] Login keyring
I have my desktop computer and my new laptop set up to boot Xubuntu without requiring a login. That part works perfectly, but the instant I try to do anything I get a popup: Authentications required The login keyring did not get unlocked when you logged into your computer Password: [ ] What's the point of booting without logging in if I have to log in to do anything? Not only that, if I enter my password to satisfy the login keyring (whatever that is), the next time I try to launch an application I have to login again ... and again ... and again. On my main computer I set it up to require a login, but the desktop and the new laptop don't have anything sensitive on them and they never leave the house. Is there any way to get rid of the stupid keyring requirements?
