View original (French)

I can't unlock the keychain.

Solved
LEVINE Posted messages 127 Registration date   Status Member Last intervention   -  
mamiemando Posted messages 33174 Registration date   Status Moderator Last intervention   -
Good evening everyone

The problem presents itself like this:



I looked at the seahorse documentation

This is a machine running Ubuntu 16.04 LTS. Another machine, running Windows 10, sharing several folders. Workgroup under Windows: WORKGROUP. A user, with a password, which is different from root. The user is in the group 
sudo
(so definitely no login without a password). Both machines are on Ethernet.

This machine, at my place, connected without any problem to a Windows 8 PC. And under Nautilus, I can check the "remember forever" box, no problem. I tested it with another machine. And also to a Windows 10 machine. I call seahorse from a terminal, from the user account. I can open the keyring, with its password.

On site, from the user account, I would like to do the same thing as at my place. But here, the OS is asking for the user's password to unlock the login keyring. No password is accepted: neither the user's nor root's (makes sense).

Uh! Does this ring a bell for you?

Thank you

7 answers

  1.
    mamiemando Posted messages 33174 Registration date   Status Moderator Last intervention   7 944
     
    Hello,

    The question is how did you go about transferring the keyring between the two machines. If I understand correctly, you copied and pasted a number of files and you are unable to reuse the keyring on the new machine.

    I suppose that seahorse allows you to export or import data (at least kwallet does under KDE), have you tried doing it that way?

    Otherwise, have you checked here?

    Good luck
    0
  2. LEVINE Posted messages 127 Registration date   Status Member Last intervention   4
     
    Hello :)

    Sorry for the delayed response: point recovery course = two days of work gone :(

    I haven't transferred anything. It's the same user account on the same machine. When I called Seahorse, I got this message: "The password you are using to log in on this computer no longer matches that of the keychain."

    Of course! When I install, I assign a super simple password (except for the root account): 123456. On-site, I asked the user to choose another one, and, as root (this might be my mistake), I assigned this new password to him (with passwd User_Name).

    Not a single file transfer. Just a modification of the user's password.
    Thanks for the link: I'm on it!
    I'm going to test this modification of a user's password on my laptop, with the same version of Ubuntu. I'll give feedback.

    P.S.: What I'm encountering is exactly this: https://forums.fedora-fr.org/viewtopic.php?id=65829%5B%2Furl%5D
    0
  3. mamiemando Posted messages 33174 Registration date   Status Moderator Last intervention   7 944
     
    Verdict?
    0
  4. LEVINE Posted messages 127 Registration date   Status Member Last intervention   4
     
    Hello :)
    The verdict will be delivered on Monday.
    I'm going to wipe the keyring, hoping not to wipe the user's password with it, then, under the user's account, I'll recreate it by clicking on "Remember forever" under Nautilus.
    Of course, on-site: I changed the user's password. I wasn't going to leave 123456 like I do when I install! The root password, on the other hand, is, from the start, a bit tougher. And it hasn't been changed.

    It's still strange.
    At home, I had to, including on my laptop running Ubuntu, introduce an allow rule from 192.168.0.254/24 for ufw. Otherwise, no access to files shared by my Win8 machine.

    On-site (now, it's Win 10), since it's a Livebox, I deleted the rule. And... nothing else! Nautilus and the others map the network, without needing this rule.

    At home, the incriminated Ubuntu machine accessed the shares (thanks to this rule).

    Uh! :/
    0
  6. mamiemando Posted messages 33174 Registration date   Status Moderator Last intervention   7 944
     
    Hello,

    At my place, I had to set up a rule allow from 192.168.0.254/24 for ufw, including on my laptop running Ubuntu. Otherwise, there was no access to the shared folders from my Win8 machine.

    This rule is equivalent to 192.168.0.0/24 and means that you allow traffic related to all IPs 
    192.168.0.*
    . That seems reasonable to me since the other machines on your local network have an IP address that falls within this range. In any case, this seems unrelated to the keychain issue.
    0
  7. LEVINE Posted messages 127 Registration date   Status Member Last intervention   4
     
    Hello.
    You're right: it's unrelated. But it shows how the same machine, same OS, behaves differently.
    I'm going to wipe this keychain tomorrow, after backing it up. If I have to, I'll reassign a password to the user as root.
    0
  8. LEVINE Posted messages 127 Registration date   Status Member Last intervention   4
     
    Hello everyone :)
    Verdict? Resolved!

    I applied the solution found on the Fedora forum.

    First, I made a CloneZilla image, then I logged in under the user account, moved the .local/share/keyrings to Documents (to replace it later in case of a problem), and it worked.

    Thank you for your help :hello:

    But... how do I add the [RESOLVED] tag?
    0
    1. mamiemando Posted messages 33174 Registration date   Status Moderator Last intervention   7 944
       
      Thank you for your reply, here is how to mark a topic as resolved. I'll take care of it this time.

      Best of luck!
      0