Add parser for iOS Discord and SQLite parser for iOS Instagram #4968
+593
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One line description of pull request
Add parser for iOS Discord and SQLite parser for iOS Instagram
Description:
I add and modify several files:
Add import
ios_discord
toplaso/parsers/__init__.py
Add a new parser
ios_discord.py
toplaso/parsers/
Add unit test
ios_discord.py
totests/parsers/
Add formatter support for iOS Discord parser to
plaso/data/formatters/ios.yaml
Add timeliner support for iOS Discord parser to
plaso/data/timeliner.yaml
Add
23AAD8D4-D632-4F99-8E44-152AAB8FA9D6
file for iOS Discord parsers totest_data/
Add import
ios_instagram
toplaso/parsers/sqlite_plugins/__init__.py
Add a new parser plugin
ios_instagram.py
toplaso/parsers/sqlite_plugins/
Add unit test
ios_instagram.py
totests/parsers/sqlite_plugins/
Add formatter support for iOS Instagram parser plugin to
plaso/data/formatters/ios.yaml
Add timeliner support for iOS Instagram parser plugin to
plaso/data/timeliner.yaml
Add
9368974384.db
files for iOS Instagram parser plugin totest_data/
Related issue (if applicable): fixes #
Notes:
All contributions to Plaso undergo code review.
This makes sure that the code has appropriate test coverage and conforms to the
Plaso style guide.
One of the maintainers will examine your code, and may request changes. Check off the items below in
order, and then a maintainer will review your code.
Checklist: