sec-certs.git/sec_certs/cert_processing.py, branch main Tool for analysis of security certificates (Common Criteria, FIPS 140...). https://git.neuromancer.sk/sec-certs.git/atom/sec_certs/cert_processing.py?h=main 2021-05-13T16:04:54Z delete old API 2021-05-13T16:04:54Z Adam Janovsky 2021-05-13T16:04:54Z urn:sha1:a910f54e314109203f38cea6a36b6ccc57587998 Improves parallel processing function 2021-02-19T16:39:09Z Adam Janovsky 2021-02-19T16:39:09Z urn:sha1:fccf787c1ddca5ffd4095ef1c3cb99f8feb8c78a - Adds option to unpack arguments Rethought way of processing certificates 2020-11-28T11:17:22Z Adam Janovsky 2020-11-28T11:17:22Z urn:sha1:7afc55f371b27894bae930145f4a359d98151d63 - Every certificate now implements a static method for its processing - These are called in parallel - There's some code duplication at the moment, stuff can be simplified. type hinting checks 2020-11-27T13:16:44Z Adam Janovsky 2020-11-27T13:16:44Z urn:sha1:2eeabc1d6d8cff35aff7ade1932596c104eb3d4d move merge_certs() to CCDataset 2020-11-26T14:40:10Z Adam Janovsky 2020-11-26T14:40:10Z urn:sha1:cad8f53ea493cd16f5a4d539d24884b3c8d18213 Finalize proposal of cert download and convert 2020-11-26T12:55:49Z Adam Janovsky 2020-11-26T12:55:49Z urn:sha1:56093596cd176a45bbf210e9e4def967cf3d0141 The proposed method of processing certificates is breadth-first. By that I mean that single task is done for all certificates, then next task is evaluated. All tasks should be implemented as static methods and are to be paralelized by calling `sec-certs/cert_processing.py`. Currently, a generic method `process_paralel()` sits there that is capable of pretty much arbitrary parallel processing (both using threads and processes). Any methods to-be called by this method must require unpacked arguments on the input.