Sponsored Content
Full Discussion: Need Help
Special Forums Cybersecurity Need Help Post 51803 by woofie on Tuesday 1st of June 2004 07:47:26 PM
Old 06-01-2004
Just got a old system given to me on the weekend. It doesn't have working PS/2 ports (keyboard and mouse) So I'm going to use USB keybaord and mouse.

I'm looking at setting up a honeypot with this machine. Then with a Linux machine I was going to use that to hack into my Windows machine on my own network behind my firewall. Also just run basic scans and stuffn on my own network to see how the honey pot works and what information it gets etc.

I'm thinking then I might setup a IDS systems. Just to have a little play with that.

When all this is done and I got a betetr idea of how all this works and what can be done. I'm going to look at re-creating a distro of Linux for security. Not sure at teh features I'll do if I do this yet. This will mainly be for a learning thing, more then liekly wont go any further Smilie
 
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)			 systemd-machine-id-commit.service		      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)

NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk SYNOPSIS
systemd-machine-id-commit.service DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk file system. See machine-id(5) for more information about machine IDs. This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes. See systemd-machine-id-setup(1) for details. The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase. This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to make it permanent. SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1) systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
All times are GMT -4. The time now is 11:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy