-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Unable to run caldera.py #48
Comments
Check your python version. You need 3.5+ . Check out the installation instructions here https://caldera.readthedocs.io/en/latest/installation.html |
my mistake I had python 3 and 2 both installed and accidentally ran with 2. I am getting a new error now. File "C:\Users\John\AppData\Local\Programs\Python\Python37\lib\site-packages\p |
@mgraf2 what version of mongodb and pymongo are you using? |
pymongo 3.5.1, and mongodb version 4.0. |
I was able to get past that with a lower version of mongodb, but now I am getting the following error: C:\Users\John\Desktop\caldera-master 2\caldera>C:\Users\John\AppData\Local\Progr The above exception was the direct cause of the following exception: Traceback (most recent call last): |
@mgraf2 Would you mind trying this with Python 3.6? I know I said 3.5+ earlier, but I'd like to rule out python version as the cause here. |
I can try that, I am now seeing this I think I am closer. What config file do I add this to? INFO:app.server:No SSL certificate or key found. Generating a self-signed SSL c |
I finally got it to work, thank you for all your help! |
In Running the commandline specified in the logging output should generate the needed pem files However, I think newer versions of openssl might throw an error at that line because it's missing a newly required agument. If that happens you can run |
@mgraf2 nice! Did you wind up switching to Python 3.6? |
Yes I wound up switching to python 3.6, also didn't realize when running caldera.py it was asking for pem password which is printed to the cmd prompt but it gets hidden by a bunch of other stuff thats printed out; probably should have it wait for user to input pem password before continuing. I kept hitting enter without realizing it was asking for pem password and then it would exit with the error code. Can we expect other adversaries to be added to Caldera in a future update or is the user expected to add these on their own? |
I'm trying to run caldera on a centos, all dependencies installed and python3.6, getting the first error
Any tip to get this solved and running? |
I switched to Mongodb 3.0.1, and that seemed to do the trick. |
@mgraf2 has the solution. We're currently working on MongoDB 4.0 support |
Oh, so that's it...i will try, thank you guys :D |
@dm-mitre want to be clear I must use MongodB3.6 not 4.0 as it's not supported yet. It looks the only download on Mongodb site is 4.0 though |
Download here, i think I used 3.5. |
3.01 rather |
Thanks
Eric G Steinberg
[/Users/EricSteinberg/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_1032003613]<http://www.mantix4.com/>
Mobile 303.667.4045 | Main 877.Mantix4 | www.Mantix4.com
373 Inverness Parkway | Suite 110 | Englewood, CO 80112
Visit us on:
[/Users/EricSteinberg/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_436522414] [/Users/EricSteinberg/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_2010376743] [/Users/EricSteinberg/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_463368248]
[/Users/EricSteinberg/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_78801424][/Users/EricSteinberg/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_861511575]
This E-mail message is covered by the Privacy Act 18 U.S.C. 2510-2521 the information contained in this E-mail message is personal and confidential and is intended for a specific individual (s) and purpose and therefore is protected from disclosure under the Gramm-Leach-Bliley H.R. 3723 on October 11, 1996, which has protected this document as a confidential and trade secret. If you are not the intended recipient of this communication, or the employee or agent responsible for delivering this message to the intended recipient, you are NOT authorized to read, print, retain, copy or otherwise disseminate this communication and are advised that any such dissemination, distribution or copy of this communication, or acting on the information contained herein, may be a violation of applicable law and is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return e-mail and delete all copies of this communication.
From: mgraf2 <notifications@github.com>
Reply-To: mitre/caldera <reply@reply.github.com>
Date: Friday, July 20, 2018 at 6:55 PM
To: mitre/caldera <caldera@noreply.github.com>
Cc: Eric Steinberg <Eric.Steinberg@mantix4.com>, Comment <comment@noreply.github.com>
Subject: Re: [mitre/caldera] Unable to run caldera.py (#48)
Download here, i think I used 3.5.
https://www.mongodb.org/dl/win32/x86_64-2008plus-ssl?_ga=2.51450720.857413503.1532134468-1839883456.1532134468
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#48 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AlD5K5l-4GHVpYb8_Hm1Bo1-sqeU57xpks5uInwBgaJpZM4VEe_M>.
|
@mgraf2 @ericgatm4 @w0rk3r We pushed some updates to support MongoDB 4.0 and also a docker-compose script which should make installation and running much easier. Let us know if you have any problems. |
@dm-mitre
|
@stevenbrz , I've updated the version of mongoengine pinned in requirements.txt . I believe this will fix the error you received above running under Python 3.7. |
* Add files via upload * Update wifi.ps1 * Update 297 Abilities * Delete wifi.ps1
I am getting the following error:
Traceback (most recent call last):
File "caldera.py", line 16, in
from app import server
File "C:\Users\John\Desktop\caldera-master 2\caldera\app\server.py", line 136
async def heartbeat_init():
^
The text was updated successfully, but these errors were encountered: