bugfix hid cancel

Makefile

@@ -103,7 +103,6 @@ uncached-docker-build-toolchain:
 docker-build-all: 
 	docker run --rm -v "$(CURDIR)/builds:/builds" \
 					-v "$(CURDIR):/solo" \
-					-u $(shell id -u ${USER}):$(shell id -g ${USER}) \
 				    $(DOCKER_TOOLCHAIN_IMAGE) "solo/in-docker-build.sh" ${SOLO_VERSION_FULL}
 
 CPPCHECK_FLAGS=--quiet --error-exitcode=2

STABLE_VERSION

@@ -1 +1 @@
-3.0.1
+3.0.0

docs/solo/application-ideas.md

@@ -1,23 +1,16 @@
 # Using Solo for passwordless or second factor login on Linux 
 
-## Setup on Ubuntu and Manjaro
+## Setup on Ubuntu 18.04
 Before you can use Solo for passwordless or second factor login in your Linux system you have to install some packages.
 
-This was tested on **Linux Mint 19.3** and on **Manjaro 18.x**
+This was tested under **Linux Mint 19.2**.
 
 First you have to install PAM modules for u2f.
 
-**Ubuntu (Linux Mint):**
 ```
   sudo apt install libpam-u2f pamu2fcfg
 ```
 
-**Manjaro**
-```
-  pacman -Syu pam-u2f
-```
-
-
 ## Setting up key
 To use Solo as passwordless or second factor login, you have to setup your system with your Solo.
 First create a new folder named **Yubico** in your **.config** folder in your **home** directory
