.... in order to simply the update process

Missing feature

Detecting when Caps Lock is enabled.

Justification

If the computer is in caps-lock, the device doesn't detect it and outputs a wrong password.
Then proceeds to detect the wrong password as a new login.

Workarounds

Just checking that Caps Lock is disabled, but half of the time my computer login password is all caps, and this comes up regularly.

Attached is a curated file
warnings.txt

Expected behavior

Once a minible has been paired and connected with Windows 10, disabling and then re-enabling Bluetooth on the device should result in the minible reconnecting.

Actual behavior

Instead of successfully reconnecting, Windows shows the status cycling between "Connected" and "Paired" with a period of between one and two seconds.

Step by step guide to reproduce the problem

1. Bring up the Windows 10 "Bluetooth & other devices" panel.
2. Pair and connect the minible to the Windows system in the usual way.
3. Once Windows shows the device connected, disable Bluetooth using the device's menu.
4. Wait for Windows to change the status from "Connected" "Paired".
5. Enable Bluetooth on the minible using the device's menu
6. Windows will now display the device's status cycling back and forth between "Paired" and "Connected".

Moolticute Version - If Involved

Not involved.

Firmware Version

AUX MCU version: v0.10
Main MCU version: v0.14

Operating System

• Windows 10

so the battery status is properly shown

Expected behavior

Mooltipass Mini BLE shouldn't crash/show weired screen content if you stop entering the PIN and wait until the device enters sleep mode.

Actual behavior

If you select the first number of your PIN code and wait until the Mooltipass enters sleep mode it start crashing or the screen is cutted in half.

Step by step guide to reproduce the problem

1. Enter your smartcard into the Mooltipass
2. Connect the Mooltipass with your PC
3. Select a random number for the first PIN but don't press the scroll wheel
4. wait until the Mooltipass enters sleep mode
5. Use the scroll wheel to wake up the mooltipass again.
6. The screen is cutted in half and only shows half of the content
   

Moolticute Version - If Involved

v0.42.31-testing

Firmware Version

AUX MCU version: 0.13
Main MCU version: 0.18

Operating System

• Windows 10 Enterprise 2016 LTSB

I haven't tested this with usernames, but passwords that contain a pipe character | show up correctly in credential management, display correctly on the device, but output as the plus-minus character ± instead. I haven't yet tested what it outputs if the password contains the ± though.

The Aux MCU version is 0.8, the Main MCU version is 0.7

moolticute and the device both report language as English US, and Bluetooth+USB layouts as USA and I'm only using US-based input devices with macos.

Expected behavior

Outputs the password including pipe characters |

Actual behavior

Outputs the password substituting pipe characters | with plus-minus characters ±

Step by step guide to reproduce the problem

• store a credential with a pipe character included in the password
• find the credential and output it [in this case over usb; bluetooth untested]

Moolticute Version - If Involved

0.42.8-testing

Operating System

macos 10.14.6

8<------------------------ BUG REPORT -----------------------------------------

Expected behaviour

When the BLE is connected to a "dumb" wall charger - in my case, an IKEA desk lamp with a USB port on the bottom - it shows the battery charging animation and, you would expect, charges its battery.

Actual behaviour

The battery does not seem to charge, though the animation does play. Verified by leaving it connected all day, and finding it was still on one bar of charge at the end.

Verified it further by connecting via a USB Type-C power meter, which showed the BLE drawing 0.06A while connected to the wall charger; switching it to being connected via a PC's USB port caused the BLE to draw 0.14A and charge normally.

Step by step guide to reproduce the problem

1. Run down the BLE battery
2. Plug into a "dumb" wall charger rather than a PC or other host device.
3. Go make a cup of tea or something.
4. Come back to see if the BLE's battery is charged.

Firmware Version

AUX MCU version: 0.11
Main MCU version: 0.16

Operating System

N/A

8<------------------------ END BUG REPORT -------------------------------------

