Implement ChromeIPass and PassIFox compatibility

[fabriceb]

Using the specs best described here https://github.com/pfn/keepasshttp/blob/master/test/tests/test-kph.js implement a KeepassHTTP compatible interface to work with Chrome and Firefox Keepass integrations.

I am ready to work on this

[gesellix]

Yes, that's what I would also like to be implemented. Since I have not completed the write-support, yet, I would be glad if you could already start working on the browser integration. To reduce future conflicts, I just merged the current write-support branch into master, so you can start working based on a more recent state.

Cloning the repo, npm install and npm test should get you started. Would you need some more information?

[fabriceb]

I have already cloned and installed the repo. So the next step for me is some time and understanding the keepasshttp protocol. I will let you know as soon as I do something.

[gesellix]

great :)

I guess you don't necessarily need to understand the keepasshttp protocol, but more important would be to understand how the Chrome/Firefox plugins work. I would hope that the plugins could directly talk to the keepass-node backend, just like the angular frontend does.

[gesellix]

@fabriceb Hey, did you have some time to work on this? If not: I'll soon try to implement a React based ui as Chrome extension. This is more or less some kind of playground, though, so no pressure :-)

[zohead]

@gesellix Will the Chrome extension you planned still need Node.js on a server?
I'm interested in making this works in a standalone Chrome Packaged App (need to port keepass.io without Node.js).

[gesellix]

@zohead I personally don't have an idea how one could store the keepass file safely without a secure backend (in this case implemented in node.js). So I would prefer to still use a node.js backend. I also don't want to be dependent on a dedicated device where the keepass file is saved.

If it isn't too much hassle including other "backends", like node.js, Google Drive, Dropbox, etc, I'd be glad if you started with your standalone variant and I could extend it to use the node.js backend. I would beg you to keep this in mind when implementing the Chrome extension. If you don't like to reinvent the wheel, you can have a look at the BrowsePass Chrome extension.

[ppmathis]

@zohead If you need any help or assistance with porting keepass.io so that it doesn't use Node.js, feel free to contact me. I had that actually planned for the future (including rewriting a few bits of the code), but didn't find the time to do so yet.

@gesellix Sorry for intervening here :)

A chrome extension / packaged app would be really cool though - I even started on doing so once, but I hate frontend coding, heh. I also tried to use those new HTML5 crypto libraries, but they kinda sucked last time I tested them, unfortunately.

[zohead]

@gesellix Your are right, while a Chrome packaged app with read/write access to keepass database would be really useful for Chromebook users. Keepass database can be stored locally or on Google Drive via Chrome's Filesystem API.
Chrome OS user can only run Node.js in Crouton chroot environment (it's also inconvenient to use Node.js on ARM Chromebook).
BrowsePass app is really a good start, just lack write support for now.

@NeoXiD It will be quite helpful if you make keepass.io works for Chrome without Node.js. ^_^

[gesellix]

hey, now I guess all relevant people are talking to each other :-)
I'm also willing to help, for frontend stuff or even "boring" user testing as well, so just leave a note here!
Am 29.07.2015 11:29 vorm. schrieb Pascal Mathis notifications@github.com:@zohead If you need any help or assistance with porting keepass.io so that it doesn't use Node.js, feel free to contact me. I had that actually planned for the future (including rewriting a few bits of the code), but didn't find the time to do so yet.

@gesellix Sorry for intervening here :)

A chrome extension / packaged app would be really cool though - I even started on doing so once, but I hate frontend coding, heh. I also tried to use those new HTML5 crypto libraries, but they kinda sucked last time I tested them, unfortunately.

—Reply to this email directly or view it on GitHub.

[gesellix]

ah, yes I didn't have Chromebooks in mind. There's also some offline mode relevant, where a standalone extension would help. so, don't get me wrong when I'd also like a node backend on top of that :-)

Am 29.07.2015 12:15 nachm. schrieb Uranus Zhou notifications@github.com:@gesellix Your are right, while a Chrome packaged app with read/write access to keepass database would be really useful for Chromebook users. Keepass database can be stored locally or on Google Drive via Chrome's Filesystem API.
Chrome OS user can only run Node.js in Crouton chroot environment (it's also inconvenient to use Node.js on ARM Chromebook).
BrowsePass app is really a good start, just lack write support for now.

@NeoXiD It will be quite helpful if you make keepass.io works for Chrome without Node.js. ^_^

—Reply to this email directly or view it on GitHub.

[gesellix]

... and why looks answering via mail so shitty?

[gesellix]

@zohead @NeoXiD there's a new branch https://github.com/gesellix/keepass-node/tree/chrome-extension where I'd like to work on the Chrome extension. It should already be installable in a normal Chrome, I didn't have a chance to check it with ChromeOS - most important would be to add a permission to upload files, I guess.

If you don't like to work on personal forks, you may add PRs to that branch and I'll merge them more or less without checking your changes.

[gesellix]

Apart from making it work on ChromeOS or in offline mode, we should have a look at the ChromeIPass features to recognize URLs, password fields to enable the extension to conveniently suggest the best KeePass entry.

[zohead]

@gesellix Is it possible to make this chrome extension simple as KeePass desktop program and only implement as a KeePassHttp server, then let ChromeIPass do the "dirty" work with URLs/username/Password fields?