Update documents: README, LICENSE, SECURITY, CREDITS, RELEASE NOTES

Update contributor list:
git log --format="%aN" d6464e2272327d146b694af0d6dbdc5eb353deb5..HEAD | sort

Add some release notes (for a full list, see git commits):
git log --format=oneline c35b346bddf083973689f60af48a94c9614aac1c..HEAD

CREDITS.md

@@ -3,9 +3,11 @@
 * Abhishek Lekshmanan
 * Abramo Bagnara
 * Adam Bailey
+* Adam Hunyadi
 * Alan Somers
 * Alberto Bignotti
 * Alex Kozlov
+* Alexander Kozhinov
 * AndreyArsov
 * Anton Te
 * beaver
@@ -44,11 +46,11 @@
 * duong2179
 * ehlertjd
 * Elan P. Kugelmass
-* eugene
 * Eric Tsau
 * Erick Vieyra
 * Erik Beran
 * Erik Partridge
+* eugene
 * extergnoto
 * F-Secure Corporation
 * Fabrice Fontaine
@@ -101,6 +103,7 @@
 * Kevin Wojniak
 * Khem Raj
 * Kimmo Mustonen
+* krpano
 * Krzysztof Kozlowski
 * Lammert Bies
 * Lars Immisch
@@ -140,10 +143,12 @@
 * Peter Foerster
 * Philipp Friedenberger
 * Philipp Hasper
+* Pieter Cardoen
 * Piotr Zierhoffer
 * pkvamme
 * Ponnuvel Palaniyappan
 * qinch
+* qinchao
 * Radoslaw Zarzynski
 * Red54
 * Retallack Mark mark.retallack
@@ -175,6 +180,7 @@
 * Thomas Davis
 * Thomas Klausner
 * Thorsten Horstmann
+* Tim Gates
 * tnoho
 * Tom Deblauwe
 * Tomas Andrle

LICENSE.md

@@ -11,7 +11,7 @@ Civetweb License
 
 ### Included with all features.
 
-> Copyright (c) 2013-2020 The CivetWeb developers ([CREDITS.md](https://github.com/civetweb/civetweb/blob/master/CREDITS.md))
+> Copyright (c) 2013-2021 The CivetWeb developers ([CREDITS.md](https://github.com/civetweb/civetweb/blob/master/CREDITS.md))
 >
 > Copyright (c) 2004-2013 Sergey Lyubka
 >
@@ -45,7 +45,7 @@ Lua License
 
 http://www.lua.org/license.html
 
-> Copyright (C) 1994-2015 Lua.org, PUC-Rio.
+> Copyright (C) 1994-2020 Lua.org, PUC-Rio.
 >
 > Permission is hereby granted, free of charge, to any person obtaining a copy
 > of this software and associated documentation files (the "Software"), to deal
@@ -120,7 +120,7 @@ Lua File System License
 
 https://github.com/keplerproject/luafilesystem/blob/master/LICENSE
 
-> Copyright © 2003-2014 Kepler Project.
+> Copyright © 2003-2020 Kepler Project.
 >
 > Permission is hereby granted, free of charge, to any person
 > obtaining a copy of this software and associated documentation

README.md

@@ -170,7 +170,7 @@ Some guidelines can be found in [docs/Contribution.md](https://github.com/civetw
 
 CivetWeb has been forked from the last MIT version of Mongoose in 2013.
 Since then, CivetWeb has seen many improvements from various authors
-(Copyright (c) 2013-2020 the CivetWeb developers, MIT license).
+(Copyright (c) 2013-2021 the CivetWeb developers, MIT license).
 
 A list of authors can be found in [CREDITS.md](https://github.com/civetweb/civetweb/blob/master/CREDITS.md).
 

RELEASE_NOTES.md

@@ -5,6 +5,12 @@ Release Notes v1.14 (under construction)
 Changes
 -------
 
+- Improve documentation
+- Fix HTTP range requests
+- All some functions for Lua scripts/LSP
+- Build system specific fixes (CMake, MinGW)
+- Update 3rd party components (Lua, lfs, sqlite)
+- Allow Lua background scripts to use timers
 - Update version number
 
 

SECURITY.md

@@ -2,10 +2,10 @@
 
 ## Supported Versions
 
-The current "head" version undergoes some automatic tests, but may have defects and vulnerabilities of any kind.
-Also development branches may be in an intermediate, untested state.
+The current "head" version ("master" branch) undergoes some automatic tests, but may have defects and vulnerabilities.
+All development branches may be in an intermediate, untested state.
 
-For released versions, manual tests are performed in addition to automatic tests and static source code analysis.
+For released versions, additional tests are performed, including manual tests, static source code analysis and fuzz testing.
 
 Defects will be fixed in the current head version. 
 Selected, critical defects are fixed in the latest release as well.
@@ -13,3 +13,8 @@ Selected, critical defects are fixed in the latest release as well.
 ## Reporting a Vulnerability
 
 Please send vulnerability reports by email to bel2125 at gmail com.
+Vulnerability with low severity can be sent directly by email.
+
+For high severity vulnerabilities, you can get a private key to encrypt your detailed description on vulnerabilities you want to report. 
+
+If you do not get any response within ten days, your email might have got lost (e.g., deleted as spam) - in this case, please open a GitHub issue.