java.lang.RuntimeException: Cannot add Tasks to already shutdown executor

[m10x]

Had the following stacktraces for all TLS targets (10+) of a customer

[...] [24/54] Padding oracle probe executed
Killed task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@549cae8b[Cancelled]
Exception in thread "main" java.util.concurrent.CancellationException
        at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:121)
        at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
        at de.rub.nds.scanner.core.execution.ThreadedScanJobExecutor.executeProbesTillNoneCanBeExecuted(ThreadedScanJobExecutor.java:162)
        at de.rub.nds.scanner.core.execution.ThreadedScanJobExecutor.execute(ThreadedScanJobExecutor.java:135)
        at de.rub.nds.scanner.core.execution.Scanner.scan(Scanner.java:188)
        at de.rub.nds.tlsscanner.serverscanner.Main.main(Main.java:45)
Could not scan SessionTickets for version TLS12
java.lang.RuntimeException: Cannot add Tasks to already shutdown executor
        at de.rub.nds.tlsattacker.core.workflow.ParallelExecutor.addTask(ParallelExecutor.java:87)
        at de.rub.nds.tlsattacker.core.workflow.ParallelExecutor.addStateTask(ParallelExecutor.java:108)
        at de.rub.nds.tlsattacker.core.workflow.ParallelExecutor.bulkExecuteStateTasks(ParallelExecutor.java:114)
        at de.rub.nds.tlsscanner.core.probe.TlsProbe.executeState(TlsProbe.java:36)
        at de.rub.nds.tlsscanner.serverscanner.probe.SessionTicketProbe.performInitialConnections(SessionTicketProbe.java:86)
        at de.rub.nds.tlsscanner.serverscanner.probe.SessionTicketProbe.checkVersionChange(SessionTicketProbe.java:129)
        at de.rub.nds.tlsscanner.serverscanner.probe.SessionTicketProbe.executeTest(SessionTicketProbe.java:58)
        at de.rub.nds.scanner.core.probe.ScannerProbe.call(ScannerProbe.java:47)
        at de.rub.nds.scanner.core.probe.ScannerProbe.call(ScannerProbe.java:26)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at java.base/java.lang.Thread.run(Thread.java:1583)
Could not collect SessionTickets for version TLS12k probe, Named groups probe, …
java.lang.RuntimeException: Cannot add Tasks to already shutdown executor
        at de.rub.nds.tlsattacker.core.workflow.ParallelExecutor.addTask(ParallelExecutor.java:87)
        at de.rub.nds.tlsattacker.core.workflow.ParallelExecutor.addStateTask(ParallelExecutor.java:108)
        at de.rub.nds.tlsattacker.core.workflow.ParallelExecutor.bulkExecuteStateTasks(ParallelExecutor.java:114)
        at de.rub.nds.tlsscanner.core.probe.TlsProbe.executeState(TlsProbe.java:36)
        at de.rub.nds.tlsscanner.serverscanner.probe.SessionTicketCollectingProbe.collectTickets(SessionTicketCollectingProbe.java:62)
        at de.rub.nds.tlsscanner.serverscanner.probe.SessionTicketCollectingProbe.executeTest(SessionTicketCollectingProbe.java:36)
        at de.rub.nds.scanner.core.probe.ScannerProbe.call(ScannerProbe.java:47)
        at de.rub.nds.scanner.core.probe.ScannerProbe.call(ScannerProbe.java:26)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at java.base/java.lang.Thread.run(Thread.java:1583)

[m10x]

Is it possible that failing probes get skipped and do not end the scan? This behaviour makes TLS-Scanner pretty unreliable

[XoMEX]

This is likely caused due to a timeout (as the padding oracle probe is rather slow). For now I'd recommend disabling it.

As for the suggestion, yeah, we should do something about that