elreydetoda / docker-bashfuscator Goto Github PK

View Code? Open in Web Editor NEW

3.0 3.0 1.0 6 KB

dockerizing this project: https://github.com/Bashfuscator/Bashfuscator

Dockerfile 7.33% Shell 92.67%

docker-bashfuscator's People

Contributors

Stargazers

Watchers

Forkers

jonathanzhou348

docker-bashfuscator's Issues

finish parser

docker-bashfuscator/docker-entrypoint.sh

Lines 18 to 23 in 5a53ccf

 # TODO: finish parser 

 # body: write a parser to interpret where commands being and end. Here are a few things to consider. 

 # parse **Program Options** [here](https://github.com/elreydetoda/docker-bashfuscator/blob/master/bashfuscator_options.md) which are necessary to the function of the program.  

 # - these will tell you what you will be reading in from for the obfuscation 

 parse(){ 

 # this function is to parse bashfuscation arguments, because docker

This issue was generated by todo based on a `TODO` comment in `5a53ccf`. It's been assigned to @elreydetoda because they committed the code.

Implement reading from stdin

docker-bashfuscator/docker-entrypoint.sh

Lines 23 to 28 in ebd0943

 # TODO: Implement reading from stdin 

 # body: Need to work on trying to check for the parser function if input 

 # can be read from stdin from a docker container, I am thinking yes if 

 # someone does `-- <(file_path)` at the end of running a container, but 

 # need to validate this later down the road.

This issue was generated by todo based on a `TODO` comment in `ebd0943`. It's been assigned to @elreydetoda because they committed the code.

Create parser for bashfuscator in docker

This would have been extremely easy if docker didn't strip " from cli pass arguments. So, since docker strips that character, I need to do the following

#3
parse commands (blocked by #3) /read in file (blocked by #2) /stdin (blocked by #1)
#4

output command to stdout

docker-bashfuscator/docker-entrypoint.sh

Lines 80 to 85 in 5a53ccf

 # TODO: output command to stdout 

 # body: always append `--output -` to the end of a command so it is outputted to stdout and the user can append `-- | clipcopy` or `xclip` or whatever their clipboard manager is (i.e. `clip.exe` for windows or `pbcopy` for osx) so it get's copied to their clipboard. 

 # - the `--` at the end of the command will allow docker to realize that there are no more args getting passed to it. (i.e. `docker container run --rm -it bashfuscator -- | less` 

 # "${bin_path}/bashfuscator" "$@" 

 ;; 

 esac

This issue was generated by todo based on a `TODO` comment in `5a53ccf`. It's been assigned to @elreydetoda because they committed the code.

use bind mount to access file

docker-bashfuscator/docker-entrypoint.sh

Lines 29 to 34 in 6d9eedb

 # TODO: use bind mount to access file 

 # body: use the `-v` option to bind mount a file to be allowed to be read 

 # by bashfuscator, so that way the file can be accessed from within the 

 # docker container. Throw error if not mounted 

 parsed_string=()

elreydetoda / docker-bashfuscator Goto Github PK

docker-bashfuscator's People

Contributors

Stargazers

Watchers

Forkers

docker-bashfuscator's Issues

finish parser

This issue was generated by todo based on a `TODO` comment in `5a53ccf`. It's been assigned to @elreydetoda because they committed the code.

Implement reading from stdin

This issue was generated by todo based on a `TODO` comment in `ebd0943`. It's been assigned to @elreydetoda because they committed the code.

Create parser for bashfuscator in docker

output command to stdout

This issue was generated by todo based on a `TODO` comment in `5a53ccf`. It's been assigned to @elreydetoda because they committed the code.

use bind mount to access file

This issue was generated by todo based on a `TODO` comment in `6d9eedb`. It's been assigned to @elreydetoda because they committed the code.

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	# TODO: finish parser
	# body: write a parser to interpret where commands being and end. Here are a few things to consider.
	# parse Program Options [here](https://github.com/elreydetoda/docker-bashfuscator/blob/master/bashfuscator_options.md) which are necessary to the function of the program.
	# - these will tell you what you will be reading in from for the obfuscation
	parse(){
	# this function is to parse bashfuscation arguments, because docker

	# TODO: Implement reading from stdin
	# body: Need to work on trying to check for the parser function if input
	# can be read from stdin from a docker container, I am thinking yes if
	# someone does `-- <(file_path)` at the end of running a container, but
	# need to validate this later down the road.

	# TODO: output command to stdout
	# body: always append `--output -` to the end of a command so it is outputted to stdout and the user can append `-- \| clipcopy` or `xclip` or whatever their clipboard manager is (i.e. `clip.exe` for windows or `pbcopy` for osx) so it get's copied to their clipboard.
	# - the `--` at the end of the command will allow docker to realize that there are no more args getting passed to it. (i.e. `docker container run --rm -it bashfuscator -- \| less`
	# "${bin_path}/bashfuscator" "$@"
	;;
	esac

	# TODO: use bind mount to access file
	# body: use the `-v` option to bind mount a file to be allowed to be read
	# by bashfuscator, so that way the file can be accessed from within the
	# docker container. Throw error if not mounted

	parsed_string=()

elreydetoda / docker-bashfuscator Goto Github PK

docker-bashfuscator's People

Contributors

Stargazers

Watchers

Forkers

docker-bashfuscator's Issues

This issue was generated by todo based on a TODO comment in 5a53ccf. It's been assigned to @elreydetoda because they committed the code.

This issue was generated by todo based on a TODO comment in ebd0943. It's been assigned to @elreydetoda because they committed the code.

This issue was generated by todo based on a TODO comment in 5a53ccf. It's been assigned to @elreydetoda because they committed the code.

This issue was generated by todo based on a TODO comment in 6d9eedb. It's been assigned to @elreydetoda because they committed the code.

Recommend Projects

Recommend Topics

Recommend Org

This issue was generated by todo based on a `TODO` comment in `5a53ccf`. It's been assigned to @elreydetoda because they committed the code.

This issue was generated by todo based on a `TODO` comment in `ebd0943`. It's been assigned to @elreydetoda because they committed the code.

This issue was generated by todo based on a `TODO` comment in `5a53ccf`. It's been assigned to @elreydetoda because they committed the code.

This issue was generated by todo based on a `TODO` comment in `6d9eedb`. It's been assigned to @elreydetoda because they committed the code.