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

Feature request: piped input #1

Closed
richardlehane opened this issue Jan 10, 2016 · 3 comments
Closed

Feature request: piped input #1

richardlehane opened this issue Jan 10, 2016 · 3 comments

Comments

@richardlehane
Copy link

Hi Timothy,
great project! It'd be cool to have another mode of operation where brunnhilde reads a csv piped into STDIN. This would allow you to do something like:

sf -csv directory | python brunnhilde.py

Benefit would be that users could have more control over options passed to sf (like choice of hash, signature file, etc.).

Re. type of reporting: have you seen Ross Spencer's DROID analysis projects https://github.com/exponential-decay/droid-sqlite-analysis ? May give you some ideas as to useful info to report.

cheers
Richard

@tw4l
Copy link
Owner

tw4l commented Jan 12, 2016

Thanks, Richard! I agree, that could be very helpful - I'll look into building out that functionality in the next version.

And thanks also for pointing out Ross' project -- very cool and a great source of ideas.

Tim

@tw4l
Copy link
Owner

tw4l commented Aug 1, 2020

Hi @richardlehane , hope you're doing well! I just released Brunnhilde 1.9.0, which includes a --stdin option that will read a Siegfried CSV from piped stdin (e.g. sf -csv . | brunnhilde.py --stdin . /path/to/output/dir), as well as a --csv option that will take a Siegfried CSV file on disk as input. More details are available in the project README and release notes. Better late than never? 😆

@tw4l tw4l closed this as completed Aug 1, 2020
@richardlehane
Copy link
Author

wow! Thanks Tessa and congrats on the release :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants