From 63a3547f998bfbe52c2bc8a540e0f33d37f3ad88 Mon Sep 17 00:00:00 2001
From: Ivan Nardi <12729895+IvanNardi@users.noreply.github.com>
Date: Tue, 14 Jan 2025 12:05:03 +0100
Subject: Add (kind of) support for loading a list of JA4C malicious
 fingerprints (#2678)

It might be usefull to be able to match traffic against a list of
suspicious JA4C fingerprints

Use the same code/logic/infrastructure used for JA3C (note that we are
going to remove JA3C...)

See: #2551
---
 fuzz/corpus/fuzz_filecfg_malicious_ja3/1 | 2 --
 1 file changed, 2 deletions(-)
 delete mode 100644 fuzz/corpus/fuzz_filecfg_malicious_ja3/1

(limited to 'fuzz/corpus/fuzz_filecfg_malicious_ja3/1')

diff --git a/fuzz/corpus/fuzz_filecfg_malicious_ja3/1 b/fuzz/corpus/fuzz_filecfg_malicious_ja3/1
deleted file mode 100644
index 6cebd9e6e..000000000
--- a/fuzz/corpus/fuzz_filecfg_malicious_ja3/1
+++ /dev/null
@@ -1,2 +0,0 @@
-# ja3_md5,Firstseen,Lastseen,Listingreason
-b386946a5a44d1ddcc843bc75336dfce,2017-07-14 18:08:15,2019-07-27 20:42:54,Dridex
-- 
cgit v1.2.3