Skip to content
Snippets Groups Projects
  1. Apr 14, 2020
    • Denis Pynkin's avatar
      Add manual test of SabreLite secure boot · df2a0fcc
      Denis Pynkin authored
      This test ensures:
      - U-Boot is compiled with HAB and FIT support
      - SRK hash is fused and U-Boot is signed ('hab_status' call)
      - U-Boot is able to verify signed OS image in FIT format
      - U-Boot hangs in case if we try to boot with unsigned binary
      
      Unfortunately the DUT in "open" mode assume any signature as valid,
      hence it is not possible to check the boot hang for FIT image signed
      with incorrect key -- the HW return 'success' while checking signature.
      
      If the system is in 'closed' state then it is able to use incorrect
      signature for the image, for example taken from document
      "High Assurance Boot (HAB) for dummies" by Boundary Devises:
      https://boundarydevices.com/high-assurance-boot-hab-dummies/
      
      
      
      To check if the system is in "closed" state:
        => fuse read 0 6
           Reading bank 0:
      
           Word 0x00000006: 00000012
      
      the last digit must be "2".
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      df2a0fcc
  2. Apr 11, 2020
  3. Apr 09, 2020
  4. Apr 01, 2020
  5. Mar 31, 2020
  6. Mar 26, 2020
  7. Mar 25, 2020
  8. Mar 24, 2020
  9. Mar 13, 2020
  10. Mar 12, 2020
  11. Feb 13, 2020
  12. Feb 10, 2020
  13. Jan 31, 2020
  14. Jan 30, 2020
  15. Jan 21, 2020
  16. Dec 20, 2019
  17. Dec 06, 2019
  18. Dec 04, 2019
  19. Nov 28, 2019
  20. Nov 27, 2019
  21. Nov 15, 2019
  22. Oct 25, 2019
  23. Oct 23, 2019
  24. Sep 26, 2019
    • Denis Pynkin's avatar
      AUM OTA manual: copy hint with time settings for all tests · 6023dfd3
      Denis Pynkin authored
      Use timedatectl to workaround NTP issues on some networks
      
      With battery backed devices on networks with no properly reachable NTP servers
      the boards would fail to automatically get the right time, so testers set it up
      manually with `date`.
      
      However, the hardware clock need to be configured as well for the time
      configuration to survive a reboot, needed by the Apertis update manager OTA
      test.
      
      Without this, the device will fail to establish any TLS connection after the
      reboot since every certificate will look like they are out of their validity
      period.
      
      This is only a workaround until we ensure NTP servers are reachable on the
      testers' network, see https://phabricator.apertis.org/T6115
      
      
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      6023dfd3
    • Denis Pynkin's avatar
      Enable AUM automatic tests for all architectures · 96227328
      Denis Pynkin authored
      
      Need to test the upgrade behavior on different architectures.
      Enabled automatic tests of ostree and upgrade manager behavior for all
      supported minimal images.
      
      Not enabled rollback test for Arm64 and Amd64 yet since they have no
      enabled bootcounter mechanism in bootloader.
      
      Signed-off-by: default avatarDenis Pynkin <denis.pynkin@collabora.com>
      96227328
  25. Sep 23, 2019
  26. Sep 20, 2019
  27. Sep 18, 2019
    • Emanuele Aina's avatar
      gettext: Accept `pass`/`fail` as results · 2328be64
      Emanuele Aina authored and Luis Araujo's avatar Luis Araujo committed
      The test is currently emitting results in this way:
      
          Testing supported locales:
          ar_QA.utf8: fail
          ar_SA.utf8: fail
          cs_CZ.utf8: fail
          da_DK.utf8: fail
          de_DE.utf8: fail
          el_GR.utf8: fail
          en_GB.utf8: fail
          en_US.utf8: fail
          es_AR.utf8: fail
          es_ES.utf8: fail
          es_MX.utf8: fail
          fi_FI.utf8: fail
          fr_CA.utf8: fail
          fr_FR.utf8: fail
          hu_HU.utf8: fail
          id_ID.utf8: fail
          it_IT.utf8: fail
          ms_MY.utf8: fail
          nb_NO.utf8: fail
          nl_NL.utf8: fail
          pl_PL.utf8: fail
          pt_BR.utf8: fail
          pt_PT.utf8: fail
          ro_RO.utf8: fail
          ru_RU.utf8: fail
          sk_SK.utf8: fail
          sv_SE.utf8: fail
          th_TH.utf8: fail
          tr_TR.utf8: fail
          zh_CN.utf8: fail
          zh_HK.utf8: fail
          31 test(s) failed
      
      See https://lava.collabora.co.uk/scheduler/job/1827695#L5089
      
      
      
      However, the current regex only matched uppercase characters,
      expecting `PASSED`/`FAILED`.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      2328be64
  28. Sep 16, 2019
  29. Sep 12, 2019
  30. Sep 10, 2019
    • Emanuele Aina's avatar
      Drop the audit.log reset steps · 86d41860
      Emanuele Aina authored
      
      Most tests have been converted to use the system journal to check for audit
      events, so there's no need to reset the audit.log anymore.
      
      Resetting it is even harmful today since `auditd` is no longer shipped by
      default on images, thus the step fails as the file and the directory that
      should contain it do not exist.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      86d41860
  31. Sep 09, 2019
Loading