> The configuration files appear to be readable in the sandbox, but I'm
not seeing the ticket available there even after running 'kinit' outside
of the sandbox and then 'snap connect firefox:kerberos-tickets'.

That is expected because Snapd relies on KRB5CCNAME to expose the ticket
to a place from which the snap can read the ticket.

What you could try is to manually run

  KRB5CCNAME=FILE:/tmp/krb5cc_{ETC} firefox

where /tmp/krb5cc_{ETC} is the ticket's path as you see outside the
sandbox.

> These systems aren't domain-joined, so a ticket is not created by
logging in, which I think is what you're expecting to happen. I can't
login with my external e-mail, just as a local user.

Indeed, I was expecting that workflow. I did not know that one logs in
as a normal user. But after a Kinit, your KRB5CCNAME is set-up in the
environment, correct? Then try to launch Firefox from that terminal
where you did Kinit.

>  Does the 'firefox:kerberos-tickets' plug allow access to tickets in
'/tmp'?

Not really, because /tmp is private to every snap so the host's /tmp is
entirely invisible inside the snap sandbox.

> Either way, I think the issue establishing HTTPS connection must first
be solved before I can really test Kerberos with this Snap. Is there
some prerequisite reading I should go through before trying to test the
Firefox snap package?

Not really; Also I am certainly missing bits of knowledge to grasp what
is going on in your case. It must be the interaction with certificates
but my test case doesn't include that. I'll keep looking and will ask
around but feel free to share documents that might help me understand
the issue further, if you have any.

> And thank you for working on a fix!

My pleasure!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849346

Title:
  [SRU] kerberos GSSAPI no longer works after deb->snap transition

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to