support custom config dir

[dogancanbakir]

Proposed changes

This PR fixes custom config dir support -same functionality as nuclei. Closes #323 .

Checklist

• Pull request is created against the dev branch
• All checks passed (lint, unit/integration/regression tests etc.) with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[Mzack9999]

Implementation: lgtm

suggesting a minor aesthetic change to remove panic from internals on sporadic config file read error

[Mzack9999]

I'm getting this error (test folder doesn't exist):

$ go run . -config test
...
[INF] Current proxify version 0.0.11 (latest)
[FTL] failed to load open test/cakey.pem while saving private key got open test/cakey.pem: no such file or directory
exit status 1

I think we need O_CREATE|O_TRUNC also in

proxify/pkg/certs/mitm.go

Line 61 in 5d6cda1

kf, err := os.OpenFile(keyFile, os.O_WRONLY, 0600)

or just use os.Create(...)

[dogancanbakir]

@Mzack9999 Fixed in #340

[Mzack9999]

lgtm!

[ehsandeep]

to overwrite config dir, we should use a dedicated and separate option like in nuclei as this conflicts with -config option, which is generally used to specify the custom tool config file across all the tools.

we can make changes to make sure these cases are covered.

./proxify -config test/custom_config.yaml
./proxify -config-directory custom_dir_to_store_config_files

   -cdir, -config-directory string      directory to store/read proxify cert/config files ($HOME/.config/proxify)