To avoid that the database file might get into different versions I’m using a very different scenario: So I must live with this trade-off.ĮDIT: mentioned that Keepass2Android will hold a offline version in case you access the keepass database via webdav. I would never give my passwords to an external. (Thanks hope this will help you a bit! My clunky solution was the only way for me to have my passwords available on all my devices and not using services like lastpass. You can directly access your database in the seafile cloud with Keepass2Android via Webdav and the app will provide you an offline version of the database as well in case you loose internet connection. As soon as your phone logs into your network, a new version of the database will be deployed if there is any. You can automate the sync at home in your network, via samba, ftp, … There are apps for this as well. (Remember: Webdav is not working with encrypted libraries.) Because the Seafile mobile app has no sync feature, you can use one of the many mobile sync apps which support sync ober Webdav and sync it over these apps and Seafile’s Webdav. If you want a decent sync on mobile, there are two main solutions: I use Keepass on my phone also as read-only. So, on my mobile phone the database can be outdated, but I always have one version on my phone and always can get the newest database version as long as I have internet access. On mobile, I deploy my Keepass database manually by just simply downloading the file via the Seafile Android App or at home in my network over samba. (In addition: This way of use will become much safer, when Seafile gets “read-only-sync” in later versions.) Mostly you just need your passwords and don’t add/change a lot, so this is ok. So after all: Only one device writes changes, the other devices are read only. (If I change it elsewhere I make a note and check the sync, but it’s better to note the change and catch up with it later on the main machine.) In my case, I have one “main working machine” and I try to always change my keepass database only here. The Keepass database is synced by the Seafile client over my different PCs. (Can be with a simple document file and a syncing services, too. So, to summerize: If you are a very careful user, syncing a keepass database with such services like Seafile over different devices, can work, but is very, yeah let’s say, dangerous. are not better in this point), so you might restore every version of you DB file, BUT in these use case scenario you first have to realize that you maybe have created some mistakes at all.) (Seafile has very good file versioning and okeyish conflict handling (Dropbox and Co. So, there is always just one version of your keepass database at the same time available.Ĭonclusion: If you sync your Keepass database (remember: just one single file) over different devices (maybe not always in sync because of not always online simultanious use worst: more than one Keepass database user, …), you can/will very likely end up with different versions/file conflicts/overwrites and so for the worst case with password loss. and the way they work, you will see, that even if they support delta sync (Seafile does, when using the desktop clients) the smallest entity for the user to see and for apps like Keepass to use is the file. Second: When you now look closer to file services like Seafile, Dropbox, etc. Of course there is a database in it, but you don’t access just a database, you access and change one single file, its time stamp, … On Android I’m using Keepass2Android, which is a very good app.įirst things first: If you use Keepass (and derivates) everything is saved in one single file! And that is the the crux. Is anyone seeing anything similar? Any help with where or how we should raise this issue would be helpful.I’ve used Keepass for some years and switched reacently to KeepassXC 2.2.0, because of their community effort and because it is running much smoother on my Linux machines, than Keepass on Mono. For reference, our users are seeing this on iOS 15.3.x and iOS 15.4, so latest stable production releases. So something recent looks to have changed, either in the accountchooser.js code, or in how "document.domain" is calculated/determined on iOS. We use the OneDriveSDK via a Cocoapod (nothing has changed here in years) and our App hasn't changed anything here in a similar time frame. The trouble is this URL is generated by " accountchooser.js" in code that looks like this:Į.skyApiBaseUrl = "." + document.domain + "/API/2/" Obviously, the URL looks incorrect (too many "onedrive."'s in there.). You might be connecting to a server that is pretending to be “.com” which could put your confidential information at risk." "The certificate for this server is invalid. About 5 days ago users of our App have started receiving a certificate error:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |