I collected opportunistic tls data for rdp with sslyze. When I run the analyzer, a TypeError Exception is thrown.
./analyze.py -i ../logs/recon -t sslyze tls
Vulnerabilities and/or deviations from the recommended settings (`/recon/config/recommendations/tls/default.toml`):
Traceback (most recent call last):
File "/recon/./analyze.py", line 150, in <module>
main()
File "/recon/./analyze.py", line 147, in main
process(parser.parse_args())
File "/recon/./analyze.py", line 81, in process
services = analyzer.analyze(files)
^^^^^^^^^^^^^^^^^^^^^^^
File "/recon/analyzers/tls/__init__.py", line 111, in analyze
services = self.parser.parse_files(files[self.parser_name])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/recon/analyzers/__init__.py", line 24, in parse_files
self.parse_file(path)
File "/recon/analyzers/tls/sslyze.py", line 197, in parse_file
self._parse_scan_result(
File "/recon/analyzers/tls/sslyze.py", line 205, in _parse_scan_result
self._parse_certificate_info(
File "/recon/analyzers/tls/sslyze.py", line 301, in _parse_certificate_info
if not certificate_deployment['path_validation_results']['was_validation_successful']:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: list indices must be integers or slices, not str
This is caused by a difference in the collected data at the path_validation_results value, as it contains an array and is not an individual value to be read from. An exempt from the file can be seen below.
Therefore the path_validation_results need an additional step before was_validation_successful can be checked.
To check for further issues i added a single fixed index to the handling and i encountered no further errors during the processing of the data. So this seems to be the only place (at least in my data) where additional steps are required. The block below is only an exempt as it would take some effort to clean identifying data from it.
I collected opportunistic tls data for rdp with sslyze. When I run the analyzer, a TypeError Exception is thrown.
./analyze.py -i ../logs/recon -t sslyze tls
This is caused by a difference in the collected data at the
path_validation_results
value, as it contains an array and is not an individual value to be read from. An exempt from the file can be seen below.Therefore the
path_validation_results
need an additional step beforewas_validation_successful
can be checked.To check for further issues i added a single fixed index to the handling and i encountered no further errors during the processing of the data. So this seems to be the only place (at least in my data) where additional steps are required. The block below is only an exempt as it would take some effort to clean identifying data from it.