All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Milan Knížek" <knizek.confy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: mount.cifs multiuser w/o krb5? How?
Date: Wed, 11 Jul 2012 21:05:31 +0200	[thread overview]
Message-ID: <cone.1342033531.608672.10432.1000@athlon> (raw)

sorry, sent from a wrong email address and probably silently rejected by  
Majordomo...
-------- Přeposlaná zpráva --------
Předmět: Re: mount.cifs multiuser w/o krb5? How?
Datum: Tue, 10 Jul 2012 23:01:32 +0200

Jeff Layton writes:

>> cifscreds add is more or less equivalent to a command like this:
>
>     $ keyctl add logon cifs:a:ip_address 'username:password' @s
>

There seems to be a general problem with adding keys (@s) to the default  
"session" keyring. Adding user type keys (@u) works.

$ keyctl add logon description data @s
does not add anything to the _uid_ses:UID keyring, which is automatically  
created after login.

Interestingly, when a new session keyring is added, then it works:

[root@client ~]# su - zmrzlinka
[zmrzlinka@client ~]$ keyctl show
Session Keyring
1037083570 --alswrv   1001    -1  keyring: _uid_ses.1001
 578017679 --alswrv   1001    -1   \_ keyring: _uid.1001
[zmrzlinka@client ~]$ cifscreds add toillet
Password:
[zmrzlinka@client ~]$ keyctl show
Session Keyring
1037083570 --alswrv   1001    -1  keyring: _uid_ses.1001
 578017679 --alswrv   1001    -1   \_ keyring: _uid.1001
[zmrzlinka@client ~]$ keyctl session new-session
Joined session keyring: 871855811
[zmrzlinka@client ~]$ keyctl show
Session Keyring
 871855811 --alswrv   1001   100  keyring: new-session
[zmrzlinka@client ~]$ cifscreds add toillet
Password:
[zmrzlinka@client ~]$ keyctl show
Session Keyring
 871855811 --alswrv   1001   100  keyring: new-session
 244698182 ----sw-v   1001   100   \_ logon: cifs:a:192.168.1.3

Milan

             reply	other threads:[~2012-07-11 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 19:05 Milan Knížek [this message]
2012-07-11 19:56 ` mount.cifs multiuser w/o krb5? How? Jeff Layton
  -- strict thread matches above, loose matches on Subject: below --
2012-07-11 19:06 Milan Knížek
2012-07-04 18:52 Milan Knížek
     [not found] ` <1341427937.3252.6.camel-77nuZImz6nKt3pJmeLR6bw@public.gmane.org>
2012-07-06 18:15   ` Jeff Layton
     [not found]     ` <20120706141543.1b564c11-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-07-06 22:09       ` Milan Knížek
     [not found]         ` <1341612593.26748.9.camel-77nuZImz6nKt3pJmeLR6bw@public.gmane.org>
2012-07-09 10:26           ` Jeff Layton
2012-07-10 21:01             ` knizek-VIXq6x/3rUk
2012-07-10 21:05             ` knizek-VIXq6x/3rUk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cone.1342033531.608672.10432.1000@athlon \
    --to=knizek.confy-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.