Users Guide

● ‑r for reboot if a reboot is required for the type of update being performed.
In the following command example, the command applies a BIOS DUP without any user confirmation, forces the execution in
the case of a downgrade from a more recent BIOS version, and reboots the system after the DUP is applied. This command is
executed provided the DUP satisfies all the system and version requirements.
BIOS_XR23Y_LN_1.2.8.BIN ‑q ‑f ‑r
For more information on the command line interface (CLI), see Command Line Interface Reference.
Verifying the Digital Signature
A digital signature is used to authenticate the identity of the signer of an Update Package and to certify that the original
content is unchanged. Digital signature of DUPs provide a reliable and trustful method of authentication.
Verifying the digital signature ensures that the original Update Package was received correctly and that the content has not
been modified since it was signed.
NOTE: Verifying the digital signature is applicable for systems running Windows and Linux.
Verifying the Digital Signature on Systems Running Linux
If you do not already have it installed on your system, you must install the Gnu Privacy Guard (GPG) to verify a Linux DUP digital
signature. To use the standard verification procedure, perform the following steps:
1. Get the Dell Linux public GnuPG keys (GPG1 and GPG2), if you do not already have it. You can download it by navigating to
https://linux.dell.com/files/pgp_pubkeys/.
2. Import the public key to the gpg trust database by running the following command: gpg --import <Public Key
Filename>
NOTE:
You need to import GPG1 and GPG2 public keys
● GPG 2 Key : 0x756ba70b1019ced6.asc
● GPG 1 Key : 0xca77951d23b66a9d.asc
3. To avoid a distrusted-key warning, validate the public key by its fingerprint before you use it.
a. Type the following command: gpg --edit-key 23B66A9D
b. In the GPG key editor, type fpr. The following message appears: pub 1024D/23B66A9D 2001-04-16 Dell,
Inc. (Product Group <linux [e-mail]>Primary key fingerprint: 4172 E2CE 955A
1776 A5E6 1BB7 CA77 951D 23B6 6A9D. If the fingerprint of the imported key is the same as the key owner's,
you have a correct copy of the key. You can verify the key's owner in person, over the phone, or by any other means that
guarantees that you are communicating with the key's true owner.
c. While still in the key editor, type sign.
d. Answer the list of trust-validation questions that appear and create a passphrase to use as the secret key. You must
import and validate the public key only once.
a. To avoid a distrusted-key warning, validate the GPG2 public key by its fingerprint before you use it.
b. Type the following command: gpg --edit-key 1019CED6
c. In the GPG key editor, type fpr. The following message appears: pub 2048D/1019CED6 2011-10-17 Dell Inc., PGRE
2011 (PG Release Engineering Build Group 2011) <[e-mail]>. Primary key fingerprint: 79A1
61F5 A83F 992C CB10 A544 756B A70B 1019 CED6. If the fingerprint of the imported key is the same as the key
owner's, you have a correct copy of the key. You can verify the key's owner in person, over the phone, or by any other
means that guarantees that you are communicating with the key's true owner.
d. c While still in the key editor, type sign.
e. Answer the list of trust-validation questions that appear and create a passphrase to use as the secret key. You must
import and validate the public key only once.
4. Obtain the Linux DUP and its associated signature file from dell.com/support/manuals/downloads.
NOTE:
Each Linux DUP has a separate signature file, which is displayed along with the DUP. You need both the DUP
and its associated signature file for verification. By default, the signature file is named the same as the DUP filename
with a sign extension.
5. Verify the DUP using the following command: gpg --verify <Linux Update Package signature filename> <Linux Update
Package filename>.
12
Using Dell Update Packages