@@ -35,30 +28,25 @@ If you want to register an additional key use this command instead:
   pamu2fcfg >> ~/.config/Yubico/u2f_keys
 ```
 Now press the button on your Solo.
-<br>
-<br>
  
-If you can't generate your key on **Ubuntu** (error message), you may add Yubico Team from PPA and install latest libpam-u2f and pamu2fcfg and try again.
+
+If you can't generate your key (error message), you may add Yubico Team from PPA and install latest libpam-u2f and pamu2fcfg and try again.
 ```
   sudo add-apt-repository ppa:yubico/stable
   sudo apt-get update
   sudo apt-get upgrade
 ```
 
-**Manjaro** should work without problems.
-
 
 ## Login into Linux
 ### Passwordless
 To login passwordless into your Linux system, you have to edit the file **lightdm** (or **gdm** or which display manager you prefered).
-In case of lightdm and VIM as editor:
+In case of lightdm:
 
 ```
 sudo vim /etc/pam.d/lightdm
 ```
-
-**On Ubuntu:**<br>
-Search following entry:
+Now search following entry:
 ```
 @include common-auth
 ```
@@ -66,26 +54,9 @@ and add
 ```
 auth    sufficient      pam_u2f.so
 ```
-**before** *@include common-auth.*
-<br>
-<br>
+**before** @include common-auth.
 
-**On Manjaro**<br>
-Search following enrty
-```
-  auth    include   system-login
-```
-
-and add
-```
-  auth    sufficient    pam_u2f.so
-```
-
-** before** *auth include system-login*.
-<br>
-<br>
-
-Now save the file and test it.<br>
+Save the file and test it.<br>
 Insert Solo in your USB port and logout.
 Now you should be able to login into Linux without password, only with pressing your button on Solo and press enter.
 
@@ -94,7 +65,7 @@ Why **sufficient**? The difference between the keyword sufficient and required i
 
 The login mechanism can be also used for additional features like:
 
-  - Login after screen timeout - edit /etc/pam.d/mate-screensaver (or kde-screensaver, ...)
+:  - Login after screen timeout - edit /etc/pam.d/mate-screensaver (or kde-screensaver, ...)
   - Passwordless sudo - edit /etc/pam.d/sudo
 
 Check out your folder **/etc/pam.d/** and do some experiments.
@@ -109,9 +80,7 @@ To use Solo as second factor, for login into your Linux system, is nearly the sa
 ```
 sudo vim /etc/pam.d/lightdm
 ```
-
-**On Ubuntu**<br>
-Search following entry:
+Now search following entry:
 ```
 @include common-auth
 ```
@@ -119,24 +88,7 @@ and add
 ```
 auth    required      pam_u2f.so
 ```
-**after** *@include common-auth*.
-<br>
-<br>
-
-**On Manjaro**<br>
-Search following entry:
-```
-  auth   include    system-login
-```
-
-Add following entry
-```
-  auth    required    pam_u2f.so
-```
-
-**after** *auth include system-login*.
-<br>
-<br>
+**after** @include common-auth.
 
 Save the file and test it. <br>
 In case your Solo is not present, your password will be incrorrect. If Solo is plugged into your USB port, it will signal pressing the button and you will be able to login into Linux.

docs/solo/programming.md

@@ -36,13 +36,9 @@ So it's important to not mess this up or you may brick your device.
 You can use a firmware build from the [latest release](https://github.com/solokeys/solo/releases) or use
 a build that you made yourself.
 
-You need to use a firmware file that has the combined bootloader, application, and attestation key pair (bootloader + firmware + key).
-This means using the `bundle-*.hex` file or the `bundle.hex` from your build.  
-
-#### *Warning*
-
-* **If you overwrite the Solo flash with a missing bootloader, it will be bricked**.  
-* **If you program bootloader and firmware with no attestation, you will run into FIDO registration issues**
+You need to use a firmware file that has the combined bootloader and application (or at the very least just the bootloader).
+This means using the `bundle-*.hex` file or the `bundle.hex` from your build.  If you overwrite the Solo flash with a missing bootloader,
+it will be bricked.
 
 We provide two types of bundled builds.  The `bundle-hacker-*.hex` build is the hacker build.  If you update with this,
 you will update the bootloader and application, but nothing will be secured.  The `bundle-secure-non-solokeys.hex`

targets/stm32l432/bootloader/bootloader.c

@@ -50,15 +50,12 @@ typedef struct {
     uint8_t payload[255 - 10];
 } __attribute__((packed)) BootloaderReq;
 
-uint8_t * last_written_app_address;
-
 /**
  * Erase all application pages. **APPLICATION_END_PAGE excluded**.
  */
 static void erase_application()
 {
     int page;
-    last_written_app_address = (uint8_t*) APPLICATION_START_ADDR;
     for(page = APPLICATION_START_PAGE; page < APPLICATION_END_PAGE; page++)
     {
         flash_erase_page(page);
@@ -109,6 +106,7 @@ int is_bootloader_disabled()
     uint32_t * auth = (uint32_t *)(AUTH_WORD_ADDR+4);
     return *auth == 0;
 }
+uint8_t * last_written_app_address;
 
 #include "version.h"
 bool is_firmware_version_newer_or_equal()
@@ -118,7 +116,7 @@ bool is_firmware_version_newer_or_equal()
           current_firmware_version.major, current_firmware_version.minor, current_firmware_version.patch, current_firmware_version.reserved,
           current_firmware_version.major, current_firmware_version.minor, current_firmware_version.patch, current_firmware_version.reserved
           );
-  volatile version_t * new_version = ((volatile version_t *) (last_written_app_address-8+4));
+  volatile version_t * new_version = ((volatile version_t *) last_written_app_address);
   printf1(TAG_BOOT,"Uploaded firmware version: %u.%u.%u.%u (%02x.%02x.%02x.%02x)\r\n",
           new_version->major, new_version->minor, new_version->patch, new_version->reserved,
           new_version->major, new_version->minor, new_version->patch, new_version->reserved
@@ -172,7 +170,6 @@ int bootloader_bridge(int klen, uint8_t * keyh)
     uint32_t addr = ((*((uint32_t*)req->addr)) & 0xffffff) | 0x8000000;
 
     uint32_t * ptr = (uint32_t *)addr;
-    uint32_t current_address;
 
     switch(req->op){
         case BootWrite:
@@ -199,16 +196,9 @@ int bootloader_bridge(int klen, uint8_t * keyh)
                 printf2(TAG_ERR, "Error, boot check bypassed\n");
                 exit(1);
             }
-            current_address = addr + len;
-            if (current_address < (uint32_t) last_written_app_address) {
-                printf2(TAG_ERR, "Error, only ascending writes allowed.\n");
-                has_erased = 0;
-                return CTAP2_ERR_NOT_ALLOWED;
-            }
-            last_written_app_address = (uint8_t*) current_address;
-
             // Do the actual write
             flash_write((uint32_t)ptr,req->payload, len);
+            last_written_app_address = (uint8_t *)ptr + len - 8 + 4;
             break;
         case BootDone:
             // Writing to flash finished. Request code validation.

tools/requirements.txt

@@ -1,4 +1,5 @@
 ecdsa
+fido2==0.7.3
 intelhex
 pyserial
 solo-python