Konstantin Weddige

If the increase in the term makes this check undesirable, I would be also happy about an optional plugin (not included in `--regular`) to perform this check.

Yes, with the following change, the issue is detected: ```diff $ git diff diff --git a/sslyze/plugins/robot/_robot_tester.py b/sslyze/plugins/robot/_robot_tester.py index 784ef20..48e68a3 100644 --- a/sslyze/plugins/robot/_robot_tester.py +++ b/sslyze/plugins/robot/_robot_tester.py @@ -183,7 +183,7 @@ def test_robot(server_info:...

> @weddige Would you be able to email me the server, so I can troubleshoot this? Did you get my email or do you need any more information?

eTLS does not need to be implemented in the browser. From the point of view of the browser eTLS is 100% compatible to TLS 1.3. But I agree with you...

> and is snake oil eTLS (or ETS by now) is not snake oil, but pure poison. That's why I want to recognize it in the scan.

> The only way to actually detect is the way and how it uses the key exchange. A detection via behaviour would be of course ideal. However, eTLS is (in...

Unfortunately (or fortunately) I do not know of any. I would also rather expect it in an intranet and therefore not accessible from the internet. But so far I haven't...

Without knowing, if this leads to other issues: Not setting `/Author (Ben Tester, Max Muster)` if `` is set, solves the problem: 

After playing around, I think I understand the behaviour of Adobe Reader: If both `/Author` and `` are defined, it shows * `/Author` * `[1:]`. This is independent of the...

What are the current challenges for this feature? Did K-9 5.800 change the approach to solve this?