Subj : RE: preventing brute force attempts on privleged ports
To   : bugz
From : NuSkooler
Date : Mon Apr 12 2021 09:00 pm


On Saturday, April 10th bugz said...
 Bu> Unfortunately, fail2ban doesn't parse json logs.  Doesn't look like  are 
 Bu> going to be adding that anytime/if ever.  You're stuck using regex to 
 Bu> parse the logs.  Ugh!  https://xkcd.com/1171/

You can always use jq or such in your pipeline as well, or even 'bunyan' (the tool to accompany Bunyan style/JSON logs)


-- 
|08 ■ |12NuSkooler |06// |12Xibalba |08- |07"|06The place of fear|07"
|08 ■ |03xibalba|08.|03l33t|08.|03codes |08(|0344510|08/|03telnet|08, |0344511|08/|03ssh|08)
|08 ■ |03ENiGMA 1/2 WHQ |08| |03Phenom |08| |0367 |08| |03iMPURE |08| |03ACiDic
--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 14.15.4)
 * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

.