None of the existing password managers filled my need, so i started to write my own (not the crypto ofcourse). Here it is :)
Why did I do it?
I'm totaly dependend on my password managing software, all my passwords are generated by random so non of them are rememberable.
During the last years I felt that my expectations and the traits of the password manager I was using grew appart.
I dislike subscription based software (especialy if i might need it to extract/recover my secrets out of an old file).
I dislike Web-UIs in native Apps.
So i was looking around but when I had an incident where a licensed password vault just forgot that it was licenced and denied access I had enough.
I wanted something that had a UI but also a data format that enables recovery with very little tools.
So thats what I started to create.
A-Pass saves its secrets as json content encrypted by age[1] (so no hasseling with gpg).
No information is visible without decrypting the files (no names / no urls).
The file structure should be easy to sync, but its not implemented yet.
unfortunately not anymore,
in the early days of firefox sync back when it was called wave it was easy to selfhost. Just throw some[1] php files to a host and it worked.
Then mozilla changed it to use multiple services (auth, ...)
it got difficult and the documentation wasn't easy to access.
There doesn’t have to run anything special on the IPhone.
In the early days iTunes could make backups on the local pc when the iPhone was connected via usb. Later on apple extended this to wifi: so if you had an iTunes running in your wifi and the iPhone joined a backup was done at the iTunes side.
I‘m not sure if this feature is still there, but I would have found this very useful if it would have been possible with the computer that is running anyways (as in the pi).