Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Unable to start http listener with CertPath option #665

Closed
CustosClarus opened this issue Apr 21, 2023 · 1 comment
Closed

[BUG] Unable to start http listener with CertPath option #665

CustosClarus opened this issue Apr 21, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@CustosClarus
Copy link

CustosClarus commented Apr 21, 2023

Note: Please fill out all sections (if applicable) and do not delete the below section headers, otherwise the bot will close the issue.

Empire Version

  • [Version] 5.0.0-beta2

OS Information (Linux flavor, Python version)

  • OS: kali 6.1.0-kali5-amd64
  • Python: Python 3.11.2

Describe the bug

Using HTTP listener , I cannot run the listener using CertPath argument

To Reproduce

  1. Start powershell-empire server
  2. Start powershell-empire client (Empire: uselistener/http) > set CertPath data/empire-chain.pem
    INFO: Set CertPath to ../empire/server/data/empire-chain.pem
[INFO]: 127.0.0.1:37800 - "POST /api/v2/listeners HTTP/1.1" 400 
[INFO]: v2: Starting listener 'First' 
[ERROR]: First: Listener startup on port 9090 failed: [Errno 2] No such file or directory 
Traceback (most recent call last):
  File "/usr/share/powershell-empire/empire/server/listeners/http.py", line 1235, in start_server
FileNotFoundError: [Errno 2] No such file or directory
[ERROR]: Failed to start listener 'First' 
[INFO]: 127.0.0.1:53352 - "POST /api/v2/listeners HTTP/1.1" 400 
 ##Expected behavior
[*] Active listeners:

  ID    Name              Host                                 Type      Delay/Jitter   KillDate    Redirect Target
  --    ----              ----                                 -------   ------------   --------    ---------------
  1     test              http://192.168.10.3:9090                 native    5/0.0      
     

Screenshots

alt text

Additional info

I have generated the cert using the script located in location
/usr/share/powershell-empire/setup/cert.sh

@CustosClarus CustosClarus added the bug Something isn't working label Apr 21, 2023
@CustosClarus
Copy link
Author

Problem solved you don't need to enter full path with file-name as with earlier version but just using the absolute path of the folder where the .pem file is located be enough.

vinnybod added a commit that referenced this issue Aug 27, 2023
…8374dd70c3dd82847d681282

Cherry-pick 58b97f0 to private-main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant