Thanks to all for writing.
Pag and token are mostly needed at login. Could all be done under PAM.
If there is no PAM given, the user must do it in his Shell startup profile.
The use of pagsh there is tricky (but possible) , but a working aklog
-setpag
makes that easy and straightforward. (O
In particular, the kernel functionality to modify the groups/keyring
contents/etc. of the parent process has not been present for a long time.
So the kernel version is arguably more relevant than the OpenAFS version.
-Ben
On Thu, Oct 18, 2018 at 06:43:25AM -0400, Malato, Andy wrote:
> The -setpag
The -setpag has long been deprecated and should no longer be used. You
should be using pagsh instead.
On Thu, Oct 18, 2018 at 6:08 AM, r.laatsch
wrote:
> The aklog from openafs-1.6.23 honours the flag -setpag correctly, i.e.
> sets a PAG and token if a krb5 ticket is present.
>
> If I get an
The aklog from openafs-1.6.23 honours the flag -setpag correctly, i.e.
sets a PAG and token if a krb5 ticket is present.
If I get an aklog compiled in openafs 1.8.x, aklog -setpag neither sets
a PAG nor a token; simple
aklog (without -setpag) gives a token without a PAG (I dont want that).
P