Use one of the two templates below and delete the other. All issues not following this template will be directly closed.

8<------------------------ BUG REPORT -----------------------------------------

Expected behavior

Username and password will be entered from Mooltipass BLE at the position of the cursor in the active edit field.

Actual behavior

Username and password are not entered at the position of the cursor in the active edit field.

Step by step guide to reproduce the problem

• Connect Mooltipass BLE with MacBook Pro with BT.
• select under MacOS a position, where you want to insert the username.
• select Login on Mooltipass BLE
• select an entry type Login, confirm Ok
• select under MacOS a position, where you want to insert the password
• confirm Ok

Moolticute Version - If Involved

0.42.9

Operating System

MacBook Pro, Model 2017, MacOS Catalina (10.15.1)
Mention if you are using either:

• Windows 7/10
• Debian Based distribution
• Other Linux distribution
• MacOS

Other operating systems are not supported.

8<------------------------ END BUG REPORT -------------------------------------

Expected behavior

Not freeze when selecting a digit on the PIN screen if selecting while an animation is playing

Actual behavior

Freezes, restarts after 15 seconds.

Step by step guide to reproduce the problem

Go to any screen requiring a PIN (initial unlock, MMM)
Scroll and press in to Select while an animation is playing
Freeze occurs, wait 15 seconds for reset.

Moolticute Version - If Involved

v0.42.23-testing

Operating System

Windows 7
Windows 10
Arch

Mooltipass Extension

1.8.0

... when denying user registration prompt

Main->Aux: FIDO2 Message - missing command description: 4
Debug MSG: CborError: 0x27: ../src/fido2/ctap.c: 572: unknown error
Debug MSG: make_credential time: 40802 ms
Debug MSG: DATA [len: 0]
Debug MSG: [000]:
Debug MSG: cbor output structure: 0 bytes. Return 0x27
Debug MSG: CBOR writeback: 40805 ms
Debug MSG:
Debug MSG: length: 8
Debug MSG: adding a new cid
Debug MSG: length: 1
Debug MSG: CTAPHID_CBOR
Debug MSG: cbor input structure: 0 bytes
Debug MSG: cbor req:
Debug MSG: DATA [len: 0]
Debug MSG: [000]:
Debug MSG: CTAP_GET_INFO
Debug MSG: DATA [len: 54]
Debug MSG: [000]: A4 01 81 68 46 49 44 4F 5F 32 5F 30 03 50 6D B0
Debug MSG: [010]: 42 D0 61 AF 40 4C A8 87 E7 2E 09 BA 7E B4 04 A4
Debug MSG: [020]: 62 72 6B F5 62 75 70 F5 62 75 76 F5 64 70 6C 61
Debug MSG: [030]: 74 F4 05 19 04 00
Debug MSG: cbor output structure: 54 bytes. Return 0x00
Debug MSG: CBOR writeback: 59379 ms

Missing feature

When entering "Credential Management Mode" the message "authenticate yourself" is displayed during approximately 5 seconds. It could immediately display "Enter Your PIN".

Justification

I'm not sure it's necessary. After all it does not display "authenticate yourself" before asking the PIN when I put the card in.

Workarounds

Wait 5 seconds before entering the PIN

8<------------------------ FEATURE REQUEST ------------------------------------

Missing feature

When you enter the Bluetooth menu on the MBLE, the default option is "Pair new device." Choosing this, however, does nothing - because, by default, Bluetooth is switched off. You have to scroll across to "Enable Bluetooth," then attempt to pair a new device.

It would be smoother to disable the pair option (and, possibly, unpair) until Bluetooth is enabled. Alternative solutions would be to make "Enable Bluetooth" the default option if it's not already enabled (so you see that it's disabled before being given the option to pair) or to have the pair icon bring up an error with the option to enable Bluetooth.

Justification

From a first-user perspective, choosing "Pair new device" and having nothing happen feels like - though technically isn't - a bug.

Workarounds

