Lines Matching refs:authentication

29 can be used to get full data authentication at the block layer.
33 authentication for UBIFS. Since UBIFS uses fscrypt for file contents and file
34 name encryption, the authentication system could be tied into fscrypt such that
36 be possible to use UBIFS authentication without using encryption.
205 This chapter introduces UBIFS authentication which enables UBIFS to verify
212 UBIFS authentication enables detection of offline data modification. While it
217 UBIFS authentication will not protect against rollback of full flash contents.
231 UBIFS authentication does not cover attacks where an attacker is able to
232 execute code on the device after the authentication key was provided.
323 it is necessary to also add authentication information frequently to the
327 nodes. From time to time whenever it is suitable authentication nodes are added
330 authentication node. The tail of the journal which may not have a authentication
333 We get this picture for journal authentication::
384 For simplicity, UBIFS authentication uses a single key to compute the HMACs
390 UBIFS authentication is intended to operate side-by-side with UBIFS encryption
394 UBIFS authentication on the other hand has an all-or-nothing approach in the
396 Because of this and because UBIFS authentication should also be usable without
398 a dedicated authentication key.
400 The API for providing the authentication key has yet to be defined, but the
407 or key in userspace that covers UBIFS authentication and encryption. This can
409 authentication in addition to the derived fscrypt master key used for
413 superblock node will additionally store a hash of the authentication key. This
423 UBIFS authentication key. Instead, in addition the each HMAC a digital