Let me highlight this observation here and ask: is this kind of
control by executable path really useful on a normal Linux desktop? I
believe GNOME Keyring had something like that in the past and moved
away from it because it didn't not add any real security.
In this case, with gSSO, it really gets in the way.
For testing purposes I think you can bypass this check by a) compiling gsignond with
b) setting SSO_KEYCHAIN_SYSCTX environment variable to the path+name of the executable -
that's how we run unit tests.