Only to make sure you enable Bluetooth before attempting to pair a device!

8<------------------------ END FEATURE REQUEST --------------------------------

Expected behavior

If you set the active category to "work" the mooltipass should not freeze for some seconds if you visit a website where the credentials are saved under no category.

Actual behavior

If you set the active category to "work" or "home" the mooltipass freeze if you visit a website where the credential and username is saved under no category.

Step by step guide to reproduce the problem

1. plug in your smartcard and enter your pin code
2. set the active category to one of your categories
3. visit a website where the credential is not saved in the current active category
4. scroll through the Mooltipass menu and notice that it is stuck at the current menu icon. After 2-3 seconds you're able to scroll again.

Moolticute Version

v0.42.32-testing

DEBUG: (2020-02-25T08:20:04.319) :0 - JSON API recv: {"msg":"ask_password","client_id":83,"data":{"extension_version":"1.0","service":"gitlab.northernroot.net","fallback_service":"northernroot.net","login":"","request_id":82}}
INFO: (2020-02-25T08:20:04.319) :0 - "Get Credential"
DEBUG: (2020-02-25T08:20:04.319) :0 - Platform send command:  "GET_CREDENTIAL (0x0007)"
DEBUG: (2020-02-25T08:20:04.319) :0 - Full packet# 0 :  "[0xb8, 0x00, 0x07, 0x00, 0x34, 0x00, 0x00, 0x00, 0xff, 0xff, 0x67, 0x00, 0x69, 0x00, 0x74, 0x00, 0x6c, 0x00, 0x61, 0x00, 0x62, 0x00, 0x2e, 0x00, 0x6e, 0x00, 0x6f, 0x00, 0x72, 0x00, 0x74, 0x00, 0x68, 0x00, 0x65, 0x00, 0x72, 0x00, 0x6e, 0x00, 0x72, 0x00, 0x6f, 0x00, 0x6f, 0x00, 0x74, 0x00, 0x2e, 0x00, 0x6e, 0x00, 0x65, 0x00, 0x74, 0x00, 0x00, 0x00]"
DEBUG: (2020-02-25T08:20:06.619) :0 - Message payload length: 0
DEBUG: (2020-02-25T08:20:06.619) :0 - "Received answer: GET_CREDENTIAL (0x0007)"  Full packet: "04000700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
DEBUG: (2020-02-25T08:20:06.619) :0 - Platform send command:  "GET_CREDENTIAL (0x0007)"
DEBUG: (2020-02-25T08:20:06.620) :0 - Full packet# 0 :  "[0x2a, 0x00, 0x07, 0x00, 0x26, 0x00, 0x00, 0x00, 0xff, 0xff, 0x6e, 0x00, 0x6f, 0x00, 0x72, 0x00, 0x74, 0x00, 0x68, 0x00, 0x65, 0x00, 0x72, 0x00, 0x6e, 0x00, 0x72, 0x00, 0x6f, 0x00, 0x6f, 0x00, 0x74, 0x00, 0x2e, 0x00, 0x6e, 0x00, 0x65, 0x00, 0x74, 0x00, 0x00, 0x00]"
DEBUG: (2020-02-25T08:20:09.073) :0 - Message payload length: 0
DEBUG: (2020-02-25T08:20:09.073) :0 - "Received answer: GET_CREDENTIAL (0x0007)"  Full packet: "04000700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
WARNING: (2020-02-25T08:20:09.073) :0 - Credential get for fallback service failed

Firmware Version

AUX MCU version: 0.13
Main MCU version: 0.18

Operating System

• Windows 10 2016 LTSB

• "online file editing mode" that a user could use to write some secure notes. On the device, only require one prompt to access the file, automatic save when note is closed.

Expected behavior

I expect bluetooth to work (not really :p)

Actual behavior

When I connect bluetooth to the computer, sometimes, after some time it disconnects. When I try to disable bluetooth in the device, it freezes.

Step by step guide to reproduce the problem

