From: knizek-VIXq6x/3rUk@public.gmane.org
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Milan Knížek"
<knizek.confy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mount.cifs multiuser w/o krb5? How?
Date: Tue, 10 Jul 2012 23:01:32 +0200 [thread overview]
Message-ID: <cone.1341954092.296868.13606.1000@athlon> (raw)
In-Reply-To: 20120709062608.3a67445f@tlielax.poochiereds.net
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
next prev parent reply other threads:[~2012-07-10 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 18:52 mount.cifs multiuser w/o krb5? How? 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 [this message]
2012-07-10 21:05 ` knizek-VIXq6x/3rUk
2012-07-11 19:05 Milan Knížek
2012-07-11 19:56 ` Jeff Layton
2012-07-11 19:06 Milan Knížek
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.1341954092.296868.13606.1000@athlon \
--to=knizek-vixq6x/3ruk@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=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.