Mailinglist Archive: opensuse-security (555 mails)
| < Previous | Next > |
Re: [suse-security] Orginal firewall.rc.config file ?
- From: "Robert Davies" <Rob_Davies@xxxxxxxxxxxx>
- Date: Mon, 28 May 2001 15:50:44 +0100
- Message-id: <003e01c0e786$473d2f80$c40669d5@oak>
> Now that I am having all these problems with firewalls etc
> and maybe messed up my orginal firewall.rc.config file
> does any one have an orginal one that I could use
> as a template please ?
You have it already to extract it look at rpm(8), this will get you on the
right track, it goes something like the following :
rpm -qf /etc/rc.config.d/firewall.rc.config
Tells you which rpm package the file belongs to, you can confirm with,
rpm -ql <package>. To see what files have been altered, use the verify
option.
rpm --verify <package>
Perhaps you want to compare with the CD-ROM of installation?
rpm -Vp /cdrom/suse/<packet>/<rpmfile>
You can reinstall, and you can also extract the RPM to a different root
directory, avoiding updating the machine rpm database.
Another good option with many files, is to install the source rpm, and find
the configuration file in their, and then diff.
I like to use rcs(1) to have version control on these files, which allows me
to record reasons for, and to easily back out changes with ci(1) and co(1).
rcsdiff(1) is also very useful! Install the package from the development
packets and then create an RCS directory in /etc. Remember to 'ci -u' to
get an unlocked readable copy of the file, when you have made changes, you
can see files status with $Id$ and the log in the file, with the $Log$ flag.
Rob
> and maybe messed up my orginal firewall.rc.config file
> does any one have an orginal one that I could use
> as a template please ?
You have it already to extract it look at rpm(8), this will get you on the
right track, it goes something like the following :
rpm -qf /etc/rc.config.d/firewall.rc.config
Tells you which rpm package the file belongs to, you can confirm with,
rpm -ql <package>. To see what files have been altered, use the verify
option.
rpm --verify <package>
Perhaps you want to compare with the CD-ROM of installation?
rpm -Vp /cdrom/suse/<packet>/<rpmfile>
You can reinstall, and you can also extract the RPM to a different root
directory, avoiding updating the machine rpm database.
Another good option with many files, is to install the source rpm, and find
the configuration file in their, and then diff.
I like to use rcs(1) to have version control on these files, which allows me
to record reasons for, and to easily back out changes with ci(1) and co(1).
rcsdiff(1) is also very useful! Install the package from the development
packets and then create an RCS directory in /etc. Remember to 'ci -u' to
get an unlocked readable copy of the file, when you have made changes, you
can see files status with $Id$ and the log in the file, with the $Log$ flag.
Rob
| < Previous | Next > |