Connect to bluetooth using the "add bluetooth or other device" assistant on windows.
It appears as "Connected" in the bluetooth device list. Moolticute detects it.
After some time, it appears just as "Paired". Moolticute ceases to detect it.
Trying to add it again does not work
If, in the bluetooth menu of the device, I click on the "Disable Bluetooth" button, Mooltipass freezes.

Moolticute Version - If Involved

v0.42.5-testing

Operating System

• Windows 10

Other operating systems are not supported.

Mooltipass Extension

Expected behavior

If you have to select between deny and accept a credential you can scroll down and up. It should stay at the selected deny field if you constantly scroll down. If you scroll up the 🡹 arrow should flash. If you scroll down the 🡻 arrow should flash.

Actual behavior

If you have to select between deny and accept a credential you can scroll down and up, If you keep scrolling down it switches between accept and deny. Even the animation is the wrong way around. If I scroll up the arrow 🡻 start flashing.

Step by step guide to reproduce the problem

1. enter your smartcard and type in your pin(Animation is fine)
2. go to the Login menu and press the scroll wheel.
3. select one website and press the scroll wheel.
4. if the prompt ask if you want to login with the account scroll down.
5. the upper arrow starts flashing but you scroll down

Firmware Version

AUX MCU version: 0.13
Main MCU version: 0.18

Operating System

• Windows 10 Enterprise 2016 LTSB

Expected behavior

If I connect my Mooltipass Mini BLE with USB it should show the same Battery value like before when I disconnect it again(5-10 seconds).

Actual behavior

If I reboot my Mooltipass it shows three Battery bars. The Mooltipass is not connected with Bluetooth or USB. After I plug the USB cable into my Mooltipass it starts charging. When I disconnect my Mooltipass again it only shows one Battery bar.

Step by step guide to reproduce the problem

1. Use your Mooltipass a whole day only with USB.
2. Disconnect the Mooltipass after 8 hours and leave it for 15 hours inside your backpack.
3. Insert your smartcard and look at the Battery bars. It should have 4 to 3 bars.
4. Connect your Mooltipass with USB to the PC(USB-Ports on the back side of the PC).
5. The Mooltipass start charging.
6. Disconnect the Mooltipass after 5-10 seconds.
7. The Mooltipass now shows only 1 Battery bar for me. If I leave it for multiple minutes it shows more and more Battery bars until it is charged. It is fully charged after about 5 minutes.

Moolticute Version - If Involved

v0.42.26-testing

Firmware Version

AUX MCU version: 0.11
Main MCU version: 0.16

Operating System

Windows 10 Enterprise 2016 LTSB

Expected behavior

Once Mooltipass BLE battery is full, the charging animation should show a full battery so the user knows that battery is fully charged.

Actual behavior

The battery animation shows charging as long as the device is connected.

Step by step guide to reproduce the problem

Connect your Mooltipass BLE to a computer.

Moolticute Version

N/A

Operating System

N/A

Mooltipass Device

• The Mooltipass Mini BLE

Missing feature

Feature to automatically lock the BLE device whenever it disconnects from a computer or host.
Maybe even an optional timeout.

Justification

It would be easier for the user, by not having to manually lock the device every time its unplugged or disconnected.

Expected behavior

"Going to Sleep" animation should be interrupted by input from scroll wheel, not allowing the device to sleep.

Actual behavior

The device ignores any input from the scroll wheel while animation plays. Only after the animation ends, input wakes it up.

Step by step guide to reproduce the problem

Use the Mooltipass to wake its screen.
Hold it, don't touch the scroll wheel until the "Going to sleep" animation comes up.
While animation plays, use the scroll wheel (turn it / click it).

Moolticute Version

v0.42.20-testing

Operating System

• MacOS

Mooltipass Device

• The Mooltipass Mini BLE

Expected behavior

If the device has been paired to a computer, it should automatically reconnect.

Actual behavior

