k3170makan / goodork3-dev

The shards of code that will soon become the next GooDork version

GooDork3-dev

The GooDork3 development reposititory, this is a non-operational copy of GooDork3 and the pieces of code that will soon be pull together to create the new version.

As soon as all the Goals for this version of GooDork are met the working copy with be commited to the main GooDork repo.

You guys are welcome to help out ;)

Please see the TODO file for more details on contributing to the code. Before contributing or adding code with the purpose of merging it to the main GooDork repository please read the README.md file in the gooLib directory

Direcory structure: gooData --- external data crucial to operation, e.g User-Agent strings, Server domain lists gooLib --- all scripts crucial to the operation of GooDork besides GooDork.py itself I may adopt this as the folder for goo_xml,goo_html,goo_csv,goo_JOSN,---and generally and other output parsers---,goo_rcfile gooCore --- not in use at the moment, I may adopt this as the folder for goo_operator,goo_config,goo_results and goo_netlib

goodork3-dev's Issues

__repr__ in goo_results

The 'repr' function (in goo_results) is convenient only when printing results in a normal format.

When the result strings are passed to goo_writer it has to parse the information from the Unicode string of each result, which calls for more work.

One way is to remove 'repr' from goo_results, return results as goo_result instances which makes it easier to write to the outfile. However, we need to add an extra function for printing those instances to stdout.

argparse for better argument/switches handling.

This makes the job a lot easier. Especially if you intend to implement custom switches through GooDork scripting engine http://docs.python.org/2/library/argparse.html#module-argparse

pyc to .gitignore

Might want to add .pyc to gitignore

Need to quote regex and dorks.

Regex switches and dorks can cause issues when executing via command line. For eg; the example specified in the usage text doesn't work unless you quote all regex/dorks.

• Bash gives a syntax error if you don't quote regex/dorks.
• You need to quote them within double quotes in Windows command prompt. Single quote works fine in bash.

Should this just be specified in the usage text or do you have anything else in mind?