![]() It makes sense to explore which sync options they provide, so that people are not locked into KeeWeb setup and can use other clients as well. It would be also great if this server exposes other APIs, for example, it may act as an FTP or S3 server for KeePass or KeePassXC. It's better to authenticate via OAuth rather than how it's done in most of WebDAV setups. But maybe not, depending on how people would like to authenticate there and what features we want to support, simple REST API may be more appropriate. One way it can be implemented without a lot of effort, is using WebDAV protocol, but pre-configured, so that we have CORS headers and so on. It should probably support more languages rather than PHP, for example, it can be also in node.js, which is quite popular now. I'd like to get some feedback on what is desired and who would prefer setting it up this way. I'm not sure if there's demand for a simple web server, but I see why it may make sense. It's a shame SFTP isn't viable, but as I understand it, that won't work from a browser. I don't know how broad the use for this would be, or how difficult it would be to build such a thing. ![]() No user name would be necessary the file name itself would serve that role. Creating a new KeePass file (other than the first one) would require having already successfully opened one file. When the KeePass file is next requested, the server would send the encrypted string and the client would respond with the unencrypted string, proving that the user supplied the correct passphrase. The server-side service would store both of these in a file of the same name with a different extension. ![]() For example, when a file is to be saved, in addition to the file, KeeWeb would send (over https) a randomly-generated string and the result of encrypting that same string with the passphrase. I'm thinking that some clever use of challenge-response should make it possible to use the same passphrase that encrypts the KeePass file to protect it from access/vandalism as well, so one wouldn't have to remember separate login credentials to access the file. Would it be possible to create a simple server-side service specifically to support KeeWeb that could be installed easily on any server or shared hosting account that supports PHP? but it demonstrates how completely flaky support for the WebDAV "standard" really is.) This is probably a NextCloud absurdity, not a KeeWeb problem. I've gotten it to work by installing NextCloud, which feels like swatting a fly with a sledgehammer. Even where it is supported, other confusions (CORS seems to be a common one) cause failures. Support on shared hosts is spotty, and if there is a simple way to add it, I couldn't find it. I think the reason is that WebDAV appears to be the only non-proprietary standard that allows client-side ECMAScript in a browser to update a file on a server without application-specific server-side support.Īlas, support for the WebDAV standard is not always so standard. KeeWeb itself only run in the browser and never sends any password to the server - that's the reason why it is quite secure to use it as long as you can trust your browser.KeeWeb can be used with a few different proprietary remote storage schemes, but the only non-proprietary standard is WebDAV. However that may be a security problem as the server part would then have to know the password used to create the database file. However KeeWeb is technically not able to store that file to Nextcloud as it is a pure browser based solution which has no access to the server at all, except the one file which was opened first using a security token from Nextcloud.Įdit: In addition - we could create a server based part in the integration app just to create a new KeePass database file with asking for a password for it. The file must be created by KeeWeb first (since it needs to be a valid KeePass database file which includes encryption information created by KeePass). Thank u is not Nextcloud which has to create the file. what is the "programming" issue? is there some code you can point to? ![]() I don't fully understand why nextcloud can't call nextcloud to create a file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |