> The -i option requires privilege to write to the destination.
>
> The -u option requires privilege secpolicy_ucode_update(),
> which is currently PRIV_ALL. The privilege checking will be
> performed by the driver. User with "Maintenance and Repair"
> profile will be allowed to execute "/usr/sbin/ucodeadm -u" to
> update microcode.
>
> What privilege does the -i subcommand require? How does it compare to
> the secpolicy_ucode_update() privilege required for the -u subcommand?
> Presumably, the two subcommands require identical privilege, but it's
> best to be explicit.
Actually I meant to say
The -i option requires write permission to the destination.
It does not require secpolicy_ucode_update() privilege.
Thanks,
Sherry
