qsecure-labs / overlord

Overlord - Red Teaming Infrastructure Automation
https://blog.qsecure.com.cy/posts/overlord/
MIT License
615 stars 74 forks source link

Using LetsEncrypt module causes 'create' command to fail #9

Closed c4ch3c4d3 closed 1 year ago

c4ch3c4d3 commented 3 years ago

Describe the bug When using the LetsEncrypt module, terraform script creation fails

To Reproduce Steps to reproduce the behavior:

  1. usemodule LetsEncrypt
  2. set required variables (domain_name)
  3. add to campaign
  4. create
  5. Receive error 'EXCEPTION of type 'UnboundLocalError' occurred with message: 'local variable 'output' referenced before assignment'

Expected behavior File creation as normal.

Screenshots overlord error

It seems the debug true variable also no longer exists?

Desktop (please complete the following information):

Sikkis commented 3 years ago

Thank you for submitting an issue, we will investigate it.

Sikkis commented 3 years ago

Hello c4ch3c4d3, I have confirmed the bug. I will investigate the issue further. From a quick look, it seems that the Lets Encrypt module does not correctly handle the name of the redirector module. For now, use the redirectors inside the C2 module until the issue is fixed.

The 'debug' variable is inherited from the cmd2 package. Its the default throw error message for verbose errors.

c4ch3c4d3 commented 3 years ago

Sounds good. I’m still getting a handle on how the C2 default redirector works, I guess there’s no time like the present to figure it out! Thank you for taking a look!

On Apr 24, 2021, at 12:19 PM, S1kk1S @.***> wrote:

 Hello c4ch3c4d3, I have confirmed the bug. I will investigate the issue further. From a quick look, it seems that the Lets Encrypt module does not correctly handle the name of the redirector module. For now, use the redirectors inside the C2 module until the issue is fixed.

The 'debug' variable is inherited from the cmd2 package. Its the default throw error message for verbose errors.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.