Comment 4 for bug 1328622

That is via an SSH connection. I was running that on a machine in the 1SS datacenter via SSH.

Also, this was FIXED before after you switched to using sudo the last time we had problems. If you'll recall, we were using plainbox-insecure-policy to get around the pkexec problems over ssh.

Then you fixed plainbox-secure-policy to allow sudo and we went back to using that, and I have not heard anyone complaining about this issue.

AFAIK, this only recently (within the last week or two) started happening. This remote testing on the arm64 card I'm working on is the first place I've seen in.

It's not so much being prompted for sudo, I get that, and expect it to happen early on. THe problem is that I'm being prompted for sudo every time a test runs. This makes certification testing extremely time consuming and difficult, as I now have to actively monitor what should be a completely automated test run to enter a password yet again.

Given what Daniel has said, the only real option I see is using the insecure policy by DEFAULT.