Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chromeIPass not working after update to 0.3 #48

Open
morriswinkler-simple opened this issue Nov 28, 2017 · 10 comments
Open

chromeIPass not working after update to 0.3 #48

morriswinkler-simple opened this issue Nov 28, 2017 · 10 comments

Comments

@morriswinkler-simple
Copy link

morriswinkler-simple commented Nov 28, 2017

  MacPass 
  Version 0.7.3 (17830)

  MacPassHTTP
  Version 0.3 (78)

  chromeIPass
  Version 2.8.1

  chromeIPass reports 
  Your running version of KeePassHttp:KeePassHTTPKit
  Latest available version of KeePassHttp:1.8.4.2

On start of MacPass I get

2017-11-28 10:56:52.739 MacPass[58451:18480459] Looking for external plugins at /Users/morris/Library/Application Support/MacPass.
2017-11-28 10:56:52.739 MacPass[58451:18480459] Looking for internal plugins
2017-11-28 10:56:52.739 MacPass[58451:18480459] No internal plugins found!
2017-11-28 10:56:53.027 MacPass[58451:18480459] Unable to Start KeePassHTTP Server: (null)
2017-11-28 10:56:53.066 MacPass[58451:18480459] Loaded plugin instance MPHMacPassHTTP
2017-11-28 10:56:53.147 MacPass[58451:18480459] Plugin com.hicknhacksoftware.MacPassHTTP already loaded!

Telnet to the server works on port 19455, but chromeIPass is not working anymore.

i attached wireshark and got

POST / HTTP/1.1
Host: localhost:19455
Connection: keep-alive
Content-Length: 54
Origin: chrome-extension://ompiailgknfdndiefoaoiligalphfdae
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Content-Type: application/json
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-GB,en;q=0.9,en-US;q=0.8,de;q=0.7
Cookie: session=XXX

{"RequestType":"test-associate","TriggerUnlock":false}
HTTP/1.1 200 OK
Cache-Control: no-cache
Content-Length: 167
Content-Type: application/json
Connection: Close
Server: GCDWebServer
Date: Tue, 28 Nov 2017 10:06:32 GMT

{"Hash":"E66C3B88-F61C-40C4-908D-521E38D63CDAB51D8804-C9E6-485D-97F0-054703281FC4","Version":"KeePassHTTPKit","RequestType":"test-associate","Success":false,"Count":0}

Any Idea what is going on here. looks like login isn't working.

@morriswinkler-simple morriswinkler-simple changed the title Unable to Start KeePassHTTP Server: (null) chromeIPass not working after update to 0.3 Nov 28, 2017
@mstarke
Copy link
Member

mstarke commented Nov 28, 2017

Take a look at ~/Libarary/Application Support/MacPass it seems there is more than one instance of the plugin residing in this folder.

@morriswinkler-simple
Copy link
Author

Ok, i removed the second instance, which does not change anything on the outcome,

2017-11-28 10:56:53.027 MacPass[58451:18480459] Unable to Start KeePassHTTP Server: (null)

is now gone, but chromeIPass will not really connect to my database

@morriswinkler-simple
Copy link
Author

I still have the same output from Wireshark with an reponse stating:

{"Hash":"020EA127-2BE0-4A31-AFCC-B3400670C304(null)","Version":"KeePassHTTPKit","RequestType":"test-associate","Success":false,"Count":0}

@morriswinkler-simple
Copy link
Author

I think I will reinstall the old version and look at the network output to figure if something with the login is not working, but well it returns success=false

@mstarke
Copy link
Member

mstarke commented Nov 28, 2017

What version did you use before 0.7.3? 0.7.2?

I did change the settings key for remote connections for KeePassHTTP but that should not affect you - or did you enabled this before?

@mstarke
Copy link
Member

mstarke commented Nov 28, 2017

The client hash is generated with the trash UUID which is null in your case - this might be an implementaion error. I have to check how keepasshttp handles this.

@mstarke
Copy link
Member

mstarke commented Nov 28, 2017

This actually is a unfortunate design decision on the part of keepasshttp. If you synchronise a database without a trash and then it will get generated you have to re-synchronize since the client hash has changed. The actual string format doesn't matter that much so I guess it's ok the way it is. Keepass seems to omit the dashes in the string will add an empty string if no trash is present

@morriswinkler-simple
Copy link
Author

morriswinkler-simple commented Nov 28, 2017

@mstarke looks like it comes from databases that are still stored within my chromeIPass settings, i created a new chrome profile and it worked.

screen shot 2017-11-28 at 16 28 43

I think i just need to figure out how to delete them, button doesn't work. So not MacPass related.

@mstarke
Copy link
Member

mstarke commented Nov 28, 2017

I'm sorry for my lack of support but I just ported the plugin and never spent much time on the details. I should try to get into the setup of KeePassHTTP a bit more to fix such problems since it seems to happen from time to time and this setup is rather cumbersome to debug for normal users, you're an exception with your ability to telnet the requests in clear text :)

@martin-braun
Copy link

Both chromeIPass and its fork https://github.com/smorks/keepasshttp-connector are discontinued. I don't know if KeePassXC-Browser is compatible, this extension isn't working for me at all. Is there anything that can be done, so I can integrate MacPass into Brave?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants