Update README.md

Remove outdated and confusing statements about AVM's TLS library. Reword some minor things.

For the technically inclined folks, Fritz!OS 7.19/7.20 now supports TLS 1.3 and X25519 (yeah).

README.md

@@ -10,16 +10,14 @@ If the solution by AVM is not for you, then maybe this software is. This softwar
 This program does not aid in creating these certificates - thus, this software is only suitable for professional users that can issue and manage web-certificates.
 
 # Compatibility and technical notes
-This program utilizes functionality available in the webinterface of Fritz!OS. Versions 7 and higher have this feature accessible under "Internet -> releases -> Fritz!Box services -> certificate" (note: translated from german version, GUI menu may differ in international version). At this menu point, any user can upload custom (RSA) certificates.
+This program utilizes functionality available in the webinterface of Fritz!OS. Versions 7 and higher have this feature accessible under "Internet -> releases -> Fritz!Box services -> certificate" (note: translated from german version, GUI menu may differ in international version). At this menu point, any user can upload custom (RSA) certificates. The TLS implementation of Fritz!OS at this point only supports *RSA* certificates. Other keytypes, like ECDSA, are currently unsupported.
 
 ### Wait: If there's already GUI functionality that does this, what is this program for?
 -> That's the point. Only Fritz!Box products have this menu. Repeaters, powerline, etc products from AVM do *not* have this menu. However, the *functionality is just hidden, it is indeed present in almost all devices running Fritz!OS with a web gui*.
-This software works with these products, even though the menu is hidden. Thus, this program is the only option to access the feature. In conclusion, this software works with most *Fritz!Box, Fritz!WLAN and Fritz!Powerline products* (tested only with devices running Fritz!OS 7 and higher).
+This software works with these products, even though the menu is hidden. Thus, an external program is the only option to access the feature. In conclusion, this software works with most *Fritz!Box, Fritz!WLAN and Fritz!Powerline products* (tested only with devices running Fritz!OS 7 and higher).
 
 # Compatibility and technical notes (continued)
-The TLS implementation of Fritz!OS at this point only supports *RSA* certificates. All other cert-types are unsupported (both in client & server mode), even though the implementation supports ECDHE handshakes (with P256). RSA verified keylengths are 2048 bits and higher (tested up to 4096). Also, if we're listing technical details: At the moment, only TLS 1.2 and below is supported. This will likely change in future releases of Fritz!OS 7.
-
-Fritz!OS remembers if a custom certificate has been uploaded and disables the (re-)generation of self-signed certificates if one is present. Fritz!OS supports password protected .pem files, this tool supports only unprotected pem files at the moment. Both certificate and private key must be in the same file, encoded in standard PEM format with header-guards (=== BEGIN ... === etc).
+Fritz!OS remembers if a custom certificate has been uploaded and disables the (re-)generation of self-signed certificates if one is present. Fritz!OS supports password protected .pem files, but this tool supports only unprotected pem files at the moment. Both certificate and private key must be in the same file, encoded in standard PEM format with header-guards (=== BEGIN ... === etc).
 
 # Usage
 `java -jar <jarfile> <filepath> <domain> [username] <password>`
@@ -47,3 +45,5 @@ https://build.germancoding.com/job/FritzCerts/lastSuccessfulBuild/artifact/targe
 The program is not fully finished at the moment. There's no pretty status printing yet, instead full HTML pages are printed to the console. Additionally, password protected files should be supported and some other improvements are planed too.
 
 This software copies code from [FritzLED](https://github.com/GermanCoding/FritzLED).
+
+Neither this program nor the author(s) are affiliated with AVM. The name of this program may change in the future.