search

clipperz / password-manager

Clipperz is an online vault and password manager that knows nothing about you and your data. Everything you submit is locally encrypted by your browser before being uploaded to Clipperz. The encryption key is a passphrase known only to you and Clipperz could never access your data. Clipperz is built upon open proven and trusted encryption algorithms.
https://clipperz.is
GNU Affero General Public License v3.0
726 stars 134 forks source link

Clipperz.PM.DataModel.User.exception.LoginFailed #69

Closed DaPutzy closed 5 months ago

DaPutzy commented 9 years ago

on a fresh install I:

Frontend-Error:

Clipperz.PM.DataModel.User.exception.LoginFailed

PHP-Error:

2015/05/27 22:01:46 [error] 27473#0: *305 FastCGI sent in stderr: "PHP message: registration
PHP message: result: {"result":{"lock":"","result":"done"}}" while reading response header from upstream, client: 77.64.189.242, server: U_DONT_NEED_TO_KNOW_MY_DOMAIN, request: "POST /index.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "U_DONT_NEED_TO_KNOW_MY_DOMAIN", referrer: "http://U_DONT_NEED_TO_KNOW_MY_DOMAIN/gamma/index.html"
2015/05/27 22:01:47 [error] 27473#0: *305 FastCGI sent in stderr: "PHP message: handshake
PHP message: result: {"result":{"s":"1fd35b3b4acbb0e4bebfbd18e0dcd4f32a5e956b0946c9b1ec0001a9dda74103","B":"1caac82469682f108ed5ce1df76bc73e2956b0ab1d8462b48b31d6d20c02c0b06"}}" while reading response header from upstream, client: 77.64.189.242, server: U_DONT_NEED_TO_KNOW_MY_DOMAIN, request: "POST /index.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "U_DONT_NEED_TO_KNOW_MY_DOMAIN", referrer: "http://U_DONT_NEED_TO_KNOW_MY_DOMAIN/gamma/index.html"
2015/05/27 22:01:47 [error] 27473#0: *305 FastCGI sent in stderr: "PHP message: handshake
PHP message: credentialCheck
PHP message: result: {"result":{"error":"?"}}" while reading response header from upstream, client: 77.64.189.242, server: U_DONT_NEED_TO_KNOW_MY_DOMAIN, request: "POST /index.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "U_DONT_NEED_TO_KNOW_MY_DOMAIN", referrer: "http://U_DONT_NEED_TO_KNOW_MY_DOMAIN/gamma/index.html"
2015/05/27 22:01:47 [error] 27473#0: *305 FastCGI sent in stderr: "PHP message: handshake
PHP message: result: {"result":{"s":"112233445566778899aabbccddeeff00112233445566778899aabbccddeeff00","B":"d2661284a6ec0759727a35c497250b46978f61acbace3b43ee8c4b566d96b476"}}" while reading response header from upstream, client: 77.64.189.242, server: U_DONT_NEED_TO_KNOW_MY_DOMAIN, request: "POST /index.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "U_DONT_NEED_TO_KNOW_MY_DOMAIN", referrer: "http://U_DONT_NEED_TO_KNOW_MY_DOMAIN/gamma/index.html"
2015/05/27 22:01:48 [error] 27473#0: *305 FastCGI sent in stderr: "PHP message: handshake
PHP message: credentialCheck
PHP message: result: {"result":{"error":"?"}}" while reading response header from upstream, client: 77.64.189.242, server: U_DONT_NEED_TO_KNOW_MY_DOMAIN, request: "POST /index.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "U_DONT_NEED_TO_KNOW_MY_DOMAIN", referrer: "http://U_DONT_NEED_TO_KNOW_MY_DOMAIN/gamma/index.html"
gcsolaroli commented 4 years ago

@mt-mrx when I said "official" I meant the online version; sorry for not being clear. I have managed to create three new accounts with the credentials you have listed without any issue. This seems to point at the backend as responsible for the misbehaviour. No idea what can cause the problem though.

aunxx commented 4 years ago

@gcsolaroli Ah, thank you for the clarification. I stand corrected. It makes more sense to use a combination of username and password presented to define the database entry. I must admit I probably didn't spend that much time looking at the username definition as it seemed to be working and I'm not very good with javascript.

aunxx commented 4 years ago

Hi, I created a new database, and new checkout of the code, and tested by creating a user with name 'abcd' and password '"abcd1234' The account registered without issue, and I was able to re-login and test the access. Similarly, I've tried using the abcd/$abcd1234 combination which also worked.

Can you let me know exactly how you created your database, and set the associated setting, and I'll try altering my database to see if I can re-create your issue.

Graham.

mt-mrx commented 4 years ago

Hi @aunxx

I'm baffled. Before and while commenting for the first time here I tested it multiple times, with the steps below. It always failed, repeatedly! I also setup a parallel install/db for testing, it had the same behaviour there as well. However now I cannot recreate the issue while writing the step by step instructions below. Neither on my test installation nor on my "live" setup. I know how it sounds ;-) but I didn't change anything between 5 days ago and now, especially not php/mariadb version or Firefox plugins. I used a different system (a) Fedora32/Firefox while reporting the issue, and the initial system (b) where I stumbled accross this issue was a different Windows10/Firefox system, when I tried it now I'm using another system (c) Windows10/Firefox, however I tested it again with the Fedora system (a) and the issue is gone there as well.

