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
Added support for Firefox Cookie SQLite schema version 10 #4664 #4665
Added support for Firefox Cookie SQLite schema version 10 #4664 #4665
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #4665 +/- ##
==========================================
+ Coverage 85.81% 85.82% +0.01%
==========================================
Files 412 412
Lines 35476 35483 +7
==========================================
+ Hits 30442 30453 +11
+ Misses 5034 5030 -4
☔ View full report in Codecov by Sentry. |
@@ -175,5 +153,61 @@ def ParseCookieRow(self, parser_mediator, query, row, **unused_kwargs): | |||
|
|||
self._ParseCookie(parser_mediator, cookie_name, cookie_data, url) | |||
|
|||
class FirefoxCookie2Plugin(BaseFirefoxCookiePlugin): | |||
''' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please use """
to keep the codebase consistent
'path, appId, inBrowserElement))')}] | ||
|
||
sqlite.SQLiteParser.RegisterPlugins([FirefoxCookie2Plugin, FirefoxCookie10Plugin]) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove trailing empty lines
Let's also add a unit test for FirefoxCookie10Plugin |
docs linter is flagging a concern, I'll remove the anchor
|
Make some style and linting related changes and tests are passing now. |
One line description of pull request
Firefox cookie table schema has been upgraded to remove baseDomain. Removed baseDomain from the required keys
Description:
fixes #4664
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: