Closed erdnamulb closed 1 year ago
Anything special with you W10 install? I just tried on a W10 machine without any issue:
As mentioned: the problem exists on three different computers, all running Win10 pro with latest patches - nothing special (no dev environments or similar - just office PCs or Laptops)
All entries were generated with Moolticute versions <1.00.0. With 1.00.0 I cannot access a single one to edit it. If I try in credentials management, the App says that access was denied (although PIN was given and I'm in the credentials management mode). Also strange characters appear in credentials management entries. This only occurs with 1.00.0. Works all fine with 0.55.
Integrity check of one of the Mooltipass (I have 2 mini which all show same behavior with 1.00.0) for information:
I will generate a new user database with 0.55 and/ or 1.00.0 and generate some fake entries to see if there's a difference and show you some screenshots without private data...
could you enable the debug logs, and send us the logs for when you try to access a given credential? I'm guessing moolticute is querying the device and somehow you're not getting a prompt on it
Now I did the following: 1) take fresh card, insert, create new user with Mooltipass mini (NOT BLE!) connected to Win10 pro, Moolticute 0.55.0 2) generate 3 sample entries with moolticute Application 3) disconnect & move device to Win10 pro Laptop with Moolticute 1.00.0 running 4) enter credentials editing mode and there the strange characters appear and credentials can not be managed/ edited 5) logged all in debug mode with the Moolticute 1.00.00 6) connecting back to Win10 pro machine with Moolticute 0.55 shows no problems - behavior as expected (Mooltipass mini BLE shows none of these problems - works fine with 0.55 and 1.00)
...it does not matter on which machine I create the credentials. As long as I do this in 0.55 and want to access them in 1.00.0 it will fail. Even just showing the passphrases in credentials mode gives the error "access denied" ("Kennwortabfrage wurde abgelehnt" see screenshot below). The Mooltipass only shows "credential mode" all time - no other visible reaction on the device.
Trying to access credentials on v1.00.0 has been logged in debug mode - see file above. Can't believe that I'm the only one having this behavior... :-o And by the way: thanks for the time you guys are investing in Moolticute and issues like this one here! 🥇
@deXol I think the terminating 0 detection isn't happening, and maybe credential querying is sending the wrong string as well
@erdnamulb : we've just released 1.00.1 at https://github.com/mooltipass/moolticute/releases .. could you give it a quick go and let us know if things improved?
Tested on all available Computers with all available devices -> works like a charm. All entries accessible and can be edited as expected. @limpkin @deXol Thanks for the lightspeed-solution!
woot!
Expected behavior
When I open the credentials management in Moolticute, I want to change/ edit existing entries.
Actual behavior
Mooltipass asks for permission/ code for credential management; Moolticute loads data from Mooltipass mini; the list being shown of my existing entries ist not editable, nor clearly readable; lots of special characters are showing up beside the credential data fragments; no editing can be done, only "leave credentils management"; problem occurs with 2 different databases on 2 different Mooltipass mini devices with 2 different cards.
Step by step guide to reproduce the problem
1) use Mooltipass mini (NOT BLE) 2) insert card, enter code 3) open Moolticute -> Enter credentials management Mode -> confirm on device/ enter PIN 4) look at credentials in Moolticute: no entry can be edited (not clickable); entries contain strange special characters 5) occurs with 2 independent devices and 2 independent credential databases and 2 different cards
Moolticute Version
1.00.0
Operating System
Mention if you are using either:
Mooltipass Device
The Mooltipass Mini
EDIT: Downgrading Moolticute from 1.00.0 to 0.55.0 solves the problem and all entries can be edited on the devices. So definitely a problem with the Application.