mmetc

Results 131 issues of mmetc

ssh and http brute-force scenarios are not triggered because pfsense already has sshguard with more aggressive defaults (three strikes and a 2 min. ban). We may want a new scenario...

it would be nice to allow the user to register to the console directly from the UI. we have to keep in mind local vs remote lapi

how do we show bouncer logs if possible? the config xml only allows one log file per package, and we choose crowdsec.log

probably embedding symfony/yaml is not a best practice, but pfsense has no php package manager so what's the best way to ensure compatibility with pfsense core and possibly avoid issues...

- fix upload from bats tests - ignore generated code

needs/area
kind/chore

kind/fix
area/local-api

In addition to the method split, I propose to replace the term "soft delete" with "expired". Ideally imho it would be expire/remove instead of soft/hard delete, but it may clash...

needs/area
kind/refactoring

this should keep exactly the same look as the previous version, except for a missing hyphen when wrapping path names (which should have never been there)

kind/enhancement
area/cscli