Reference Guide

Miscellaneous configuration and
management
Topics:
• OpenManage Ansible modules licensing
• Protect authenticity and integrity
• Signature file verification
• Ansible module security
OpenManage Ansible modules licensing
OMAM is open source and licensed under the GNU General Public License v3.0+. For more details see COPYING.md. iDRAC
and OpenManage Enterprise may require its own licenses for some functions in OMAM to work. Refer the User Guide for more
details.
Protect authenticity and integrity
To ensure the product integrity, the OMAM installation package is signed and uploaded to https://www.dell.com/support. The
collection bundle uploaded to ansible-galaxy is also signed.
Signature file verification
About this task
To verify the signature file, perform the following steps:
Steps
1. Download GPG3 public key from https://linux.dell.com/files/pgp_pubkeys/0x1285491434D8786F.asc.
2. Import the public key in the system using GPG. gpg --import 0x1285491434D8786F.asc
3. Upon running gpg --list-key, it lists the key ID 34D8786F.
4. Validate signature file using gpg --verify <FileName>.tar.gz.sign <FileName>.tar.gz or gpg -v --
verify <FileName>.tar.gz.sign <FileName>.tar.gz
Verification is successful if you see the following output:
gpg: Signature made Fri 17 Nov 2017 03:40:10 PM IST using RSA key ID 34D8786F
gpg: using PGP trust model
gpg: Good signature from "Dell Inc., PGRE 2012 (PG Release Engineering Build Group
2012) <[e-mail]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 4255 0ABD 1E80 D7C1 BC0B AD85 1285 4914 34D8 786F
gpg: binary signature, digest algorithm SHA512
4
Miscellaneous configuration and management 9