06-07-2013
Agreed, you can't convert. The entire point of keeping passwords in hashes is because you cannot reverse them. You can only compare a hash to another hash.
This User Gave Thanks to Corona688 For This Post:
9 More Discussions You Might Find Interesting
1. Programming
Hi,
I have usernames and passwords (to connect oracle DB) buried in so many shell scripts.
We want to externalize all usernames and passwords from those shell scripts and encrypt them and keep them in a file.
So far I found two choices,
1) Use some encryption algorithms like (RC5/MD5) to... (5 Replies)
Discussion started by: satguyz
5 Replies
2. HP-UX
Hi,
We are planning to do migration from HP-UX to Redhat linux. We have 1300 makefiels. Is there any difference between HP-UX make and GNU make? Is there any tutorial on that?
Regards
hari_anj (0 Replies)
Discussion started by: hari_anj
0 Replies
3. UNIX for Dummies Questions & Answers
hello ppl, someone must be able to help with this --> I have an old NCR tower 32 with an ADDS terminal running a unix version 020102 (Im not sure if thats correct but its unix for sure). I have no user names and no passwords and need to login to read a tape. Is there any way to do that? I hear... (3 Replies)
Discussion started by: orestis
3 Replies
4. UNIX for Dummies Questions & Answers
Thanks
AVKlinux (3 Replies)
Discussion started by: avklinux
3 Replies
5. UNIX for Dummies Questions & Answers
In unix, i know the password encrypt by using salt
But how does it work? And how windows protect its password?
Thank you for helping in advance (5 Replies)
Discussion started by: cryogen
5 Replies
6. UNIX for Dummies Questions & Answers
Hi,
We are currently using solaris 9 on sunfire v240 and strongly considering to migrate to redhat enterprise. But we are not sure if we can install redhat enterprise on sunfire WS . Although, we will purchase a X64 machine we also want to use sunfire machine.
can we install redhat on sunfire... (2 Replies)
Discussion started by: titanic
2 Replies
7. Red Hat
Hi expert,
after creating users on Redhat, i wantn to change their password with something that easy to remember and the way we use. For example
#passwd username
hello$123
it don't allow me. It may has something to do /etc/pam.d/filesXXXX there which i don't know to change to allow root... (1 Reply)
Discussion started by: lamoul
1 Replies
8. Red Hat
Hi,
I need to migrate using Redhat 4 as host based migration,EMC Clariion to VNX.
Please what are the best ways to perform online migration,with users working on the box?The file system is ext3 and the source logical voulumes are raid 1.
- adding the 3rd LUN(from VNX) to the... (0 Replies)
Discussion started by: tanislavm11
0 Replies
9. Solaris
Does anyone have experience running the Vormetric Data Encryption on Oracle Solaris platform? (0 Replies)
Discussion started by: dwevans
0 Replies
LEARN ABOUT MOJAVE
eficheck
EFICHECK(8) BSD System Manager's Manual EFICHECK(8)
NAME
eficheck -- check the integrity of the x86 flash chip firmware.
SYNOPSIS
eficheck --integrity-check [-h EFI-hash-input-file] [-b EFI-binary-input-file]
eficheck --show-hashes [-h EFI-hash-input-file] [-b EFI-binary-input-file]
eficheck --generate-hashes [-h EFI-hash-output-file] [-p output-path]
eficheck --save [-b EFI-binary-output-file]
eficheck --cleanup [-b EFI-binary-input-and-output-file>]
eficheck --version
eficheck --help
DESCRIPTION
eficheck is a tool to check the x86 flash chip firmware.
The following commands can be used with eficheck:
--integrity-check hashes portion of the firmware and compares against known-good hashes
--generate-hashes outputs hashes for a given firmware to be used as known-good hashes
--show-hashes shows the hashes for the sub-sections of the firmware which are measured
--save saves the full flash chip contents to a binary file. Requires root privileges.
--cleanup zeros any privacy-sensitive data (such as nvram), enabling the file to be shared for analysis.
--version print out eficheck version number.
--help display a short help.
EXAMPLES
'eficheck --save -b firmware.bin'
Save this system's EFI firmware as firmware.bin
'eficheck --cleanup -b firmware.bin'
Overwrite the EFI variables portion of the firmware.bin, in place
'eficheck --generate-hashes'
Analyze the current system's installed EFI firmware, and store the hashes into hash file(s) in current folder
File name(s) will be selected according to image's EFI version(s)
'eficheck --generate-hashes -b firmware.bin'
Analyze the firmware.bin, and store the hashes into hash file(s) in current folder. Filename will be based on the detected
firmware version.
'eficheck --generate-hashes -p /usr/local/allowlists'
Analyze the current system's installed EFI firmware, and store the hashes into hash file(s) in /usr/local/allowlists folder
'eficheck --integrity-check'
Attempt to automatically determine which firmware you are running, and integrity check against the appropriate file, and report
any differences
'eficheck --integrity-check -h /usr/libexec/firmwarecheckers/eficheck/EFIAllowListShipping.bun-
dle/allowlists/IM171.88Z.0105.B08.1604111319.0.ealf'
Compare the current system's EFI firmware against the Apple-provided expected measurements for an "iMac17,1" at firmware revision
B08, and report any differences
'eficheck --integrity-check -h hash.ealf -b firmware.bin'
Compare the given hash file against against the given firmware image and report any differences
'eficheck --show-hashes'
Print the hashes for the current system's installed EFI firmware to stdout
'eficheck --show-hashes -b firmware.bin'
Print the hashes for the given firmware.bin to stdout
'eficheck --show-hashes -h IM171.88Z.0105.B08.1604111319.0.ealf'
Print the hashes for the given allowlist to stdout
May 25, 2017