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.8p15 was released on 23 June 2020. It addresses 1 medium-severity security issue in ntpd, and provides 13 non-security bugfixes over 4.2.8p13.
Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
Adding, renaming and deleting webs are all web-based operations.
is divided into webs; each one represents one subject, one area of collaboration. Administrators can add/rename/delete webs.
Choose Web Template
There are two methods used to create a new web. First you can use a specially designed TemplateWeb
. This is an invisible web that begins with an underscore "_" character (for example
). All topics in the template web will be copied into your new web.
The second method is to use an existing web as a template web. This may be useful if you already have a web that you would like to use as a starting point. Only topics that have names beginning with Web...
(like "WebHome", "WebNotify", etc.) are copied.
In either case you will want to be sure to verify that your new web has all the custom modifications that you desire. Any TWikiVariables
defined in the form below will automatically be set in the WebPreferences of the new web.
Adding a New Web
- You must have
ROOTCHANGE access to create a top-level web (one with no parent)
- Only the person who created it has permission to change the WebPreferences in the new web
You can only create hierarchical webs (webs within webs) if the
setting in configure
is enabled. Hierarchical webs are currently enabled.
You might not need hierarchical webs. TWiki topics already have a parent/child relationship within a web, which is shown in the breadcrumb. Try to keep the number of webs to a minimum in order to keep search and cross-referencing simple.
You can create hierarchical webs via the Adding a New Web
form above, by using a slash- or dot-separated path name which is based on an existing web name in the Name of new web:
To create a subweb named
inside a web named
as the new web name in the form above.
Subweb Preferences are Inherited
The preferences of a subweb are inherited from the parent web and overridden locally. Preferences are ultimately inherited from the TWiki.TWikiPreferences
Example Preference Inheritance for
TWiki.TWikiPreferences site-wide preferences
Sandbox.WebPreferences inherits from and overrides settings in
Sandbox/TestWeb.WebPreferences inherits from and overrides settings in
Sandbox/TestWeb/SubWeb.WebPreferences inherits from and overrides settings in
Sandbox/TestWeb/SubWeb.SubWebTopic inherits from and overrides settings in
The Pattern skin (default) indicates Subwebs by indenting them in the sidebar relative to their level in the hierarchy.
Renaming or Deleting a Web
Rename a web via the Tools section in each WebPreferences
topic. You may delete a web by moving it into a Trash web.
You may only rename a web if you have the following permissions
- You must be allowed to rename and changes topics in the web you want to rename
- You must be allowed to rename topics in the parent web of the web you want to rename
- If the web is a root web (i.e. it has no parent web) then you must have permission to both create and rename root webs. These permissions are controlled by the ALLOWROOTCHANGE preference, which can be set in Users.TWikiPreferences.
- If you move the web to another parent web you must be allowed to create and change topics in the new parent web.
When you rename a web TWiki will try and update all links that refer to the old web. You should note that links only get updated in topics that you are allowed to edit. If you use access rights in the TWiki installation it is generally best to let an administrator rename webs to avoid too many broken links.
If anyone is editing a topic which requires updating, or which lives in the web being renamed, a second confirmation screen will come up which will indicate which topics are still locked for edit. You may continue to hit the refresh button until an edit lease is obtained for each topic which requires updating (the "Refresh" button will change to "Submit"), or hit "Cancel", which will cancel your edit lease on all affected topics.
Renaming the webs in the distribution
It is possible, though not recommended, to change the names of the webs in the distribution.
If you plan to rename the Users web, remember that TWiki stores user topics in this web. That means that every WikiName
- points to it and would need updating (unless the variable,
, is used throughout). This potentially large change can be performed automatically if you rename the web from the Tools section of WebPreferences
, as described above.
If you want to rename the TWiki or Users webs, remember they are referred to in the TWiki configuration. You will need to change the
settings in the configuration using the configure
Renaming the webs in the distribution is not recommended because it makes upgrades much more complicated.
Related Topics: AdminDocumentationCategory