Lines Matching full:usb

1 # In-Band Update of BMC Firmware using USB
17 and USB is not yet supported.
19 The intent of this new application design is to enable the USB driver of BMC to
26 - Monitor whether the USB key is inserted.
27 - The first tar file found in the sorted list of files on the USB device is
38 phosphor-usb-code-update). The design process is as follows:
40 - Define a macro switch (`usb-code-update`) in [phosphor-software-manager][1]
41   repository to identify whether to enable the USB Code Update function, which
43 - If `usb-code-update` enabled, install the udev rules file to
46   start the phosphor-usb-code-update daemon.
47 - This daemon verifies the `/run/media/usb/sda1` directory and copies the first
49 - Set ApplyTime to OnReset so that the proposed usb code update app does not
53 - Exit the phosphor-usb-code-update daemon.
60 …block", ACTION=="add", ENV{ID_USB_DRIVER}=="usb-storage", ENV{DEVTYPE}=="partition", ENV{SYSTEMD_W…
67 - Assuming that the USB drive has a physical security vulnerability (such as
68   memory overflow, etc.), should disable "USB code update" via Redfish. After
69   the vulnerability is fixed, enable "USB code update" again via Redfish.
81 This impacts security because it can copy files to the BMC via an external USB
87 - When the USB code update is disabled, the service will return directly without
89 - Manually insert the USB key with the firmware upgrade package, and check
92   `systemcl start usb-code-update@sda1.service`)