Could there maybe have been a browser caching issue because I'm using the same clipperz.example.de domain for my old 2011 installation as the new version (ad13fffb0...) from you?

------ issue dissappeared for now ----------- php: 7.3.19-1.el7.remi mariadb: 5.5.65-1.el7

database type: InnoDB collation: utf8mb4_general_ci

  1. Install 
    $ ./scripts/build clean install --backends php  --frontends delta
$ cp -a target/php/* ~/clipperzdev.example.de/
$ cd ~/clipperzdev.example.de/; ln -s delta/index.html; ln -s delta/manifest.appcache
  2. Add the db credentials and setup password to configuration.php.
  3. Go to https://clipperz.example.de/setup/
  4. Just hit "POG me up!" 
    CHECKED 5 OBJECT(S). FOUND 0 ERROR(S). HURRAY!

    DB tables are created as table type: MyISAM table collation type: utf8mb4_general_ci

  5. Go to https://clipperz.example.de/ click "sign up"
  6. Use ' abcd ' and ' "abcd1234 ' without spaces and single quotes. As a result the registration will fail. ------ issue dissappeared for now -----------
mt-mrx commented 4 years ago

Oh, I think I figured out what the problem was ... stupid me ...

Initially I didn't realize that you need the manifest.appcache file from the frontend in the root directory of clipperz.example.de as well, so I didn't link it. I fixed that while investigating the issue last week. I only saw the 404 error later in the apache logfile so I linked it in but it looks like the browser caches the frontend for a while without the manifest file and only fetches the manifest file when you either do a "Shift + F5" reload or clear the browser cache.

So if I don't link or copy the manifest.appcache file to my webserver root, clear browser cache and reload the site. I can recreate the issue. It's strange that it works at all and then only this partially, where some passwords work and others will fail.

mt-mrx commented 3 years ago

Hi @aunxx

I'm still running your clipperz version ad13fffb0727d3b1c6fe5f46944094b2d4b7bfaa but recently I stumbled accross an issue with a corrupted card which caused export issue, see details in #139 . Today I managed to recreate the issue and it looks like the corruption happens if I only modify the "Notes" field of a card when editing it, see also details in #139 .

Do you see the same problem in your installation?

Thanks

Matthias

aunxx commented 3 years ago

Hi Matthias, I had a single incident some time ago where a single record would hang when trying to view it. I did not work out what triggered the problem, but removing the entry from the database did fix the issue. At the time, my first thoughts were related to an unsafe handling of a quote character, but I couldn't find another way to trigger the issue. I will create a new install and see if I can recreate your issue, and see if I can work out what is causing the corruption. Alas, due to work commitments it may not be for a while though. :(

Graham.

aunxx commented 2 years ago

Hi All, For those still interested, I've discovered that this doesn't work in php 8.0. It's due to a depricated function and class contructors. I've fixed my version, and will be updating my git repo with the updated code in the next day or so.

Graham.

meoso commented 2 years ago

no plans to put on github @aunxx ? ( for those not up on info: git clone http://git.whoc.org.uk/git/password-manager.git )

aunxx commented 2 years ago

@meoso I should do really. I'll try and sort that this weekend. :)

cisco722 commented 10 months ago

Hi.

I've finally configured my webserver to allow access to my repository. Try cloning from:

http://git.whoc.org.uk/git/password-manager.git

Most of the changes are in a couple of files, and I'm fairly sure it isn't compatible with the main branch any more, but it works with PHP as a backend. There are problems if you try to update an old install with this code, but new installs seem to be okay. Any old installs can be persuaded to work with some mysql changes though.

Cheers, Graham. Hi Cheers,

Is your clipperz password manager repo still accessible?

I tried the official version but I can't make it work, it always returns "Clipperz.PM.DataModel.User.exception.LoginFailed"

I thank you if you can help me.

Francesco

nerdCopter commented 10 months ago

I tried the official version but I can't make it work, it always returns "Clipperz.PM.DataModel.User.exception.LoginFailed"

official version known to be a dead-project. @aunxx had the only known updated version, but i see it is currently error 403 (forbidden)

Looking at the forks, i see some updates. Maybe try one or all.
https://github.com/clipperz/password-manager/forks (look at all branches, not just master)

Someone should decide to maintain an "official" fork. This was a good product in it's time. Although I/we no longer use it, I do recall liking it better than most other projects.

[edited for spelling]

aunxx commented 10 months ago

Hi All. Let me check my repo config. It's not used very often so I suspect it may need to be updated to make it available again. Hopefully will be back shortly -- I'll post after I have checked.

Graham.

cisco722 commented 10 months ago

Hi All. Let me check my repo config. It's not used very often so I suspect it may need to be updated to make it available again. Hopefully will be back shortly -- I'll post after I have checked.

Graham.

thank you so much

aunxx commented 10 months ago

Hi.

It was modsecurity being a bit overprotective.

Can you try cloning the repo again please? I am not sure if I've tested much beyond php 8.0, and I only use the delta frontend.

Any issues you find then let me know and I may be able to have a look.

I rally probably should look at putting this elsewhere, but I am aware that the changes I had to make to sort the authentication out in php/java make this incompatible with the version here.

Graham.

nerdCopter commented 10 months ago 
$ git clone http://git.whoc.org.uk/git/password-manager.git
Cloning into 'password-manager'...
warning: redirecting to https://git.whoc.org.uk/password-manager.git/
error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
fatal: error reading section header 'shallow-info'
aunxx commented 10 months ago

Hi. Yes, just seen that. It worked for me so possibly client related. I've disabled the offending rule rather than trying to fix it, so please try again.

Graham.

nerdCopter commented 10 months ago

[...]] so please try again.

fixed! TY TY

aunxx commented 10 months ago

[...]] so please try again.

fixed! TY TY

No worries. Hope it all still works. I still use it without any issues. I've not setup a new install recently, so hopefully that's working still. I have a vague recollection of fixing that for php 8.0.

I never got around to changing the table storage method, I think it's an old one -- just something to be aware of.

Graham.

cisco722 commented 10 months ago

Hi. Yes, just seen that. It worked for me so possibly client related. I've disabled the offending rule rather than trying to fix it, so please try again.

Graham.

I can't clone the repo I always get this error

root@pwd:~# git clone http://git.whoc.org.uk/git/password-manager.git Cloning into 'password-manager'... fatal: unable to access 'https://git.whoc.org.uk/git/password-manager.git/': gnutls_handshake() failed: Error in protocol version

root@pwd:~# git clone https://git.whoc.org.uk/git/password-manager.git Cloning into 'password-manager'... fatal: unable to access 'https://git.whoc.org.uk/git/password-manager.git/': gnutls_handshake() failed: Error in protocol version root@pwd:~#

cisco722 commented 10 months ago

[...]] so please try again.

fixed! TY TY

On which linux version (distro) did you install it, which version of PHO and Mysql, does it also work with mariaDB?

Thank you for the information.

Francesco

aunxx commented 10 months ago

Hi,

The following error looks to me to be a shared cipher issue. I have the protocols set to require a modern set of client protocols. I think it requires TLS1.3 to connect I will downgrade the cipher requirements for a while to see if that helps you, but it may be that you need to check your supported ciphers to ensure that you're able to access the latest ones.

root@pwd:~# git clone http://git.whoc.org.uk/git/password-manager.git Cloning into 'password-manager'... fatal: unable to access 'https://git.whoc.org.uk/git/password-manager.git/': gnutls_handshake() failed: Error in protocol version

I've downgraded, so please try again and let me know.

Currently, my install is running on gentoo, and the web server is Nginx, and I use a mariaDB backend. I'm still using php8.0, as I've not updated to 8.1 yet.

Graham.

cisco722 commented 10 months ago

Hi,

The following error looks to me to be a shared cipher issue. I have the protocols set to require a modern set of client protocols. I think it requires TLS1.3 to connect I will downgrade the cipher requirements for a while to see if that helps you, but it may be that you need to check your supported ciphers to ensure that you're able to access the latest ones.

root@pwd:~# git clone http://git.whoc.org.uk/git/password-manager.git Cloning into 'password-manager'... fatal: unable to access 'https://git.whoc.org.uk/git/password-manager.git/': gnutls_handshake() failed: Error in protocol version

I've downgraded, so please try again and let me know.

Currently, my install is running on gentoo, and the web server is Nginx, and I use a mariaDB backend. I'm still using php8.0, as I've not updated to 8.1 yet.

Graham.

Thank you, you are really very kind, I tried but it still doesn't work, leave everything as before, now I install a new patch, a more recent Ubuntu LTS server and try again, I was testing it on an old machine.

I'll let you know if it works in a bit.

Thank you.

nerdCopter commented 10 months ago

push to github, less configuration :wink: and users can see the fixing-commits without cloning as well.

cisco722 commented 10 months ago

git clone http://git.whoc.org.uk/git/password-manager.git

hi, I installed Ubuntu LTS server 20.04 and updated with the latest updates but I always get an error when I try to clone your repository, version of git is 2.25.1

root@pwd:~# git clone http://git.whoc.org.uk/git/password-manager.git Cloning into 'password-manager'... warning: redirecting to https://git.whoc.org.uk/password-manager.git/ error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403 fatal: the remote end hung up unexpectedly root@pwd:~# git --version git version 2.25.1

aunxx commented 10 months ago

Hi All. I've uploaded it here: https://github.com/aunxx/password-manager

Hopefully that should allow access. Let me know if there are any issues.

Graham.

aunxx commented 8 months ago

I've updated to v1.2.0 which has my fixes for php8.0. Been a while and I thought I had fixed it, but found a couple of issues with creating new records. Let me know if you have any issues with this new version.

Graham.

gcsolaroli commented 5 months ago

The new /epsilon version has a fully open-source scala backend. So the php Community-Edition will be neglected even more. 😬 Cleaning up some old neglected issues.