| Commit message (Collapse) | Author | Age | 
| |  | 
 | 
| |  | 
 | 
| | 
| 
| 
|  | 
Signed-off-by: Szczepan Zalega <szczepan@nitrokey.com>
 | 
| | 
| 
| 
|  | 
Signed-off-by: Szczepan Zalega <szczepan@nitrokey.com>
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |\  
| | 
| | 
| |  | 
CI: correct Meson builds
 | 
| | |  | 
 | 
| |/   | 
 | 
| |\  
| | 
| | 
| | 
| | 
| | 
| |  | 
Update Meson build script
Add CI job to test build
Fixes #165
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |\  
| |/  
|/|   
| |    | 
Update to latest
 | 
| |\ \  
| | | 
| | | 
| | | 
| | | 
| | |  | 
Add NK_config struct and read/write functions
Fixes #176
 | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | |  | 
This patch adds the NK_config struct to the C API that stores the
general configuration of a Nitrokey device.  It also adds the
NK_read_config_struct and NK_write_config_struct functions to make the
API easier to use.  While NK_write_config_struct is only a convenience
method, NK_read_config_struct makes the API more safe as the user no
longer has to read the data from a pointer to an array.
This patch also extends the test_read_write_config test case with the
two new functions.
 | 
| |\ \ \  
| | | | 
| | | | 
| | | | 
| | | | 
| | | |  | 
Add functions for freeing memory of some C API results
Fixes #175
 | 
| | | | | 
| | | | 
| | | | 
| | | | 
| | | | 
| | | | 
| | | | 
| | | |  | 
This patch adds two missing free functions, NK_free_config and
NK_free_password_safe_slot_status, to enable memory-safe use of the C
API.
Fixes #173.
 | 
| | |/ /  
| | |   
| | |   
| | |   
| | |   
| | |    | 
This patch adds a test_memory test case that demonstrates new[]/free
mismatches with the NK_read_config and NK_get_password_safe_slot_status
functions if run with valgrind, see #173.
 | 
| |\ \ \  
| | | | 
| | | | 
| | | | 
| | | | 
| | | |  | 
Check for null pointer in the provided data
Fixes #168
 | 
| | | | |  | 
 | 
| | | | | 
| | | | 
| | | | 
| | | | 
| | | | 
| | | |  | 
While the fields of the hid_device_info struct should not be null, it is
better to perform an explicit check before trying to construct strings
from them.
 | 
| |\ \ \ \  
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | |  | 
Return serial number as uint32_t
Fixes #174
 | 
| | | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | |  | 
This patch adds the function NK_device_serial_number_as_u32 to the C
API.  It is similar to NK_device_serial_number but returns the raw
unsigned integer instead of a formatted string.  This patch also adds a
simple test case that ensures that the number is not zero.
Fixes #172.
 | 
| | | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | |  | 
To avoid duplicate code, this patch refactors the get_serial_number
method to use get_serial_number_as_u32 internally.  It does not change
get_serial_number’s behavior.
 | 
| | | |/ /  
| |/| |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |    | 
This patch adds the get_serial_number_as_u32 method to NitrokeyManager.
It returns the serial number as a 32-bit unsigned integer.  Previously,
we only returned it as a string generated from the integer value,
get_serial_number.
While get_serial_number returns an empty string if no device is
connected and "NA" if an unknown model is connected, the new method
throws a DeviceNotConnected exception in the first case and returns zero
in the second case as we cannot express the three states in one integer
return value.
 | 
| |\ \ \ \  
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | |  | 
Update CI settings
Add new compilers and use Ubuntu 18.04
 | 
| | | | | |  | 
 | 
| | | | | |  | 
 | 
| |/ / / /   | 
 | 
| |\ \ \ \  
| | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | |  | 
Support Librem Key
Fixes #163
 | 
| | | | | | 
| | | | | 
| | | | | 
| | | | | 
| | | | |  | 
Remove the change to keep binary compatibility.
Use the vendor_id field from the dev description.
 | 
| | | | | |  | 
 | 
| |\ \ \ \ \  
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | | 
| | | | | |  | 
Correct Python 2 and 3 examples
Fixes #178
 | 
| | | | | | | 
| | | | | | 
| | | | | | 
| | | | | |  | 
Signed-off-by: Sven Ebenfeld <sven.ebenfeld@gmail.com>
 | 
| |/ / / / /  
| | | | |   
| | | | |   
| | | | |    | 
Signed-off-by: Sven Ebenfeld <sven.ebenfeld@gmail.com>
 | 
| | |/ / /  
|/| | |    | 
 | 
| |\ \ \ \  
| |_|/ /  
|/| | |   
| | | |   
| | | |   
| | | |   
| | | |   
| | | |    | 
Add tests for the Nitrokey Pro bootloader support.
Allow to reconnect to the device during the test execution
(e.g. for a reinsertion).
Connected: https://github.com/Nitrokey/nitrokey-pro-firmware/issues/69
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| | | | |  | 
 | 
| |/ / /   | 
 |