The device does nor reconnect especially when it has been disconnected for a long time. This does not to happens when the device is reconnected only a few minutes after being disconnected

Step by step guide to reproduce the problem

1. Pair the device
2. Disconnect the device by disabling Bluetooth on the device or computer
3. Later, enable the Bluetooth again
4. The device is not connected it only show the bluetooth is enabled. On the computer it is shown as paired, but not connected

Moolticute Version

• 0.42.14-testing

Operating System

• Windows 10

only on main solution

1. if it makes sense, not use a hmac based prng anymore... create our own one to pass to the ecc functions

• hopefully it should be as simple as tweaking hmac_drbg.c :)

2. check for buffer overflows for ecc related functions:

• for example br_ec_keygen returns the size written into the private key buffer, we should check it with the size of our buffer and while() in case of errors

3. use logic_encryption_delete_context function to do house cleaning

4. removed unused functions:

void logic_encryption_sha256_hmac_init(uint8_t const *key, uint32_t klen);
void logic_encryption_sha256_hmac_update(uint8_t const * data, size_t len);
void logic_encryption_sha256_hmac_final(uint8_t *hmac_out);

void logic_encryption_sha512_init(void);
void logic_encryption_sha512_update(uint8_t const * data, size_t len);
void logic_encryption_sha512_final(uint8_t *hash);

5. answer remaining comments of FIDO2 merge, especially regarding logic_encryption_ecc256_derive_public_key()

when outputting over usb, text encoding is incorrect for the USA (MacOS) layout on a mac. I've validated that the keyboard layout for usb reads USA (MacOS) from both Moolticute and the device's settings menu.

Expected behavior

username abcdefg1234567890 and password 1!aAqQpP4$'" would output as

abcdefg1234567890	1!aAqQpP4$'"

Actual behavior

