-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add PyAFF4 suppport #657
Comments
No releases in https://github.com/aff4/pyaff4 and 2017 release in https://pypi.org/project/PyAFF4/ Let's get this updated first, marking as blocked |
Looks like this is going to be more involved:
|
Potential licensing issues:
|
New release 0.27 in PyPi. Re the observation that the dependency list is going to be more involved, can you elaborate? |
Thx
The thing is that plaso ships a packaged version that includes all dependencies for this reason all dependencies need to be compatible with the plaso license (https://github.com/log2timeline/l2tdocs/blob/master/process/Dependencies.md). Seeing the uncertainty around compatibility of PD and FOSS (some context https://opensource.org/node/878) I would need to take a closer look how this affects plaso. An option might be to make pyaff4 an optional dependency to dfVFS and not ship it as part of the packaged release of plaso. However this means additional steps in the release build process. |
We could make the pyblake2 dependency a soft one - it isn't regularly used. |
In general, the less dependencies the easier to deploy. Maybe an alternative approach is to have a pyaff4(-core) and pyaff4-blake (or equiv) split? |
What is aff4-snappy, a fork from https://github.com/andrix/python-snappy? Under rekall-innovations (https://github.com/rekall-innovations/aff4-snappy)? Asked for clarification: aff4/pyaff4#9 |
To unblock log2timeline/dfvfs#362 add PyAFF4 suppport to l2tdevtools and l2tbinaries/GIFT
https://pypi.org/project/PyAFF4/
https://github.com/aff4/pyaff4
@blschatz FYI
WIP: https://github.com/joachimmetz/l2tdevtools/tree/pyaff4
The text was updated successfully, but these errors were encountered: