* docs: move link to final CSAF 2.0 in README
* docs: underline that we are _not_ offering an API yet
* Grammar fix
---------
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
* move csaf_searcher to a lower prio place
* Adjust wording
* Grammar fix #2 'this is work in progress' -> 'This is a work in progress'...
---------
Co-authored-by: JanHoefelmeyer <hoefelmeyer.jan@gmail.com>
* Change release action to use elder Ubuntu runner
* use `ubuntu-20.04` so we get binaries that are more
compatible with elder GNU/Linux distribution, because
go binaries link to glibc (for some operating system operations
like dns).
resolve #456
* docs: update main README
* introduce more structure and put commands for users to the top.
* improve description of the command for the 3.0 release.
* Add 'Tools for ...' to make it more readable.
---------
Co-authored-by: Sascha L. Teichmann <sascha.teichmann@intevation.de>
* started with forwarding support in downloader
* Add missing files.
* Add missing files.
* Raise needed Go version
* More Go version bumping.
* Fix forwarding
* Go 1.21+ needed
* Make terminating forwarder more robust.
* Better var naming
* Remove dead code. Improve commentary.
* Prepare validation status adjustment.
* Move validations to functions to make them executable in a loop.
* Introduce validation mode flag (strict, unsafe)
* Add short description for each component in the main README
* Move more Info in separated files.
* Add hint that csaf_provider offers a service interface.
* Explain why windows only has uploader and checker.
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Add "client-cert" and "client-key" flag options to allow the checker to use TLS client certificate for authentication.
* Fix typo TSL -> TLS in docs.
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Add "client-cert" and "client-key" flag options to allow the uploader to use
TLS client certificate for authentication with the provider.
Co-authored-by: Bernhard Reiter <bernhard@intevation.de>
* Add instructions for installing a TLS server certificate on nginx
* Fix link to nginx in README.md
* List all three ways to get a webserver TLS certificate. With some
hints on which to chose for which purpose.
* Do not add CSR instructions, because they can change over time and each CA may
have slightly different requirements.
* Add a hint about setting protocol selection.
* Fix typo in provider-setup.md
* "build_linux": building for GNU/linux
* "build": Building for both linux and windows (cross build)
* Place the generate binaries under "binaries/" directory
* Improve echo messages
