Common tasks

Authentication shortcuts

See also

All these methods and their documentation can be found in the Namespace desfire::fs.

Generic filesystem helpers

These methods check for existence and automate multiple-command tasks, such as creating an app with a specific key.

See also

All these methods and their documentation can be found in the Namespace desfire::fs.

Creating read-only applications

Read-only applications do not really exist in the Desfire world; there are read-only files. However, we can emulate this behavior by creating a randomized key which we can then throw away. This is thus split into two steps, desfire::fs::create_app_for_ro() (which creates an app with a randomized key, which is returned) and desfire::fs::make_app_ro() (which forbids any further file creation).

Note

If you keep the key, or create files that have desfire::free_access to desfire::file_access_rights::write, then of course those files will be writable.

See also

All these methods and their documentation can be found in the Namespace desfire::fs.

Creating read-only files

Read-only files might require multiple operations to be performed, as e.g. data files need to be created, then written to, and then sealed to not be writable anymore. These methods are shortcuts for this.

See also

All these methods and their documentation can be found in the Namespace desfire::fs.

Creating read-only, free-to-read files

Helper methods to desfire::fs::create_ro_data_file() and desfire::fs::create_ro_value_file() that always specify a desfire::free_access for desfire::file_access_rights::read, and desfire::file_security::none for desfire::common_file_settings::security.

See also

All these methods and their documentation can be found in the Namespace desfire::fs.