[logging-log4j2] branch master updated: Add missing license header

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mattsicker pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/master by this push:
     new 1e1dbf0fa0 Add missing license header
1e1dbf0fa0 is described below

commit 1e1dbf0fa0031967bdf5a72ca2c49ec8a546ef36
Author: Matt Sicker <ma...@apache.org>
AuthorDate: Sun Jan 22 16:04:29 2023 -0600

    Add missing license header
    
    Signed-off-by: Matt Sicker <ma...@apache.org>
---
 docs/2.17.0-interpolation.md | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/docs/2.17.0-interpolation.md b/docs/2.17.0-interpolation.md
index 76c496da3f..ae43e0f6e3 100644
--- a/docs/2.17.0-interpolation.md
+++ b/docs/2.17.0-interpolation.md
@@ -1,3 +1,22 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements.  See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership.  The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied.  See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
 I'd like to go into detail on some of the changes in 2.17.0, why they're so important, and how they relate to both [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046) and [CVE-2021-45105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105).
 
 The substitution of untrusted log data allowed access to code that was never meant to be exposed. Lookups should be triggered only by configuration and the logging framework (including custom layout/appender/etc plugins). Not by user-provided inputs.
@@ -153,4 +172,4 @@ The fix in this case is to inline the `fileName` property value into the `Rollin
         </Route>
       </Routes>
     </Routing>
-```
\ No newline at end of file
+```