Giters
ciscocsirt
/
netsarlacc
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
38
Watchers:
8
Issues:
41
Forks:
5
ciscocsirt/netsarlacc Issues
Add generic "listen" protocol.
Updated
6 years ago
Add build versioning / version number
Updated
7 years ago
IPv6 support
Updated
7 years ago
Explore making protocol handlers more modular
Updated
7 years ago
Move global configuration vars to a config struct
Updated
7 years ago
Rework socket read() calls to do more than one
Closed
7 years ago
Comments count
1
Possibly record version of TLS negoiated
Updated
7 years ago
Possibily record TLS SNI if the client uses it
Updated
6 years ago
Comments count
2
Look into increasing TCP backlock on listening socket
Updated
7 years ago
Comments count
1
init scripts
Updated
7 years ago
Collapse the starting of the ReadWorkers and normal workers into one start function
Closed
7 years ago
Comments count
1
Move the stopping of the logger into the logger.go file
Closed
7 years ago
Comments count
1
Move the worker stopping code into the dispatcher file
Closed
7 years ago
Comments count
1
Need to audit usage of time for timezone correctness
Closed
7 years ago
Comments count
1
Consider decoupling reading from socket and the parsing, logging of HTTP, and sending responses
Closed
7 years ago
Comments count
1
Moar, better, updated docs, readme, examples
Updated
7 years ago
Factor out template code and try to re-use some work between invocations
Closed
7 years ago
Comments count
2
Get socket handles and then drop privs by passing handles through daemon
Closed
7 years ago
Comments count
1
Code should accept a path via cmdline / config and not assume working in '.'
Closed
7 years ago
Comments count
1
Parameterize and CONSTize many magic values / strings / paths
Closed
7 years ago
Comments count
1
Use advisory locking via flock() on log files
Closed
7 years ago
Comments count
1
Support a configuration file to specify logging dir, ports, and TLS certs
Closed
7 years ago
Comments count
1
Fatal errors should (try to) gracefully shut down sinkhole
Closed
7 years ago
Comments count
1
"Snap" log file names to 10 minute boundaries
Closed
7 years ago
Comments count
1
Get code ready for additional protocols
Closed
7 years ago
Comments count
3
Start using branches
Closed
7 years ago
Comments count
3
Test cases
Updated
7 years ago
Current prints to stdout needs to be cleaned up
Closed
7 years ago
Comments count
2
All logging should be done via a single goroutine
Closed
7 years ago
Comments count
5
Needs a daemon mode for running unattended
Closed
7 years ago
Comments count
2
Worker pool
Closed
7 years ago
Comments count
4
Consider restructuring how logging is done in the worker
Closed
7 years ago
Comments count
1
JSON error output doesn't contain any information about time or client
Closed
7 years ago
Comments count
2
Logging is prepending a timestamp on our JSON output
Closed
7 years ago
Comments count
4
Error reading from connection assumes IO timeout
Closed
7 years ago
Comments count
1
Sinkhole instance name / ID
Closed
7 years ago
Consider migrating from text/template to html/template to prevent XSS
Closed
7 years ago
Comments count
3
Optional headers like User-Agent and Referer end up with empty cells in the error page
Closed
7 years ago
Comments count
1
No TLS support yet
Closed
7 years ago
Comments count
4
Some JSON fields contain sub fields
Closed
7 years ago
Parsing of headers inefficient, includes separating space in value
Closed
7 years ago
Comments count
1