From 25fee1f33e0bcf9526e7b9054a6c8d262c39fbf4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A1nos=20Barta?= Date: Wed, 24 May 2023 16:29:05 +0200 Subject: [PATCH 1/6] xx updates maketargets.json and versions for 3.38 --- Maketargets.json | 4 ++-- Project/VariableSets/Version.flvar | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Maketargets.json b/Maketargets.json index b0ecd3197..091e764ec 100644 --- a/Maketargets.json +++ b/Maketargets.json @@ -6,8 +6,8 @@ "productnameinepic": "syslog-ng-open-source-edition", "condition": "General.OSE", "conditions-to-exclude": "General.PE or General.pe6 or General.SPS or General.SRA or General.ARS", - "version": "3.36", - "techversion": "3.36" + "version": "3.38", + "techversion": "3.38" }, "syslog-ng-ose-guide-admin": { "condition": "General.OSE", diff --git a/Project/VariableSets/Version.flvar b/Project/VariableSets/Version.flvar index 7d4170838..ddefcb7f0 100644 --- a/Project/VariableSets/Version.flvar +++ b/Project/VariableSets/Version.flvar @@ -3,13 +3,13 @@ 3.36 + EvaluatedDefinition="3.38">3.38 3.36 + EvaluatedDefinition="3.38">3.38 3.36 + EvaluatedDefinition="3.38">3.38 \ No newline at end of file From bdab9c595294bd3f70be12a9124957836e20ab6a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A1nos=20Barta?= Date: Wed, 24 May 2023 16:34:38 +0200 Subject: [PATCH 2/6] xx adds Content\Guides\TechComm folder to exclusion list --- .gitignore | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/.gitignore b/.gitignore index 83837581e..d116cb9a9 100644 --- a/.gitignore +++ b/.gitignore @@ -13,7 +13,6 @@ /Content/Resources/PageLayouts /Content/Resources/Snippets /Content/Resources/Stylesheets -/Content/Resources/SyntaxHighlighting /Content/Resources/TableStyles /Content/SaaSReleaseNotes /Content/Sources @@ -42,5 +41,4 @@ OneIdentity_TemplateForNewProjects.flprj docadmin.persist docadmin.pkl Thumbs.db* -debug.log -.venv +debug.log \ No newline at end of file From ae50e73155583ee062d320ea139ce46c46fb49ab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A1nos=20Barta?= Date: Wed, 24 May 2023 17:48:43 +0200 Subject: [PATCH 3/6] 418515 ag rn adds new doc license, fixes broken online links --- .../Guides/shared/documentation-license.htm | 44 +++++++ .../syslog-ng-guide-admin/chapter-install.htm | 2 +- .../syslog-ng-guide-admin/cisco-parser.htm | 2 +- .../compiling-syslog-ng.htm | 3 +- .../concepts-licensing.htm | 1 + .../parser-checkpoint.htm | 2 +- .../parser-fortigate.htm | 2 +- .../syslog-ng-guide-admin/parser-netskope.htm | 3 +- .../syslog-ng-guide-admin/parser-websense.htm | 2 +- .../syslog-ng-guide-admin/report-bugs.htm | 2 +- .../supported-platforms.htm | 2 +- .../mutual-authentication-summary.htm | 5 +- ...ction-tutorial-mutual-tls-introduction.htm | 9 +- Content/Guides/whatsnew/3. New Features.htm | 108 +----------------- Content/Guides/whatsnew/4. Enhancements.htm | 7 +- .../Guides/whatsnew/6. Resolved Issues.htm | 2 +- Project/TOCs/syslog-ng-ose-guide-admin.fltoc | 7 +- .../TOCs/syslog-ng-ose-guide-whatsnew.fltoc | 16 ++- syslog-ng OSE Documentation License.txt | 29 +++++ 19 files changed, 116 insertions(+), 132 deletions(-) create mode 100644 Content/Guides/shared/documentation-license.htm create mode 100644 syslog-ng OSE Documentation License.txt diff --git a/Content/Guides/shared/documentation-license.htm b/Content/Guides/shared/documentation-license.htm new file mode 100644 index 000000000..4297c4c5e --- /dev/null +++ b/Content/Guides/shared/documentation-license.htm @@ -0,0 +1,44 @@ + + + + + +

The Documentation License

+ +

Permission is hereby granted, free of charge, to any person obtaining a copy of these documentation files (the "Documentation"), to use the Documentation subject to the following conditions:

+
    +
  1. +

    The above copyright notice and this permission notice shall be included in all copies or portions of the Documentation. Any and all copies of the above copyright and this permission notice contained in the Documentation shall not be removed, obscured, or modified.

    +
    2. +
  2. +

    If you modify the Documentation, You must cause any modified files to carry prominent notices stating that You changed the files.

    +
    3. +
  3. +

    The Documentation contains trademarks and registered trademarks owned by One Identity and its affiliates. Permission is granted to make and distribute verbatim copies of the Documentation from the official syslog-ng.com site. Modified versions of the Documentation containing One Identity trademarks are permitted exclusively for internal use; however, all external distributions of modified Documentation are prohibited from containing any One Identity trademarks which include syslog-ng, the syslog-ng logo, Balabit, the Balabit logo, One Identity and the One Identity logo.

    +
    4. +
  4. +

    No relationship is established as a result of this Documentation license. Any statements that suggest a partnership or other relationship with One Identity and its affiliates are prohibited.

    +
    5. +
+

THE DOCUMENTATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DOCUMENTATION OR THE USE OR OTHER DEALINGS IN THE DOCUMENTATION.

+

YOU ACKNOWLEDGE THAT THE DOCUMENTATION YOU ARE DOWNLOADING IS SUBJECT TO THE RESTRICTIONS AND CONTROLS IMPOSED BY UNITED STATES EXPORT REGULATIONS. +

+

YOU CERTIFY THAT: +

+
    +
  • +

    YOU DO NOT INTEND TO USE THE DOCUMENTATION FOR ANY PURPOSE PROHIBITED BY UNITED STATES EXPORT REGULATIONS, INCLUDING, WITHOUT LIMITATION, TERRORISM, CYBER-ATTACKS, CYBER-CRIMES, MONEY-LAUNDERING, INDUSTRIAL ESPIONAGE, OR NUCLEAR, CHEMICAL OR BIOLOGICAL WEAPONS PROLIFERATION. +

    +
    • +
  • +

    YOU ARE NOT LISTED AS A DENIED PARTY ON ANY LIST GOVERNING UNITED STATES EXPORTS. +

    +
    • +
  • +

    YOU ARE NOT A NATIONAL OF ANY COUNTRY THAT IS NOT APPROVED TO RECEIVE A U.S. EXPORT. AS OF 2023, THESE COUNTRIES ARE CUBA, IRAN, NORTH KOREA, SYRIA, BELARUS AND RUSSIA. +

    +
    • +
+

If any of the above applicable conditions are not met or if your certification is inaccurate, this restricted copyright license is immediately terminated.

+ + \ No newline at end of file diff --git a/Content/Guides/syslog-ng-guide-admin/chapter-install.htm b/Content/Guides/syslog-ng-guide-admin/chapter-install.htm index 6c4968383..10997c29b 100644 --- a/Content/Guides/syslog-ng-guide-admin/chapter-install.htm +++ b/Content/Guides/syslog-ng-guide-admin/chapter-install.htm @@ -10,7 +10,7 @@

Installing syslog-ng

This chapter explains how to install on various platforms.

  • -

    You can install on many platforms using the package manager and official repositories of the platform. For a list of third-party packages available for various Linux, UNIX, and other platforms, see the [%=General.downloads-text%].

    +

    You can install on many platforms using the package manager and official repositories of the platform. For a list of third-party packages available for various Linux, UNIX, and other platforms, see syslog-ng Open Source Edition installation packages.

  • For instructions on compiling syslog-ng Open Source Edition from the source code, see Compiling syslog-ng from source.

    diff --git a/Content/Guides/syslog-ng-guide-admin/cisco-parser.htm b/Content/Guides/syslog-ng-guide-admin/cisco-parser.htm index ee9c99145..b2c937090 100644 --- a/Content/Guides/syslog-ng-guide-admin/cisco-parser.htm +++ b/Content/Guides/syslog-ng-guide-admin/cisco-parser.htm @@ -21,7 +21,7 @@

    Cisco parser

    <189>32: 0.0.0.0: *Apr 29 13:59:12.491: %SYS-5-CONFIG_I: Configured from console by console <189>32: foo: *Apr 29 13:58:46.411: %SYSMGR-STANDBY-3-SHUTDOWN_START: The System Manager has started the shutdown procedure.
    -

    NOTE: Note that not every Cisco log message conforms to this format. If you find a message that the cisco-parser() cannot properly parse, [%=General.contact-support-text%] so we can improve the parser.

    +

    NOTE: Not every Cisco log message conforms to this format. If you find a message that the cisco-parser() cannot properly parse, contact Support, so we can improve the parser.

    The application normalizes the parsed log messages into the following format:

    ${MESSAGE}=%FAC-SEV-MNEMONIC: message
 ${HOST}=origin-id
    diff --git a/Content/Guides/syslog-ng-guide-admin/compiling-syslog-ng.htm b/Content/Guides/syslog-ng-guide-admin/compiling-syslog-ng.htm index 31a671cc0..d7d3a9c35 100644 --- a/Content/Guides/syslog-ng-guide-admin/compiling-syslog-ng.htm +++ b/Content/Guides/syslog-ng-guide-admin/compiling-syslog-ng.htm @@ -1,6 +1,7 @@  + @@ -11,7 +12,7 @@

    Compiling syslog-ng from source

    Purpose:
    -

    To compile syslog-ng Open Source Edition (OSE) from the source code, complete the following steps. Alternatively, you can use precompiled binary packages on several platforms. For a list of third-party packages available for various Linux, UNIX, and other platforms, see the [%=General.downloads-text%].

    +

    To compile syslog-ng Open Source Edition (OSE) from the source code, complete the following steps. Alternatively, you can use precompiled binary packages on several platforms. For a list of third-party packages available for various Linux, UNIX, and other platforms, see syslog-ng Open Source Edition installation packages.

    Steps:
    diff --git a/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm b/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm index 1c19800ea..f4102fbb7 100644 --- a/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm +++ b/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm @@ -11,5 +11,6 @@

    Product licensing Practically, the code stored under the lib directory of the source code package is under LGPL, the rest is GPL.

    For details about the LGPL and GPL licenses, see GNU Lesser General Public License and GNU General Public License, respectively.

    +

    For clarity, the Documentation is licensed separately. For details, see The Documentation License.

    \ No newline at end of file diff --git a/Content/Guides/syslog-ng-guide-admin/parser-checkpoint.htm b/Content/Guides/syslog-ng-guide-admin/parser-checkpoint.htm index 829137d2e..9b3fbdf4f 100644 --- a/Content/Guides/syslog-ng-guide-admin/parser-checkpoint.htm +++ b/Content/Guides/syslog-ng-guide-admin/parser-checkpoint.htm @@ -17,7 +17,7 @@

    Check Point Log Exporter parser

    The Check Point Log Exporter parser can parse Check Point log messages. These messages do not completely comply with the syslog RFCs, making them difficult to parse. The checkpoint-parser() of solves this problem, and can separate these log messages to name-value pairs. For details on using value-pairs in see Structuring macros, metadata, and other value-pairs. The parser can parse messages in the following formats:

    <PRI><VERSION> <YYYY-MM-DD> <HH-MM-SS> <PROGRAM> <PID> <MSGID> - [key1:value1; key2:value2; ... ]

    For example:

    <134>1 2018-03-21 17:25:25 MDS-72 CheckPoint 13752 - [action:"Update"; flags:"150784"; ifdir:"inbound"; logid:"160571424"; loguid:"{0x5ab27965,0x0,0x5b20a8c0,0x7d5707b6}";]

    Splunk format:

    time=1557767758|hostname=r80test|product=Firewall|layer_name=Network|layer_uuid=c0264a80-1832-4fce-8a90-d0849dc4ba33|match_id=1|parent_rule=0|rule_action=Accept|rule_uid=4420bdc0-19f3-4a3e-8954-03b742cd3aee|action=Accept|ifdir=inbound|ifname=eth0|logid=0|loguid={0x5cd9a64e,0x0,0x5060a8c0,0xc0000001}|origin=192.168.96.80|originsicname=cn\=cp_mgmt,o\=r80test..ymydp2|sequencenum=1|time=1557767758|version=5|dst=192.168.96.80|inzone=Internal|outzone=Local|proto=6|s_port=63945|service=443|service_id=https|src=192.168.96.27|
    -

    If you find a message that the checkpoint-parser() cannot properly parse, [%=General.contact-support-text%] so we can improve the parser.

    +

    If you find a message that the checkpoint-parser() cannot properly parse, contact Support, so we can improve the parser.

    By default, the Check Point-specific fields are extracted into name-value pairs prefixed with .checkpoint. For example, the action in the previous message becomes ${.checkpoint.action}. You can change the prefix using the prefix option of the parser.

    Declaration:
    @version: 
diff --git a/Content/Guides/syslog-ng-guide-admin/parser-fortigate.htm b/Content/Guides/syslog-ng-guide-admin/parser-fortigate.htm
index 8c3f9d69e..f1dc79d01 100644
--- a/Content/Guides/syslog-ng-guide-admin/parser-fortigate.htm
+++ b/Content/Guides/syslog-ng-guide-admin/parser-fortigate.htm
@@ -14,7 +14,7 @@ 
    Fortigate parser
    
         
         
    The Fortigate parser can parse the log messages of FortiGate/FortiOS (Fortigate Next-Generation Firewall (NGFW)). These messages do not completely comply with the syslog RFCs, making them difficult to parse. The fortigate-parser() of  solves this problem, and can separate these log messages to name-value pairs. For details on using value-pairs in syslog-ng OSE see Structuring macros, metadata, and other value-pairs. The parser can parse messages in the following format:
    <PRI><NAME=VALUE PAIRS>
    
         
    For example:
    <189>date=2021-01-15 time=12:58:59 devname="FORTI_111" devid="FG100D3G12801312" logid="0001000014" type="traffic" subtype="local" level="notice" vd="root" eventtime=1610704739683510055 tz="+0300" srcip=91.234.154.139 srcname="91.234.154.139" srcport=45295 srcintf="wan1" srcintfrole="wan" dstip=213.59.243.9 dstname="213.59.243.9" dstport=46730 dstintf="unknown0" dstintfrole="undefined" sessionid=2364413215 proto=17 action="deny" policyid=0 policytype="local-in-policy" service="udp/46730" dstcountry="Russian Federation" srccountry="Russian Federation" trandisp="noop" app="udp/46730" duration=0 sentbyte=0 rcvdbyte=0 sentpkt=0 appcat="unscanned" crscore=5 craction=262144 crlevel="low"
    
-        
    If you find a message that the fortigate-parser() cannot properly parse, [%=General.contact-support-text%] so we can improve the parser.
    
+        
    If you find a message that the fortigate-parser() cannot properly parse, contact Support, so we can improve the parser.
    
         
    By default, the Fortigate-specific fields are extracted into name-value pairs prefixed with .fortigate. For example, the devname in the previous message becomes ${.fortigate.devname}. You can change the prefix using the prefix option of the parser.
    
         
    
             
    Declaration:
    @version: 
diff --git a/Content/Guides/syslog-ng-guide-admin/parser-netskope.htm b/Content/Guides/syslog-ng-guide-admin/parser-netskope.htm
index 55553753d..0629fc801 100644
--- a/Content/Guides/syslog-ng-guide-admin/parser-netskope.htm
+++ b/Content/Guides/syslog-ng-guide-admin/parser-netskope.htm
@@ -1,6 +1,7 @@
 
 
     
+        
         
     
     
@@ -15,7 +16,7 @@ 
    Netskope parser
    
         
         
    The Netskope parser can parse Netskope log messages. These messages do not completely comply with the syslog RFCs, making them difficult to parse. The netskope-parser() of  solves this problem, and can separate these log messages to name-value pairs. For details on using value-pairs in  see Structuring macros, metadata, and other value-pairs. The parser can parse messages in the following format:
    <PRI>{JSON-formatted-log-message}
    
         
    For example:
    <134>{"count": 1, "supporting_data": {"data_values": ["x.x.x.x", "user@domain.com"], "data_type": "user"}, "organization_unit": "domain/domain/Domain Users/Enterprise Users", "severity_level": 2, "category": null, "timestamp": 1547421943, "_insertion_epoch_timestamp": 1547421943, "ccl": "unknown", "user": "user@domain.com", "audit_log_event": "Login Successful", "ur_normalized": "user@domain.com", "_id": "936289", "type": "admin_audit_logs", "appcategory": null}
    
-        
    If you find a message that the netskope-parser() cannot properly parse, [%=General.contact-support-text%] so we can improve the parser.
    
+        
    If you find a message that the netskope-parser() cannot properly parse, contact Support, so we can improve the parser.
    
         
    The  application sets the ${PROGRAM} field to Netskope.
    
         
    By default, the Netskope-specific fields are extracted into name-value pairs prefixed with .netskope. For example, the organization_unit in the previous message becomes ${.netskope.organization_unit}. You can change the prefix using the prefix option of the parser.
    
         
    
diff --git a/Content/Guides/syslog-ng-guide-admin/parser-websense.htm b/Content/Guides/syslog-ng-guide-admin/parser-websense.htm
index dcc4219e1..f46c3149e 100644
--- a/Content/Guides/syslog-ng-guide-admin/parser-websense.htm
+++ b/Content/Guides/syslog-ng-guide-admin/parser-websense.htm
@@ -16,7 +16,7 @@ 
    Websense parser
    
         
         
    The Websense parser can parse the log messages of Websense Content Gateway (Raytheon|Websense, now Forcepoint). These messages do not completely comply with the syslog RFCs, making them difficult to parse. The websense-parser() of  solves this problem, and can separate these log messages to name-value pairs. For details on using value-pairs in  see Structuring macros, metadata, and other value-pairs. The parser can parse messages in the following format:
    <PRI><DATE> <TIMEZONE> <IP-ADDRESS> <NAME=VALUE PAIRS>
    
         
    For example:
    <159>Dec 19 10:48:57 EST 192.168.1.1 vendor=Websense product=Security product_version=7.7.0 action=permitted severity=1 category=153 user=- src_host=192.168.2.1 src_port=62189 dst_host=example.com dst_ip=192.168.3.1 dst_port=443 bytes_out=197 bytes_in=76 http_response=200 http_method=CONNECT http_content_type=- http_user_agent=Mozilla/5.0_(Windows;_U;_Windows_NT_6.1;_enUS;_rv:1.9.2.23)_Gecko/20110920_Firefox/3.6.23 http_proxy_status_code=200 reason=- disposition=1034 policy=- role=8 duration=0 url=https://example.com
    
-        
    If you find a message that the websense-parser() cannot properly parse, [%=General.contact-support-text%] so we can improve the parser.
    
+        
    If you find a message that the websense-parser() cannot properly parse, contact Support, so we can improve the parser.
    
         
    The  application sets the ${PROGRAM} field to Websense.
    
         
    By default, the websense-specific fields are extracted into name-value pairs prefixed with .websense. For example, the product_version in the previous message becomes ${.websense.product_version}. You can change the prefix using the prefix option of the parser.
    
         
    
diff --git a/Content/Guides/syslog-ng-guide-admin/report-bugs.htm b/Content/Guides/syslog-ng-guide-admin/report-bugs.htm
index 8eeecdea9..6d0fc99d6 100644
--- a/Content/Guides/syslog-ng-guide-admin/report-bugs.htm
+++ b/Content/Guides/syslog-ng-guide-admin/report-bugs.htm
@@ -5,6 +5,6 @@
     
     
         
    Reporting bugs and finding help
    
-        
    If you need help, want to open a support ticket, or report a bug, we recommend using the syslog-ng-debun tool to collect information about your environment and  version. For details, see The syslog-ng-debun manual page. For support contacts, see About us.
    
+        
    If you need help, want to open a support ticket, or report a bug, we recommend using the syslog-ng-debun tool to collect information about your environment and  version. For details, see the syslog-ng-debun manual page. For support contacts, see About us.
    
     
 
\ No newline at end of file
diff --git a/Content/Guides/syslog-ng-guide-admin/supported-platforms.htm b/Content/Guides/syslog-ng-guide-admin/supported-platforms.htm
index da426cb87..c8874037c 100644
--- a/Content/Guides/syslog-ng-guide-admin/supported-platforms.htm
+++ b/Content/Guides/syslog-ng-guide-admin/supported-platforms.htm
@@ -15,7 +15,7 @@ 
    Supported platforms
    
                 
    The source code of  is released under the GPLv2 license and is available on GitHub.
  • -

    See the [%=General.downloads-text%] for binary packages.

    +

    For the available binary installation packages, see syslog-ng Open Source Edition installation packages.

diff --git a/Content/Guides/tutorials/chapters/mutual-authentication-summary.htm b/Content/Guides/tutorials/chapters/mutual-authentication-summary.htm index 42b0ea5d9..a538f75b4 100644 --- a/Content/Guides/tutorials/chapters/mutual-authentication-summary.htm +++ b/Content/Guides/tutorials/chapters/mutual-authentication-summary.htm @@ -11,10 +11,7 @@

Summary

If you have run into problems, or need help, leave a comment, or post your problem on the syslog-ng mailing list.

  • -

    If you would like to know more about , visit the [%=General.website-text%], or check the [%=General.doc-site-text%].

    -
    • -
  • -

    If you would like to know more about , visit the syslog-ng product page, or check the [%=General.doc-site-text%].

    +

    If you would like to know more about , visit the syslog-ng product page, or check the documentation.

    • diff --git a/Content/Guides/tutorials/chapters/section-tutorial-mutual-tls-introduction.htm b/Content/Guides/tutorials/chapters/section-tutorial-mutual-tls-introduction.htm index 55d8fdf42..909a89cd8 100644 --- a/Content/Guides/tutorials/chapters/section-tutorial-mutual-tls-introduction.htm +++ b/Content/Guides/tutorials/chapters/section-tutorial-mutual-tls-introduction.htm @@ -6,7 +6,7 @@

    Introduction

    Collecting log messages is an essential part of managing, maintaining, and troubleshooting IT systems. Since your log messages can contain all kinds of sensitive information, you should make sure that they are kept safe. The easiest way to protect the log messages as they are transferred from your clients to your logserver is to authenticate and encrypt the connection between the client and the server.

    -

    This tutorial shows you step-by-step how to create the certificates required to authenticate your server and your clients, and how to configure () to send your log messages in an encrypted connection. Installing is not covered, but downloading it from the [%=General.downloads-text%] for your platform and installing it should be easyfor details, see .

    +

    This tutorial shows you step-by-step how to create the certificates required to authenticate your server and your clients, and how to configure () to send your log messages in an encrypted connection. Installing is not covered, but downloading it from the syslog-ng Open Source Edition installation packages for your platform and installing it should be easyfor details, see .

    The tutorial is organized as follows:

    • @@ -25,9 +25,8 @@

      -

      NOTE: Some of the command line examples in this section are quite long. You might need to scroll the example to read the whole example.

      - - +
      +

      NOTE: Some of the command line examples in this section are quite long. You might need to scroll the example to read the whole example.

      +
      \ No newline at end of file diff --git a/Content/Guides/whatsnew/3. New Features.htm b/Content/Guides/whatsnew/3. New Features.htm index b30952f9c..d6465d603 100644 --- a/Content/Guides/whatsnew/3. New Features.htm +++ b/Content/Guides/whatsnew/3. New Features.htm @@ -1,113 +1,13 @@  - +

      New features in version

      -

      If there are no new features (such as for some minor releases, maintenance releases), delete this section.

      -

      Remove the sentence containing links to Enhancements and Resolved issues if this document does not contain that section.

      -

      Provide information on updates to the existing functionality offered by this version. If you are listing three items or more, use bullets. Use subheadings if necessary.

      +

      If there are no new features (such as for some minor releases, maintenance releases), delete this section.

      +

      Remove the sentence containing links to Enhancements and Resolved issues if this document does not contain that section.

      +

      Provide information on updates to the existing functionality offered by this version. If you are listing three items or more, use bullets. Use subheadings if necessary.

      This section lists the most recent changes of ().

      -
        -
      • -

        New source: mqtt() -

        -

        You can use the mqtt() source to fetch messages from MQTT brokers.

        -
        • -
      • -

        New destination: discord() -

        -

        The discord() destination driver sends messages to Discord using Discord Webhook.

        -
        • -
      • -

        New parser: fortigate-parser() -

        -

        The Fortigate parser can parse the log messages of FortiGate/FortiOS (Fortigate Next-Generation Firewall (NGFW)). These messages do not completely comply with the syslog RFCs, making them difficult to parse. The fortigate-parser() of solves this problem, and can separate these log messages to name-value pairs. For details on using value-pairs in syslog-ng OSE see Structuring macros, metadata, and other value-pairs. The parser can parse messages in the following format:

        -
        • -
      • -

        New parser: regexp-parser() -

        -

        The application can parse fields from a message with the help of regular expressions. This can be also achieved with the match() filter, by setting the store-matches flag, but the regexp-parser() offers more flexibility, like multiple patterns and setting the prefix of the created name-value pairs.

        -
        • -
      • -

        New filter: rate-limit() -

        -

        Limits messages rate based on arbitrary keys in each message.

        -
        • -
      • -

        New options for the kafka() destination C implementation -

        -

        Options batch-lines() and batch-timeout() have been added.

        -
        • -
      • -

        New options for the kafka() destination C implementation -

        -

        Options batch-lines() and batch-timeout() have been added.

        -
        • -
      • -

        New option value: transport("text-with-nuls") -

        -

        text-with-nuls: Allows embedded NUL characters in the message from a TCP source, that is, will not delimiter the incoming messages on NUL characters, only on newline characters (contrary to tcp transport, which splits the incoming log on newline characters and NUL characters).

        -
        • -
      • -

        New option for file() destination: symlink-as() -

        -

        The configured file name will be used as a symbolic link to the last created file by file destination.

        -
        • -
      • -

        New options for redis() destination driver -

        -

        Added workers() and Match mode support to the Redis destination driver.

        -
        • -
      • -

        New --remove-orphans option in syslog-ng-ctl stats -

        -

        New option --remove-orphans has been added to the stats command.

        -
        • -
      • -

        New options for the mongodb() destination -

        -

        Options collection() and workers() have been added.

        -
        • -
      • -

        disk-buffer() has been updated -

        -

        New option: truncate-size-ratio(), and other changes.

        -
        • -
      • -

        time-reopen() option on multiple drivers -

        -

        The time-reopen() option was only configurable on the global options{} level. Now every driver, which utilizes it can configure it on the driver level.

        -
        • -
      • -

        New flag(): no-rfc3164-fallback -

        -

        This flag allows to attempt parsing RFC5424 first without an automatic fallback to RFC3164.

        -
        • -
      • -

        New TLS option: keylog-file() -

        -

        This option enables saving TLS secrets (decryption keys) for a given source or destination, which can be used to decrypt data with, for example, Wireshark. The given path and name of a file will be used to save these secrets.

        -
        • -
      • -

        Other enhancements -

        -
          -
        • -

          Monitoring - Metrics: message size and EPS.

          -
          • -
        • -

          Update the no-parse flag.

          -
          • -
        • -

          Added a note to the disk-buffer() dir() path.

          -
          • -
        • -

          Added macOS and NetBSD to the system() source.

          -
          • -
        -
        • -
      \ No newline at end of file diff --git a/Content/Guides/whatsnew/4. Enhancements.htm b/Content/Guides/whatsnew/4. Enhancements.htm index 8957ab86a..895a27d8e 100644 --- a/Content/Guides/whatsnew/4. Enhancements.htm +++ b/Content/Guides/whatsnew/4. Enhancements.htm @@ -8,7 +8,10 @@

      Enhancements

      If there are no customer-requested enhancements, delete this section, and delete the link from the mini-TOC. Enhancements should have a tracking number; otherwise, they are considered new features.

      Use the optional groups to organize enhancements logically, as it applies to your product (for example, by feature or functionality). Start with General enhancements.

      The following is a list of enhancements implemented in .

      - +

      Documentation license update +

      +

      Added the documentation license to the product documentation. For more information, see documentation license.

      +
      @@ -29,7 +32,7 @@

      Enhancements

      General enhancements
      - +
      diff --git a/Content/Guides/whatsnew/6. Resolved Issues.htm b/Content/Guides/whatsnew/6. Resolved Issues.htm index 0fc83c023..901ef5365 100644 --- a/Content/Guides/whatsnew/6. Resolved Issues.htm +++ b/Content/Guides/whatsnew/6. Resolved Issues.htm @@ -1,5 +1,5 @@  - + diff --git a/Project/TOCs/syslog-ng-ose-guide-admin.fltoc b/Project/TOCs/syslog-ng-ose-guide-admin.fltoc index 77089a7d5..258860ba8 100644 --- a/Project/TOCs/syslog-ng-ose-guide-admin.fltoc +++ b/Project/TOCs/syslog-ng-ose-guide-admin.fltoc @@ -1322,7 +1322,7 @@ - + - + \ No newline at end of file diff --git a/Project/TOCs/syslog-ng-ose-guide-whatsnew.fltoc b/Project/TOCs/syslog-ng-ose-guide-whatsnew.fltoc index bab1e4d96..3bdfc5837 100644 --- a/Project/TOCs/syslog-ng-ose-guide-whatsnew.fltoc +++ b/Project/TOCs/syslog-ng-ose-guide-whatsnew.fltoc @@ -22,11 +22,12 @@ Link="/Content/Guides/syslog-ng-guide-admin/supported-platforms.htm" xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" /> + Link="/Content/Guides/whatsnew/3. New Features.htm" xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" + conditions="CommonConditions_DoNotEdit.NotInThisRelease" + StartSection="false" /> + Link="/Content/Guides/whatsnew/4. Enhancements.htm" xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" /> + Link="/Content/Guides/whatsnew/6. Resolved Issues.htm" xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" + conditions="CommonConditions_DoNotEdit.NotInThisRelease" /> + Link="/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm" xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd"> + + diff --git a/syslog-ng OSE Documentation License.txt b/syslog-ng OSE Documentation License.txt new file mode 100644 index 000000000..3fda4f614 --- /dev/null +++ b/syslog-ng OSE Documentation License.txt @@ -0,0 +1,29 @@ +The syslog-ng Open Source Edition Documentation License + +Copyright 2023 One Identity LLC. + +ALL RIGHTS RESERVED. + +Permission is hereby granted, free of charge, to any person obtaining a copy of these documentation files (the "Documentation"), to use the Documentation subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or portions of the Documentation. Any and all copies of the above copyright and this permission notice contained in the Documentation shall not be removed, obscured, or modified. + +If you modify the Documentation, You must cause any modified files to carry prominent notices stating that You changed the files. + +The Documentation contains trademarks and registered trademarks owned by One Identity and its affiliates. Permission is granted to make and distribute verbatim copies of the Documentation from the official syslog-ng.com site. Modified versions of the Documentation containing One Identity trademarks are permitted exclusively for internal use; however, all external distributions of modified Documentation are prohibited from containing any One Identity trademarks which include syslog-ng, the syslog-ng logo, Balabit, the Balabit logo, One Identity and the One Identity logo. + +No relationship is established as a result of this Documentation license. Any statements that suggest a partnership or other relationship with One Identity and its affiliates are prohibited. + +THE DOCUMENTATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DOCUMENTATION OR THE USE OR OTHER DEALINGS IN THE DOCUMENTATION. + +YOU ACKNOWLEDGE THAT THE DOCUMENTATION YOU ARE DOWNLOADING IS SUBJECT TO THE RESTRICTIONS AND CONTROLS IMPOSED BY UNITED STATES EXPORT REGULATIONS. + +YOU CERTIFY THAT: + +YOU DO NOT INTEND TO USE THE DOCUMENTATION FOR ANY PURPOSE PROHIBITED BY UNITED STATES EXPORT REGULATIONS, INCLUDING, WITHOUT LIMITATION, TERRORISM, CYBER-ATTACKS, CYBER-CRIMES, MONEY-LAUNDERING, INDUSTRIAL ESPIONAGE, OR NUCLEAR, CHEMICAL OR BIOLOGICAL WEAPONS PROLIFERATION. + +YOU ARE NOT LISTED AS A DENIED PARTY ON ANY LIST GOVERNING UNITED STATES EXPORTS. + +YOU ARE NOT A NATIONAL OF ANY COUNTRY THAT IS NOT APPROVED TO RECEIVE A U.S. EXPORT. AS OF 2023, THESE COUNTRIES ARE CUBA, IRAN, NORTH KOREA, SYRIA, BELARUS AND RUSSIA. + +If any of the above applicable conditions are not met or if your certification is inaccurate, this restricted copyright license is immediately terminated. \ No newline at end of file From b92c631d0b9ce297bac30cf830b5049ecf4890f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A1nos=20Barta?= Date: Thu, 25 May 2023 13:49:54 +0200 Subject: [PATCH 4/6] xx updated gitignore from central template repo --- .gitignore | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index d116cb9a9..83837581e 100644 --- a/.gitignore +++ b/.gitignore @@ -13,6 +13,7 @@ /Content/Resources/PageLayouts /Content/Resources/Snippets /Content/Resources/Stylesheets +/Content/Resources/SyntaxHighlighting /Content/Resources/TableStyles /Content/SaaSReleaseNotes /Content/Sources @@ -41,4 +42,5 @@ OneIdentity_TemplateForNewProjects.flprj docadmin.persist docadmin.pkl Thumbs.db* -debug.log \ No newline at end of file +debug.log +.venv From 71f0ac4bbdb3a58309d08b1a676dd755acc36d51 Mon Sep 17 00:00:00 2001 From: JanosBarta-OI <72555198+JanosBarta-OI@users.noreply.github.com> Date: Thu, 25 May 2023 14:02:35 +0200 Subject: [PATCH 5/6] Update Content/Guides/shared/documentation-license.htm Co-authored-by: Ancsur <17409848+Ancsur@users.noreply.github.com> --- Content/Guides/shared/documentation-license.htm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Content/Guides/shared/documentation-license.htm b/Content/Guides/shared/documentation-license.htm index 4297c4c5e..3fdfcee98 100644 --- a/Content/Guides/shared/documentation-license.htm +++ b/Content/Guides/shared/documentation-license.htm @@ -14,7 +14,7 @@

      The -

      The Documentation License

      +

      The Documentation License

      Permission is hereby granted, free of charge, to any person obtaining a copy of these documentation files (the "Documentation"), to use the Documentation subject to the following conditions:

        diff --git a/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm b/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm index f4102fbb7..0f212f8c5 100644 --- a/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm +++ b/Content/Guides/syslog-ng-guide-admin/concepts-licensing.htm @@ -11,6 +11,6 @@

        Product licensing Practically, the code stored under the lib directory of the source code package is under LGPL, the rest is GPL.

        For details about the LGPL and GPL licenses, see GNU Lesser General Public License and GNU General Public License, respectively.

        -

        For clarity, the Documentation is licensed separately. For details, see The Documentation License.

        +

        For clarity, the Documentation is licensed separately. For details, see The Documentation License.

        \ No newline at end of file diff --git a/Content/Guides/syslog-ng-guide-admin/what-syslog-ng-is.htm b/Content/Guides/syslog-ng-guide-admin/what-syslog-ng-is.htm index 0ded5f317..aa424a3d2 100644 --- a/Content/Guides/syslog-ng-guide-admin/what-syslog-ng-is.htm +++ b/Content/Guides/syslog-ng-guide-admin/what-syslog-ng-is.htm @@ -9,7 +9,7 @@

        What syslog-ng is

        Among others, allows you the following.

        Secure and reliable log transfer
        -

        The application enables you to send the log messages of your hosts to remote servers using the latest protocol standards. You can collect and store your log data centrally on dedicated log servers. Transfer log messages using the TCP protocol ensures that no messages are lost.

        +

        The application enables you to send the log messages of your hosts to remote servers using the latest protocol standards. You can collect and store your log data centrally on dedicated log servers. Transfer log messages using the TCP protocol ensures that no messages are lost.

        Disk-based message buffering
        @@ -45,9 +45,9 @@
        SQL, NoSQL, and monitoring

        Storing your log messages in a database allows you to easily search and query the messages and interoperate with log analyzing applications. The syslog-ng application supports the following databases: MongoDB, MSSQL, MySQL, Oracle, PostgreSQL, and SQLite.

        also allows you to extract the information you need from your log data, and directly send it to your Graphite, Redis, or Riemann monitoring system.

        -
        -
        Wide protocol and platform support
        -
        +
        +
        Wide protocol and platform support
        +
        syslog protocol standards

        syslog-ng not only supports legacy BSD syslog (RFC3164) and the enhanced RFC5424 protocols but also JavaScript Object Notation (JSON) and journald message formats.

        diff --git a/Content/Guides/whatsnew/4. Enhancements.htm b/Content/Guides/whatsnew/4. Enhancements.htm index 895a27d8e..b1acf1cf7 100644 --- a/Content/Guides/whatsnew/4. Enhancements.htm +++ b/Content/Guides/whatsnew/4. Enhancements.htm @@ -10,7 +10,7 @@

        Enhancements

        The following is a list of enhancements implemented in .

        Documentation license update

        -

        Added the documentation license to the product documentation. For more information, see documentation license.

        +

        Added the documentation license to the product documentation. For more information, see documentation license.

      [Category] enhancements
      diff --git a/Maketargets.json b/Maketargets.json index 091e764ec..72bfa73df 100644 --- a/Maketargets.json +++ b/Maketargets.json @@ -1,6 +1,6 @@ { "global": { - "product": "syslog-ng Open Source Edition 3.36", + "product": "syslog-ng Open Source Edition 3.38", "productnamelong": "syslog-ng Open Source Edition", "productnameshort": "syslog-ng OSE", "productnameinepic": "syslog-ng-open-source-edition", @@ -8,11 +8,12 @@ "conditions-to-exclude": "General.PE or General.pe6 or General.SPS or General.SRA or General.ARS", "version": "3.38", "techversion": "3.38" + "onlinedocumentation": "https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition" }, "syslog-ng-ose-guide-admin": { "condition": "General.OSE", "doc_id": "syslog-ng-ose-guide-admin", - "doc_setname": "syslog-ng-ose-3.36-guides", + "doc_setname": "syslog-ng-ose-3.38-guides", "title": "Administration Guide", "type": "Administration Guide", "description": "This manual is the primary documentation of the syslog-ng Open Source Edition application" @@ -20,7 +21,7 @@ "syslog-ng-ose-guide-whatsnew": { "condition": "General.OSE", "doc_id": "syslog-ng-ose-guide-whatsnew", - "doc_setname": "syslog-ng-ose-3.36-guides", + "doc_setname": "syslog-ng-ose-3.38-guides", "title": "Release Notes", "type": "Release Notes", "description": "Describes the new features and other highlights of this release of the syslog-ng Open Source Edition application" @@ -28,7 +29,7 @@ "syslog-ng-tutorial-mutual-auth-tls": { "condition": "General.OSE", "doc_id": "syslog-ng-tutorial-mutual-auth-tls", - "doc_setname": "syslog-ng-ose-3.36-guides", + "doc_setname": "syslog-ng-ose-3.38-guides", "title": "Mutual authentication using TLS", "type": "Best Practices", "description": "This tutorial shows you step-by-step how to create the certificates required to authenticate your server and your clients, and how to configure syslog-ng Open Source Edition (syslog-ng OSE) to send your log messages in an encrypted connection"
      General enhancements