Project

General

Profile

Actions

Bug #12668

closed

Clear System OS Boot Log removes Cypto information on Status Page

Added by Jim Middleton over 3 years ago. Updated over 3 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Coreboot
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
arm64

Description

When I clear the System Log OS Boot and return to the System Status page Crypto information changes from "AES-NI CPU Crypto: Yes (active) to "AES-NI CPU Crypto: "No. The System Status field "Hardware crypto" changes from "AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS" to nothing, its blank.

If I boot the System Status Crypto information returns to as expected.


Files

PFSense.png (94.1 KB) PFSense.png Before OS Boot log cleared Jim Middleton, 01/08/2022 06:24 AM
PFSense1.png (132 KB) PFSense1.png After OS Boot log cleared Jim Middleton, 01/08/2022 06:24 AM
Actions #1

Updated by Viktor Gurov over 3 years ago

  • Status changed from New to Feedback

Please provide more information about your configuration -

unable to reproduce on 2.6.0.b.20220109.0600

fixed in #11428 and #11710

Actions #2

Updated by Jim Middleton over 3 years ago

Viktor Gurov wrote in #note-1:

Please provide more information about your configuration -

unable to reproduce on 2.6.0.b.20220109.0600

fixed in #11428 and #11710

Nothing fancy.

Dell Optiplex 390, i7-2600, 8gb ram, 120gb ssd. 3 Intel i225v NIC's. One is WAN. Two are bridged/Lan.

I stay current with beta.

Current Base System
2.6.0.b.20220109.0600
Latest Base System
2.6.0.b.20220109.0600
Status
Up to date.

Only plug-ins I have are NUT for my UPS and Speedtest.

Actions #3

Updated by Jim Middleton over 3 years ago

Local network with 3 users. Its not an office with a bazillion VLAN's, etc.

Actions #4

Updated by Jim Pingle over 3 years ago

  • Status changed from Feedback to Not a Bug
  • Assignee deleted (Renato Botelho)
  • Target version deleted (2.6.0)

This is normal and expected. That information is obtained by inspecting the OS boot log and if you clear it, there is no alternate way for it to be derived accurately.

Actions #5

Updated by Jim Middleton over 3 years ago

Jim Pingle wrote in #note-4:

This is normal and expected. That information is obtained by inspecting the OS boot log and if you clear it, there is no alternate way for it to be derived accurately.

Thank you.

Actions

Also available in: Atom PDF