The NetBSD Update System

More documents

Recommendations

Info

Implications an update can be backed out and replaced by previous contents less onus for security instructions in security advisories digital signature provenance needs to be kick-started reliance upon GPLed code in a BSD utility
Who can use it? Anyone using the <strong>NetBSD</strong> Packages Collection Not necessarily <strong>NetBSD</strong> Notification feature advises when updates are needed
Page 1 and 2: The NetBSD Update System Maintainin
Page 3 and 4: Other approaches Windows Update RPM
Page 5 and 6: Help is at hand...
Page 7 and 8: Package naming conventions A consis
Page 9 and 10: The pkg-vulnerabilities file
Page 11 and 12: Digital Signing
Page 13 and 14: Installing a digitally-signed packa
Page 15 and 16: Pre-requisites for NetBSD Update Ne
Page 17 and 18: Windows Update Site DoS measures ea
Page 19 and 20: Stages in NetBSD Update Notificatio
Page 21 and 22: Vulnerability A package can either
Page 23 and 24: The update-list file
Page 25 and 26: Checkpoints System checkpoint facil
Page 27 and 28: Aspects of updating Changes to conf
Page 29: Template pkgsrc Makefile
Page 33 and 34: Extensibility Sun’s patch system
Page 35 and 36: Who should use it? Anyone who is se
Page 37 and 38: NetBSD Update in Action (2)
Page 43 and 44: Future Work replace gpg with BSD-li
Page 45 and 46: The End
Page 47: Contact details Alistair G. Crooks

The NetBSD Update System

Create successful ePaper yourself

Delete template?

Save as template?