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

Implement a subreddit transport #8

Open
GaelTadh opened this issue Jan 14, 2018 · 5 comments
Open

Implement a subreddit transport #8

GaelTadh opened this issue Jan 14, 2018 · 5 comments
Assignees
Labels
backlog Issues that are not planned to be worked on in the near future; considered of low(er/est) priority feature request transport

Comments

@GaelTadh
Copy link

It would be nice to have a subreddit based c2 support. This should avoid the challenges posed by twitter. While still being just as reliable.

@Und3rf10w
Copy link
Owner

I agree, this would likely be a much lower level of effort that Twitter as well. I'll begin researching options

@Und3rf10w Und3rf10w changed the title Sub reddit c2 channel Implement a subreddit transport Jan 15, 2018
@Und3rf10w
Copy link
Owner

Commit 9f0d36b is a working implementation of this using reddit PMs. While this does not fulfill the the specified "subreddit" request, this is a good first proof of concept that demonstrates this is possible and fairly straightforward.

The sample_server-gmail.py script works perfectly for this without modification as intended. To utilize this script, simply modify config.py to have these values:

ENCODER_MODULE = "encoder_b64url"
TRANSPORT_MODULE = "transport_reddit"

You will need to register a reddit app (as a script), install the praw module, then populate the proper values in server/utils/transports/transport_reddit.py and client/reddit/reddit_client.py

Currently, there is a bug that will be encountered if the data being sent is greater than 10k characters in length. I will resolve this, but one can load the stager manually (e.g. from a text file) for debugging purposes and verify that this does in fact work as a transport mechanism. This should be fairly straightforward if we go the route of adding a beginning and ending delimiter between transmissions.

@Und3rf10w
Copy link
Owner

In 4fc3399, renaming sample_server-gmail.py to server.py to signify that it doesn't require any modification.

@Und3rf10w
Copy link
Owner

Moving development tracking of reddit PM transport to #9

@Und3rf10w Und3rf10w added the backlog Issues that are not planned to be worked on in the near future; considered of low(er/est) priority label Jun 7, 2018
@Und3rf10w
Copy link
Owner

Adding to backlog for now, will revisit after beta release, see #23 and Milestone 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Issues that are not planned to be worked on in the near future; considered of low(er/est) priority feature request transport
Projects
None yet
Development

No branches or pull requests

2 participants