Manual Package Updates - Revision history

Paul Blankenbaker: Updated directions for arp-scan

2024-05-07T07:42:17Z

Updated directions for arp-scan

← Older revision		Revision as of 03:42, 7 May 2024
Line 1:		Line 1:
	~~Currently, there are no packages which have "add-ons" which need to be manually updated.~~		= Package Data Files =

	* Update the ~~IAB and OUI files used by~~ the arp-scan ~~utility (use~~ NST ~~WUI~~ to ~~get two new ones download then transfer to ''~~src~~'' directory for~~ the ''arp-scan~~'' RPM)~~.		== arp-scan ==

			Update the yum/pkgs/arp-scan/src/ieee-oui.txt included in the arp-scan package by:

			* Use the "Update OUI" button in the settings panel on the NST WUI.
			* Copy the updated /usr/share/arp-scan/ieee-oui.txt file from the NST system to the yum/pkgs/arp-scan/src/ieee-oui.txt location on the NST build system.
			* Bump the release number in yum/pkgs/arp-scan/pkginfo.xml.
			* Update the change log in yum/pkgs/arp-scan/template.spec.

	= Check Package URLs =		= Check Package URLs =

2021-06-13T17:05:08Z

@@ Line 39: / Line 39: @@
   [nst28-repo@nst yum]$ make changelog-date-check
   all - Changelog date(s) ok
   [nst28-repo@nst yum]$

2018-06-30T11:54:35Z

← Older revision		Revision as of 07:54, 30 June 2018
Line 33:		Line 33:
	NOTE: The ''skip'' entries indicate protocols which '''curl''' is unable to handle and verification is skipped. If you would like to verify the skipped entries, you will need to do it manually.		NOTE: The ''skip'' entries indicate protocols which '''curl''' is unable to handle and verification is skipped. If you would like to verify the skipped entries, you will need to do it manually.

			= Check Date Change Logs =

			Run the following command to verify that all change log dates in the spec files are good.

			[nst28-repo@nst yum]$ make changelog-date-check
			all - Changelog date(s) ok
			[nst28-repo@nst yum]$

	= Packages Which Can Be Updated =		= Packages Which Can Be Updated =

2016-07-02T14:03:28Z

← Older revision		Revision as of 10:03, 2 July 2016
Line 1:		Line 1:
	Currently, there are no packages which have "add-ons" which need to be manually updated.		Currently, there are no packages which have "add-ons" which need to be manually updated.

	* Boot a recent ISO build and bring up Firefox. Make sure that Firefox has its default settings set as specified on the [[Firefox Configuration]] page.

	* Update the IAB and OUI files used by the arp-scan utility (use NST WUI to get two new ones download then transfer to ''src'' directory for the ''arp-scan'' RPM).		* Update the IAB and OUI files used by the arp-scan utility (use NST WUI to get two new ones download then transfer to ''src'' directory for the ''arp-scan'' RPM).

2012-09-03T17:00:39Z

Packages Which Are Updatable

← Older revision		Revision as of 13:00, 3 September 2012
Line 36:		Line 36:


	= Packages Which ~~Are Updatable~~ =		= Packages Which Can Be Updated =

	Some other packages also have the notion of "updates", but these are either done automatically during the build process, or manually by the end user.		Some other packages also have the notion of "updates", but these are either done automatically during the build process, or manually by the end user.

2012-08-10T19:12:53Z

@@ Line 1: / Line 1: @@
 Currently, there are no packages which have "add-ons" which need to be manually updated.
-* Boot a recent build and bring up Firefox. Make sure that Firefox has its default settings set as specified on the [[Firefox Configuration]] page.
+* Boot a recent ISO build and bring up Firefox. Make sure that Firefox has its default settings set as specified on the [[Firefox Configuration]] page.
 * Update the IAB and OUI files used by the arp-scan utility (use NST WUI to get two new ones download then transfer to ''src'' directory for the ''arp-scan'' RPM).
 = Packages Which Are Updatable =

2012-02-27T16:03:31Z

← Older revision		Revision as of 12:03, 27 February 2012
Line 3:		Line 3:
	* Boot a recent build and bring up Firefox. Make sure that Firefox has its default settings set as specified on the [[Firefox Configuration]] page.		* Boot a recent build and bring up Firefox. Make sure that Firefox has its default settings set as specified on the [[Firefox Configuration]] page.

	* ~~The Metasploit exploits need~~ to ~~be manually updated~~ to the ~~latest version by hand before building the final release~~.		* Update the IAB and OUI files used by the arp-scan utility (use NST WUI to get two new ones download then transfer to ''src'' directory for the ''arp-scan'' RPM).

	= Packages Which Are Updatable =		= Packages Which Are Updatable =

2011-08-08T23:28:51Z

Packages Which Are Updatable

← Older revision		Revision as of 19:28, 8 August 2011
Line 12:		Line 12:

	* The nikto package has a update feature, but at this time it is not done prior to build the ISO image.		* The nikto package has a update feature, but at this time it is not done prior to build the ISO image.

	* The Nessus package allows one to update rules, but these rules can not be re-distributed. Hence the end users need to do this on their own.

	* The Snort package is similar to Nessus.

	* The GeoIP databases are similar to Nessus.

2009-09-23T10:58:18Z

← Older revision		Revision as of 06:58, 23 September 2009
Line 1:		Line 1:
	Currently, there are no packages which have "add-ons" which need to be manually updated.		Currently, there are no packages which have "add-ons" which need to be manually updated.

			* Boot a recent build and bring up Firefox. Make sure that Firefox has its default settings set as specified on the [[Firefox Configuration]] page.

	* The Metasploit exploits need to be manually updated to the latest version by hand before building the final release.		* The Metasploit exploits need to be manually updated to the latest version by hand before building the final release.

2009-09-20T15:34:07Z

Packages Which Have Updates

← Older revision		Revision as of 11:34, 20 September 2009
Line 1:		Line 1:
	Currently, there are no packages which have "add-ons" which need to be manually updated.		Currently, there are no packages which have "add-ons" which need to be manually updated.

	= Packages Which ~~Have Updates~~ =
			* The Metasploit exploits need to be manually updated to the latest version by hand before building the final release.

			= Packages Which Are Updatable =

			Some other packages also have the notion of "updates", but these are either done automatically during the build process, or manually by the end user.

	* The clamav package should ship with the latest signatures (this should be automatic in the configure/build process).		* The clamav package should ship with the latest signatures (this should be automatic in the configure/build process).

	* The ~~Metasploit exploits are no longer updated during~~ the ~~packaging. They are now updated as needed by the end user after the distribution~~.		* The nikto package has a update feature, but at this time it is not done prior to build the ISO image.

	* The ~~nikto~~ package ~~has a~~ update ~~feature~~, but at this ~~time it~~ is ~~not done prior~~ to ~~build the ISO image~~.		* The Nessus package allows one to update rules, but these rules can not be re-distributed. Hence the end users need to do this on their own.

			* The Snort package is similar to Nessus.

			* The GeoIP databases are similar to Nessus.