Support for HTTPS and reading from remote networks #165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…remote access and https bindings
Signed-off-by: Marcus Heese <[email protected]>
|
This is the wiki I was talking about: https://github.com/mheese/keepasshttp/wiki/Listener-Configuration |
|
👍 Sounds like a nice idea. I'd really like to see this merged. |
|
I agree. I had to change the UpdateUrl though so that I was able to completely test it. |
|
Please put local customizations on a separate branch |
|
Also, please don't re-indent code, it makes it impossible to review |
|
Any further progress in this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I should have done this pull request a long time ago.
My branch allows for using HTTPS and reading from remote networks. I secure this with using client certificates. I also wrote a wiki entry on how to install this on windows. Unfortunately this is rather complicated and is probably not possible for the average user.
So why did I want to have this? I'm running Mac OS X. However, all my passwords since years are accumulating in KeePass. All the existing OS X ports or mono versions are just awkward and none of them work properly (that includes the pretty expensive KyPass). So what I am doing is the following: I'm running KeePass on Parallels and I offer my KeePass database over "network" to my OS X browsers. It works extremely well and I finally have a good working solution.
I have also updated the passifox repositories, so that the chrome plugin can use this version of keepasshttp. Firefox works already out-of-the-box.