username abcdefg1234567890 and password 1!aAqQpP4$'" outputs as

]^_` abc-./012345,	-8˝]=mMlL0 #

Step by step guide to reproduce the problem

• Set keyboard layout to USA (MacOS)
• Add any credential
• Send credential out over USB

Moolticute Version

0.42.20

Operating System

macos 10.14

Firmware Versions

Aux: 0.10
Main: 0.10

Missing feature

Having the ability to put credentials in categories and show credentials of a specific category is nice. It would be even better to have a category "All categories" that would display all credential without any filter

Justification

Sometime it is quite annoying having to change categories every time.

Workarounds

Need to select the correct category

Expected behavior

When I try to enter in Credential Management Mode and finally cancel,
Moolticute should come back on the Credential Management Mode screen

Actual behavior

Stay stuck on "Unlock Your Mooltipass Device" screen, even if the Mooltipass is unlocked

Step by step guide to reproduce the problem

1. Enter the Credential Management Mode in Moolticute
2. Confirm the "manage database"
3. Cancel (long press on the wheel) when code Pin is asked
4. Moolticute stay on the screen "Unlock Your Mooltipass Device"

Notes :

• I noticed the same behaviour when no PIN is entered and the Mooltipass BLE go to sleep mode
• This does not occur with Mooltipass Mini

Moolticute Version

v0.42.6-testing

Operating System

• Windows 10

Expected behavior

If you disconnect your Mooltipass during configuration inside category, bluetooth, login menu the display should not turn black. It should stay inside the selected menu until you select something.

Actual behavior

If you disconnect your Mooltipass during configuration inside category, bluetooth, login menu the display turn black but your still able to select a option without knowing it(black screen). If you do it the other way it works like it should(running with battery and connecting it to usb).

Step by step guide to reproduce the problem

1. connect your Mooltipass with a USB-C cable
2. enter your smartcard and the pin code
3. select the "Set Active Category" menu and make sure your current selected category is "All Categories"
4. disconnect the mooltipass
5. you will see a black screen which won't wake up if you scroll. Scroll a bit and press the scroll button.
6. After that you see the main menu again
7. enter the "Set Active Category" menu again.
8. now a different category is your current category now.

Firmware Version

AUX MCU version: 0.13
Main MCU version: 0.18

Operating System

• Windows 10 Enterprise 2016 LTSB

Expected behavior

The icon for the currently selected menu item in the Bluetooth menu should be more or less centered over its labeling text.

Actual behavior

Unlike the other menus, the icon for the currently selected menu item is shifted to the right in the Bluetooth menu, making it less than clear which menu item is the current one.

Step by step guide to reproduce the problem

1. Unlock the minible by inserting the card and entering the PIN.
2. Navigate to the "Enable Advanced Menu" menu item in the Operations menu.
3. Observe that the icon is centered over the text under it.
4. Navigate to "Pair New Device" item in the Bluetooth menu.
5. Observe that the currently selected icon (the B+ item) is well to the right of the text under it.

Moolticute Version - If Involved

N/A

Operating System

• Windows 7

Other operating systems are not supported.

Mooltipass Extension

N/A

on webauthn.me, simply register a new credential then follow the process to get authenticated: you'll get 2 prompts on the device

Missing feature

Lock the Mooltipass Mini BLE during PC shutdown

Justification

If I'm in a rush it happens that I forget to pull out the smartcard. But I always shutdown my PC.

Workarounds

Don't forget to pull out the smartcard.

I apologize in advance @0x0ptr ....

It just occurred to me that it doesn't make sense adding the call to main_init_stack_tracking in both bootloaders, as we can't update the bootloaders of the currently deployed units (and the ones currently being produced...).

If I'm not mistaken, we should therefore:

• remove all stack tracking code from bootloaders
• move the main_init_stack_tracking call in the main/aux solutions from jump_to_application_function to the first line after the main()

Due to the time the call to main_init_stack_tracking may take it may be worth moving out platform_io_enable_switch() call from main_platform_init() to before the call to main_init_stack_tracking on the main solution

is it an issue if we corrupt the stack if we're never returning to jump_to_application_function() ?

When creating a new user, the "PIN :" in the second line of "Input New Card PIN :" isn't aligned to the right

8<------------------------ FEATURE REQUEST ------------------------------------

Missing feature

Animations on the new MBLE are neat, but slow: entering a PIN takes considerably longer than on the Mooltipass Mini, thanks to the smooth scrolling between digits and the four entries - where the Mooltipass Mini just jumps between each instantly.

Justification

Slow is bad; fast is good.

Workarounds

I have no workarounds, but being able to set the speed of the animation would be nice; alternatively, a simple "animations off" toggle would work. (I'm aware of the boot/prompt animation toggles, but they don't affect the PIN input.)

8<------------------------ END FEATURE REQUEST --------------------------------

Use one of the two templates below and delete the other. All issues not following this template will be directly closed.

8<------------------------ BUG REPORT -----------------------------------------

Expected behavior

"[email protected]" will be entered

Actual behavior

"ttt+uuu<´ki]ej+_ki" is entered

Step by step guide to reproduce the problem

• select tab Device Settings
• select "USB Keyboard Layout" German(MacOS)
• press "Save to device"
• enter field on MacBook Pro, where you want to insert the usernam (login)
• select Login on Mooltipass BLE
• confirm

Moolticute Version - If Involved

Operating System

Mention if you are using either:

• Windows 7/10
• Debian Based distribution
• Other Linux distribution
• MacOS

Other operating systems are not supported.

Mooltipass Extension

• If you're creating an issue to report a website incompatibility, please use the "Report incompatibilities with this website" item in the extension menu.
• If you're creating an issue to report a problem with our extension, please create another issue here:
  https://github.com/mooltipass/extension/issues

8<------------------------ END BUG REPORT -------------------------------------

Use one of the two templates below and delete the other. All issues not following this template will be directly closed.

8<------------------------ BUG REPORT -----------------------------------------
Under Catalina (OS X) bluetooth pairing with a known device.
Activate bluetooth under OS X, Catalina; activate bluetooth on Mooltipass BLE.

Expected behavior

See a stable connection between Mooltipass and MacBook Pro.

Actual behavior

Connection is instable. Only after removing the device in OS X and adding it again the connection is stable.

Step by step guide to reproduce the problem

• activate bluetooth under OS X
• activate bluetooth on Mooltipass
• remove the device under OS X
• add the device under OS X again

Moolticute Version - If Involved

0.42.9

Operating System

MacBook Pro, Model 2017, MacOS Catalina latest stable (10.15.1)
8<------------------------ END BUG REPORT -------------------------------------

Expected behavior

The encoder should follow the rotation precisely even at higher rotation speeds.

Actual behavior

Skips steps and even misses the direction when the encoder rotates too fast.

Step by step guide to reproduce the problem

Just rotate the encoder fast enough on any menu screen or pin input.

(Might be problem with the input encoder software debouncing algorithm)

Expected behavior

Settings like "Credential Display Prompt?", "Prompt When Login In?", etc. should display current active value and not preselect the "Enabled" state.

Actual behavior

The mentioned options always show the state "Enabled", even if the option is actually disabled

Step by step guide to reproduce the problem

1. Enter in one of the settings
2. Disable the setting
3. Enter the same setting again
4. "Enabled" is selected

Regards,

Julien

Missing feature

Knock detection on websites with multiple accounts

Justification

There is no knock detection on website where I have multiple accounts. I have to use the scroll wheel to accept the credentials. The feature should include that you are able to switch between the accounts with a knock and you can accept the credentials for the selected account with fast tapping for 2-3 seconds.

Workarounds

Use the scroll wheel to select the right account.

Expected behavior

I connected my Mooltipass BLE mini with Bluetooth and used it for 10-20 minutes. After that I pulled out the card and left the device on my table for 2-3 hours. The Mooltipass BLE mini should wake up when I insert my smartcard, press the scroll wheel or if I use the USB-C kabel.

Actual behavior

The Mooltipass BLE mini wasn't responding anymore. Only after pressing the scroll wheel for a long time I saw the boot animation. After it was responsive again I saw that the battery was fully charged

Step by step guide to reproduce the problem

I couldn't reproduce the problem yet. But these steps might caused the problem.

• charge the mooltipass to 100%
• unplug the mooltipass and connect it with a other computer(Bluetooth)
• Pair the Mooltipass with your PC(Bluetooth)
• use it for a while
• shutdown your PC
• unplug the smartcard and leave the mooltipass on the table for 2-3 hours
• try to wake it up

Moolticute Version - If Involved

v0.42.14-testing

Operating System

Windows 10 18362

Mooltipass firmware version

Aux MCU 0.9
Main MCU 0.9

8<------------------------ BUG REPORT -----------------------------------------

Expected behavior

"[email protected]" will be entered

Actual behavior

"xxx.yyy«domain.com" is entered

Step by step guide to reproduce the problem

• select tab Device Settings
• select "USB Keyboard Layout" Germany
• press "Save to device"
• enter field on MacBook Pro, where you want to insert the usernam (login)
• select Login on Mooltipass BLE
• confirm

Moolticute Version - If Involved

Operating System

MacBook Pro, Model 2017, MacOS Catalina (10.15.1)
Mention if you are using either:

• Windows 7/10
• Debian Based distribution
• Other Linux distribution
• MacOS

Other operating systems are not supported.

Mooltipass Extension

• If you're creating an issue to report a website incompatibility, please use the "Report incompatibilities with this website" item in the extension menu.
• If you're creating an issue to report a problem with our extension, please create another issue here:
  https://github.com/mooltipass/extension/issues

8<------------------------ END BUG REPORT -------------------------------------

Expected behavior

Mooltipass Mini BLE shouldn't crash after it wants that I confirm the credentials for a specific website(gitlab.northernroot.net).

Actual behavior

The Mooltipass Mini BLE crashes after visiting a specific website(gitlab.northernroot.net).

Step by step guide to reproduce the problem

First I connected the Mooltipass with USB. After that I changed the Keyboard Layout with Moolticute to Germany and saved the settings(no card inserted). Then I inserted my key card into the Mooltipass and confirmed the pin. After the pin was accepted I went to the Bluetooth settings menu. I checked if bluetooth was enabled or not. Bluetooth wasn't enabled. I visited my cloud and confirmed the credentials. The Mooltipass inserted the credentials and I was logged in. After that I visited my gitlab website. The Mooltipass wanted that I confirm the credentials again but it allready crashed at this time.

I tried a forced shutdown but it didn't helped.
https://www.youtube.com/watch?v=g-_SaJcDPT8

After I stopped recording I pulled out the USB cable again and plugged it back in. The Mooltipass displayed the message: No Aux MCU
Windows notified me that the connected device wasn't reconised. I pressed the scroll wheel again for 15 seconds and the message disappeared. After that the Mooltipass started again.

Moolticute Version

v0.42.23-testing

Mooltipass firmware

Aux MCU version: 0.10
Main MCU version: 0.11 (customized for: Card Failing! message)

Operating System

Windows 10 Pro 18362

Moolticute Logfile

mooltipass crash.txt

Expected behavior

A different message

Actual behavior

"PINs do not match" message

Step by step guide to reproduce the problem

Insert blank card, accept new user prompt, then long press to go back

Use one of the two templates below and delete the other. All issues not following this template will be directly closed.

8<------------------------ BUG REPORT -----------------------------------------

Expected behavior

Insert username, password at the desired position.

Actual behavior

nothing inserted at the desired position.

Step by step guide to reproduce the problem

• Connect Mooltipass BLE and MacBook Pro with a USB cable
• Connect Mooltipass BLE and MacBook Pro with bluetooth

Moolticute Version - If Involved

0.42.9

Operating System

MacBook Pro Model 2017, MacOS Catalina (10.15.1)
Mention if you are using either:

• Windows 7/10
• Debian Based distribution
• Other Linux distribution
• MacOS

Other operating systems are not supported.

Mooltipass Extension

• If you're creating an issue to report a website incompatibility, please use the "Report incompatibilities with this website" item in the extension menu.
• If you're creating an issue to report a problem with our extension, please create another issue here:
  https://github.com/mooltipass/extension/issues

8<------------------------ END BUG REPORT -------------------------------------

Expected behavior

I expect the device no to randomly ask me to please remove the card.

Actual behavior

When I connect the device to the computer, sometimes asks me to remove the card. If I forget to input the pin, eventually asks me to remove the card.

Step by step guide to reproduce the problem

Turn Off mooltipass.
Turn On mooltipass.
Connect to computer. (Sometimes, here it asks to remove the card)
Do not input pin. Wait some minutes.
There you go. "Please remove the card"

Moolticute Version - If Involved

v0.42.5-testing

Operating System

• Windows 10

Mooltipass Extension

When the mooltipass is connected via bluetooth [with and without the USB cable also connected], it doesn't output any text. After sending the password, the mooltipass's screen does "pause" like normal as if it's busy sending the data, but nothing gets typed.

Expected behavior

Credentials are outputted on screen

Actual behavior

No output appears

Step by step guide to reproduce the problem

• pair mooltipass via bluetooth
• attempt to send credentials

Moolticute Version - If Involved

0.42.20

Operating System

macos 10.14

Firmware Versions

Aux: 0.10
Main: 0.10

Expected behavior

The given credential is discarded.

Actual behavior

The credential is saved with invalid password.

Step by step guide to reproduce the problem

1. Enable MMM Store Confirmation prompt on the device
2. Add a new Credential from MMM
3. Click on Save all changes button
4. When update prompt is displayed on device discard it or wait for the timeout
5. Check the saved credential

Moolticute Version

v0.42.27-testing

Operating System

• Windows 10