Update extended_install.md to fix syntax error of the `gpg --edit-key` command.

[Danrancan]

Originally there was a Syntax Error in the "To trust the CRS project's public key:" section, where the command gpg --edit-key was misspelled as gpg edit-key. We fixed this by making the final syntax gpg --edit-key.

Before:

gpg edit-key 
----------------------------------------

After:
----------------------------------------
changed to:
```bash
gpg --edit-key
---------------------------------------

[Danrancan]

Thanks for your contribution!

You are welcome. I would like to get more involved somehow. I'm very good at writing tutorials and documentation as I do on my website https://www.danran.rocks. I'm actually wondering if you might need extra help with editing current documentation, or possibly helping in new documentation for Coraza WAF, if that is still a future WAF for CRS. Not sure where to start, but I have time, and writing/editing skills. Let me know if you need a hand with anything.

Danran

[dune73]

Thank you for you offer @Danrancan. The tutorials linked on the front page of your website return a 403 right now (unless that's the CRS FP problem discussed elsewhere).

Your contribution would be most interesting. There is a lot of stuff to write actually and I am sure also Coraza needs support (even if it is more complementary in a different use case than a replacement for ModSecurity). I suggest you join the #coreruleset channel on the OWASP slack. Invitation from https://owasp.org/slack/invite

[Danrancan]

Thank you for you offer @Danrancan. The tutorials linked on the front page of your website return a 403 right now (unless that's the CRS FP problem discussed elsewhere).

Your contribution would be most interesting. There is a lot of stuff to write actually and I am sure also Coraza needs support (even if it is more complementary in a different use case than a replacement for ModSecurity). I suggest you join the #coreruleset channel on the OWASP slack. Invitation from https://owasp.org/slack/invite

Oh wow, yes this indeed being caused from the crs4 problem I am having. Let me revert to crs3.4 again which I know is working and ping you with a message on here so you can take a look at it. I'll let ya know.

Glad to hear there is work out there in writing. I will definitely join the slack! Thanks for all of the info! Talk soon!

[Danrancan]

Thank you for you offer @Danrancan. The tutorials linked on the front page of your website return a 403 right now (unless that's the CRS FP problem discussed elsewhere).

Your contribution would be most interesting. There is a lot of stuff to write actually and I am sure also Coraza needs support (even if it is more complementary in a different use case than a replacement for ModSecurity). I suggest you join the #coreruleset channel on the OWASP slack. Invitation from https://owasp.org/slack/invite

Ping! Ping! I am now using my crs3.4 rules so the site https://danran.rocks is now working if you want to check it out. Thanks again.

[dune73]

In fact no. 403.

My IP : 213.55.188.89

[Danrancan]

In fact no. 403.

My IP : 213.55.188.89

Wait, do you mean "no 403" as in you are not getting the error? Or do you mean you are getting the 404 still and you are giving me your IP so I can whitelist it? I'm confused. Try clearing your cache if you are still getting it because it's working for me using multiple IP address with a vpn.

Let me know. Thanks.

[dune73]

I'm getting a status code number 403 and in case you want to investigate my request, my IP is 213.55.188.89.

[fzipi]

Hey @Danrancan! Thanks for your offering again. You can find us in the slack provided above by Christian. And if you want to extend your offer for Coraza, you can find that group at the '#coraza' channel in the same OWASP Slack. The website and documentation for that project is in https://github.com/corazawaf/coraza.io