Closed anoduck closed 1 year ago
the yaml
file is for service configuration. If you want your password file at /etc/systemd/user
you need to give permission to your user to read it.
The last two errors are dbus errors, look at https://github.com/yousefvand/secret-service/tree/main/docs
the
yaml
file is for service configuration. If you want your password file at/etc/systemd/user
you need to give permission to your user to read it. The last two errors are dbus errors, look at https://github.com/yousefvand/secret-service/tree/main/docs
This will take some pondering, and a review. My system is OpenBSD, which neither has systemd or a linux variant of dbus. It has messagebus.
for systemd you can run secretserviced
file manually but for dbus I have no idea because API is based on dbus.
@yousefvand I am getting it figured out now. I can just add secretserviced
to my ~/.config/i3/config
file and have it run on login. I also learned DBUS and messagebus are basically the same thing, dbus actually launches a service called messagebus in linux computers.
Looks like I will have to work around a Well, nevermind. du
issue, this happens fairly often when running OpenBSD. Commands like grep
, stat
, and du
are not the gnu variant, but you can install the gnu variant and alias them.
She is built, and now we are getting somewhere. Just not sure how to set the masterpassword, since I am not running systemd.
OK, well she is up and running. Everything looks good. The tests are checking out just fine. So everything is good on your end. I just need to get with the developer of nheko and work out why his app is not picking up on it.
Recommended trying this repo by a developer, and understandably he was attempting his best to find a resolution, but did not install it himself.
So, it built without a hitch, and I was successful at configuring it to run from
~/.local/bin
without systemd using dinit, using a 32 character password.So... I still have no clue what the user configuration file is for at
~/.secret-service.yaml
. It was not created automatically on running the script, and there is no explanation of what is supposed to be located within it or even what it's function is for. So, it's purpose is quite mysterious.Although the script runs, and does appear to use the freedesktop socket of dbus. This seems to be the extent of it's function. Since, there is no other information on it's functionality.
When attempting to probe the service using keyring, I received the following error.
which can't be good.