11-07-2017
You can perform cryptographic hash functions on files to baseline and confirm file integrity.
This User Gave Thanks to Neo For This Post:
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear all,
After succesful installation of UNIX SCO WARE 7.0, while booting the system it is displaying as follows:
The kernel will be rebuilt to incorporate recent configaration changes
Press Enter when ready OR
Press Escape to Stop.
While pressing Enter, message is coming again and again... (2 Replies)
Discussion started by: konda
2 Replies
2. UNIX for Dummies Questions & Answers
How would I rebuild the sun solaris kernel to include my new Oracle paramters? (3 Replies)
Discussion started by: jigarlakhani
3 Replies
3. Shell Programming and Scripting
Can somebody give me the link to get the source code of BASH? (1 Reply)
Discussion started by: bhargava
1 Replies
4. Linux
I can't find a source rpm for a particular tool that I'm trying to modify. I can only get a hold of the noarch and tar.bz2. Can I modify either one of these and re-package them as a noarch.rpm? (2 Replies)
Discussion started by: eur0dad
2 Replies
5. HP-UX
Hi
i have compiled and installed bash 3.2 on my hp-ux parisc
its in path /usr/local/pkg/bash/bin/bash .....When im search for this bash (through whereis bash) im not findind but other which i hve done in same procedure( gettext,m4) ..Im able to find through whereis search option
can any1... (3 Replies)
Discussion started by: vasanthan
3 Replies
6. Shell Programming and Scripting
Hi, experts.
Whould anybody clear explay me difference and usage of these 3 commands (particulary in bash) :
exec
eval
source
I've tryed to read the manual pages but did not get much.
Also could not get something useful from Google search - just so much and so not exactly, that is... (3 Replies)
Discussion started by: alex_5161
3 Replies
7. UNIX Desktop Questions & Answers
Issue resolved:
The 'culprit file' was .bash_aliases. It had the naughty (ASCII for the octal string Bash was detecting and returning an error about). I cleaned it up in Pico (see my post to the thread on favorite editors if you want background on why I use Pico/Nano), re-sourced it via... (0 Replies)
Discussion started by: SilversleevesX
0 Replies
8. AIX
Hi Guru's,
I'm trying to rebuild a very old HMC 7315-C02 the hard disk has gone so needs replacing. I've managed to find an old IDE hard disk lying around but its obvious that it's had windows running on it as the HMC install disks won't recognise the format. I'm trying to install HMC V6 R1.2... (3 Replies)
Discussion started by: elcounto
3 Replies
9. UNIX for Dummies Questions & Answers
I'm rebuilding my primary computer at work tomorrow. Currently, it has Windows 7. I would like to replace the main system with either Linux or Unix, although I would like to be able to run a fully operational Windows as a VM within that. Any recommendations on which Linux or Unix to go with?
I'm... (6 Replies)
Discussion started by: Sean_
6 Replies
LEARN ABOUT OPENSOLARIS
systemd-veritysetup-generator
SYSTEMD-VERITYSETUP-GENERATOR(8) systemd-veritysetup-generator SYSTEMD-VERITYSETUP-GENERATOR(8)
NAME
systemd-veritysetup-generator - Unit generator for integrity protected block devices
SYNOPSIS
/lib/systemd/system-generators/systemd-veritysetup-generator
DESCRIPTION
systemd-veritysetup-generator is a generator that translates kernel command line options configuring integrity protected block devices
(verity) into native systemd units early at boot and when configuration of the system manager is reloaded. This will create systemd-
veritysetup@.service(8) units as necessary.
Currently, only a single verity device may be se up with this generator, backing the root file system of the OS.
systemd-veritysetup-generator implements systemd.generator(7).
KERNEL COMMAND LINE
systemd-veritysetup-generator understands the following kernel command line parameters:
systemd.verity=, rd.systemd.verity=
Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.systemd.verity= is honored only by the
initial RAM disk (initrd) while systemd.verity= is honored by both the host system and the initrd.
roothash=
Takes a root hash value for the root file system. Expects a hash value formatted in hexadecimal characters, of the appropriate length
(i.e. most likely 256 bit/64 characters, or longer). If not specified via systemd.verity_root_data= and systemd.verity_root_hash=, the
hash and data devices to use are automatically derived from the specified hash value. Specifically, the data partition device is looked
for under a GPT partition UUID derived from the first 128bit of the root hash, the hash partition device is looked for under a GPT
partition UUID derived from the last 128bit of the root hash. Hence it is usually sufficient to specify the root hash to boot from an
integrity protected root file system, as device paths are automatically determined from it -- as long as the partition table is
properly set up.
systemd.verity_root_data=, systemd.verity_root_hash=
These two settings take block device paths as arguments, and may be use to explicitly configure the data partition and hash partition
to use for setting up the integrity protection for the root file system. If not specified, these paths are automatically derived from
the roothash= argument (see above).
SEE ALSO
systemd(1), systemd-veritysetup@.service(8), veritysetup(8), systemd-fstab-generator(8)
systemd 237 SYSTEMD-VERITYSETUP-GENERATOR(8)