r1 - 2004-11-04 - 21:39:20 - RobDayYou are here: NTP >  Dev Web > BitKeeperNotes > BkRepoStructure
NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.

ntp-4.2.8p13 was released on 07 March 2019. It addresses 1 medium-severity security issue in ntpd, and provides 17 non-security bugfixes and 1 other improvements over 4.2.8p12.

Please see the NTP Security Notice for vulnerability and mitigation details.

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
When you first clone a BK repo, the directory structure is there but the files typically aren't; they're normally initially under SCCS control in their respective SCCS/ directories. A summary of these SCCS file types is found in bk helptool under the files entry, but the only ones of interest here are, as an example:

  • SCCS/s.foo.c, the "s.file", which contains the revision history of all versions of a given file, and
  • foo.c, the corresponding "gfile" or "gotten" file, the file you'd get after checking out the s.file

If you're going to work with a file, you'd normally check out that file to get its respective s.file, but there are a number of things you can query about a file just based on its gfile name without actually having to check it out, as you'll see shortly.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback