1. 06 May, 2024 1 commit
  2. 05 May, 2024 2 commits
  3. 03 May, 2024 7 commits
  4. 02 May, 2024 2 commits
  5. 01 May, 2024 2 commits
  6. 30 Apr, 2024 11 commits
  7. 29 Apr, 2024 10 commits
  8. 26 Apr, 2024 5 commits
    • Cedric Roux's avatar
      define stream_security_context_t as a struct to get type checking · 39a5e728
      Cedric Roux authored
      By using a struct we may have warnings at compilation time in some
      cases if the type is not used properly.
      
      The type definition becomes a bit weird, so we need to properly
      comment.
      
      If too strange, we can revert to the classical "void" definition.
      39a5e728
    • Cedric Roux's avatar
    • Cedric Roux's avatar
      minor cleanup - use variable defined above · fac5c1f6
      Cedric Roux authored
      fac5c1f6
    • Cedric Roux's avatar
      cleanup the structure cbc_cmac_ctx_t · 61a2c085
      Cedric Roux authored
      - rename "lib_ctx" to "mac_implementation" which is what is stored because
        of previous commit
      - rename "mac" to "mac_context" to be clearer with what is stored in this
        variable too
      61a2c085
    • Cedric Roux's avatar
      bugfix: speedup integrity computation · d7931ea4
      Cedric Roux authored
      The main work of this commit is to rewrite cipher_aes_128_cbc_cmac()
      which was too slow and created issues when running the 4G eNB on some
      machines (LLL when using a b210).
      
      Instead of creating the security context, use it, and delete it, all in
      cipher_aes_128_cbc_cmac(), we introduce the function init_aes_128_cbc_cmac()
      to create it, and we change cipher_aes_128_cbc_cmac() to just use it,
      and we also adapt free_aes_128_cbc_cmac(). The function aes_128_cbc_cmac()
      is removed, it does not follow the new init/use/free API.
      
      Doing so, on the primary test machine used to do this work (a powerful
      and fast machine where it is possible to set the CPUs' frequencies)
      it was possible to limit the CPUs' frequencies to 500 MHz (it was not
      possible to go lower) without any LLL (using a b210, quectel UE in
      idle, no data traffic, only periodic measurement reports). Before this
      commit, it was necessary to set a frequency of at least 1.8 GHz
      otherwise some LLL would appear.
      
      Then we need to adapt the rest of the code to take into account those
      changes.
      
      A notion of security container (stream_security_container_t) containing
      ciphering and integrity contexts is introduced.
      
      And the code is harmonized for, hopefully, better readability.
      
      The (opaque) type stream_security_context_t is introduced, used by
      both integrity and ciphering contexts. The idea is to use a
      init()/use()/free() API for all the security procedures, identical for
      all the ciphering and integrity procedures.
      d7931ea4