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

terminal returned a "[conf]: alive" after run the c2shell #78

Closed
jashfjsad opened this issue Apr 16, 2021 · 3 comments
Closed

terminal returned a "[conf]: alive" after run the c2shell #78

jashfjsad opened this issue Apr 16, 2021 · 3 comments

Comments

@jashfjsad
Copy link

after i run the shell generated by gencrossc2.linux(2.2.1),the terminal appeard a"[conf]: alive"like below.
alive

env:
cobaltstrike 4.2
ubuntu 18.04

@gloxec
Copy link
Owner

gloxec commented May 10, 2021

This prompt is to confirm that the beacon can successfully communicate with the teamserver server network. The reason for this is that there is no prompt in the earlier version, but it cannot be started in some environments, and some information needs to be returned to confirm the failure reason.

@gloxec
Copy link
Owner

gloxec commented May 10, 2021

If it is to replace some native programs of the system to act as a rootkit, the prompt message here is indeed too disturbing.
In the next version, consider adding a parameter option for generating silence or writing error messages to files in other locations.

@gloxec gloxec added the New label May 10, 2021
@gloxec
Copy link
Owner

gloxec commented Aug 17, 2021

The v2.2.5 version that has been pushed has removed the default prompt, and it will prompt for information unless the environment variable is set to debug modeexport CC_DEBUG=1 ; ./beacon.

@gloxec gloxec added the Fixed label Aug 21, 2021
@gloxec gloxec closed this as completed Aug 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants