http://qs1969.pair.com?node_id=11148433

Discipulus has asked for the wisdom of the Perl Monks concerning the following question:

Hello,

inspired by Using LWP (or some other module) to Dowload HTML with Cookie Session ID I tried to unlock the cookies case of Firefox using perl. I have installed DBD::SQLite but the following code fails to open the DB even if Firefox is closed or if try the readonly flag.

I also tried to make a copy of the DB cookiesTEST.sqlite in the case some lock was there.. but nothing but failures.

use strict; use warnings; use Data::Dumper; use DBI; use DBD::SQLite; my $db = $ENV{AppData}.'\Mozilla\Firefox\Profiles\nwk2oixj.default-rel +ease\cookiesTEST.sqlite'; die "DB file not found!" unless -e $db; print "sqlite DBD version: $DBD::SQLite::sqlite_version\n"; my $dbh = DBI->connect(qq(dbi:SQLite:dbname=$db,'','',{ sqlite_open_flags => SQLITE_OPEN_READONLY, PrintError => 1, RaiseError => 1, })) or die $DBI::errstr; my $sth = $dbh->prepare(q(SELECT * FROM moz_cookies )); print Dumper $sth->fetchall_arrayref({}); __END__ sqlite DBD version: 3.39.4 DBI connect('dbname=C:\Users\ME\AppData\Roaming\Mozilla\Firefox\Profil +es\nwk2oixj.default-release\cookiesTEST.sqlite,'','',{ sqlite_open_flags => SQLITE_OPEN_REA +DONLY, PrintError => 1, RaiseError => 1, }','',...) failed: unable to open dat +abase file at firefox-cookies.pl line 11. unable to open database file at firefox-cookies.pl line 11.

With FF open both DBeaver and sqlite3 command line utility can access the DB without problem. DBeaver uses jdbc:sqlite driver and sqlite> .version shows SQLite 3.40.0 2022-11-16 12:10:08 so not the 3.39.4 shown by DBD.

I have no sqlite in the path.

Searching I found HTTP::Cookies::Mozilla and I installed it: it comes with a stringy documentation ( yes! adopt it ;) but, lurking in /examples I have found /examples/convert-to-mojo.pl that slightly modified to work on windows (around line 19 my @cookies_files = glob(     $ENV{AppData}.'\Mozilla\Firefox\Profiles\*\cookies.sqlite'); ) accesses the db without any issue.

The module documentation ( scan method not even mentioned ;) says explicitly:

> .. so you will need to have either DBI/DBD::SQLite, or the sqlite3 executable somewhere in the path.

Since I have not sqlite in the path, it should use the very same driver used by my failing script, ie: DBD::SQLite

So why the above code fails?

L*

PS ..and now crack the Chrome cookies jar

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.