From what I have understood of the bug description, the original poster is looking for a way to mount a remote network share using cifs and its kerberos ticket as credential to authenticate on remote server.
The mount command requires root privileges so must be called as root in some way. This could be achieved using sudo or using suid. From my point of view, nothing kerberos related here.
The command line I have suggested to use in comment #11 does this: use sudo to run mount as root and use the already acquired kerberos ticket to authenticate on remote server to access cifs network share.
Also, I understand that what have changed is that it used to works with the user kerberos ticket before Meerkat release without any tricky option.
Probably that in version prior to Meerkat, cifs-utils what not restricting its credential ticket search based on ticket file owner.
However, the owner match can be configured using the uid option or cruid option for cifs-utils >=4.8) so there is a simple way to allow the use of the user owned kerberos ticket file.
As you pointed, I could be wrong in my understanding, so please tell me on which point.
From what I have understood of the bug description, the original poster is looking for a way to mount a remote network share using cifs and its kerberos ticket as credential to authenticate on remote server.
The mount command requires root privileges so must be called as root in some way. This could be achieved using sudo or using suid. From my point of view, nothing kerberos related here.
The command line I have suggested to use in comment #11 does this: use sudo to run mount as root and use the already acquired kerberos ticket to authenticate on remote server to access cifs network share.
Also, I understand that what have changed is that it used to works with the user kerberos ticket before Meerkat release without any tricky option.
Probably that in version prior to Meerkat, cifs-utils what not restricting its credential ticket search based on ticket file owner.
However, the owner match can be configured using the uid option or cruid option for cifs-utils >=4.8) so there is a simple way to allow the use of the user owned kerberos ticket file.
As you pointed, I could be wrong in my understanding, so please tell me on which point.