Skip to content

Convert chromeLoginData to LAVA (per-browser tables)#732

Merged
abrignoni merged 1 commit into
mainfrom
lava-chrome-logindata
Jun 19, 2026
Merged

Convert chromeLoginData to LAVA (per-browser tables)#732
abrignoni merged 1 commit into
mainfrom
lava-chrome-logindata

Conversation

@abrignoni

Copy link
Copy Markdown
Owner

Continues the Chrome-family conversion with the per-browser pattern (#729#731).

For each browser found, generates a per-browser HTML report and a per-browser LAVA table (<Browser> - Login Data), then returns a combined dataset with a trailing Browser Name column.

  • The SQL query and the PBKDF2/AES password decryption are unchanged.
  • The original baked browser_name into every row; it's now added at the combine step, so each per-browser table doesn't carry a redundant Browser column (consistent with the other Chrome conversions).
  • Created Time marked as datetime; output standard.

Verified: parses, lint-clean, plugin loader resolves with no warnings. (No login-data test rows in available extractions; the per-browser pattern itself was behaviorally confirmed on a Samsung extraction in #729/#730.)

Apply the multi-browser pattern: per-browser HTML report and per-browser LAVA
table for every browser found, with a combined dataset returning a trailing
'Browser Name' column. The query and the password decryption (PBKDF2/AES) are
unchanged; browser_name, which the original baked into each row, is now added at
the combine step so the per-browser tables don't carry a redundant Browser
column. Created Time marked as datetime; output "standard". Function key dropped.
@abrignoni abrignoni merged commit e5a7c88 into main Jun 19, 2026
1 check passed
@abrignoni abrignoni deleted the lava-chrome-logindata branch June 19, 2026 01:51
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

Successfully merging this pull request may close these issues.

1 participant