I would like to be able to read my Chrome cookies on a Mac.

My understanding is that I can use HTTP::Cookies::Chrome to do this. The following is an example script I pulled from the git repository and modified it for my Chrome profile.

When I run it I get the attached failure messages with no other output. Any help or pointers are much appreciated.

Thanks

Craig

Script:

#!/opt/homebrew/bin/perl
use v5.10;
use strict;
use warnings;

use Mojo::Util qw(dumper);

use HTTP::Cookies::Chrome;

my $class    = 'HTTP::Cookies::Chrome';
#my $path     = $class->guess_path;
my $path     = '/Users/cmv/Library/Application Support/Google/Chrome/P
+rofile 1/Cookies';
my $password = $class->guess_password;

say <<~"HERE";
    File: $path
    Pass: $password
    HERE

my $cookies = HTTP::Cookies::Chrome->new(
    chrome_safe_storage_password => $password,
    ignore_discard => 0,
    );
$cookies->load( $path );

$cookies->scan( \&summary );

sub summary {
    state $previous_domain = '';
    my( @cookie ) = @_;
    say $cookie[4] unless $cookie[4] eq $previous_domain;
    $previous_domain = $cookie[4];
    printf "\t%-5s %-16s %s\n", map { $_ // '' } @cookie[3,1,2];
    }
[download]

Errors:

As many of you know nowadays I'm not programming for my work since years. In the not so recent past I've made some stuff for my pure pleasure or just to help a bit here.

The programming communtiy did not cried for this :)

At work I suffered a fistfull of company mergeS and now I'm relegated to boring tasks as boring can be to renew SSL certificates.

Our IT world runs as a mad without a precise destination and strange things happens, as it happened that CA/Browser Forum decided to reduce SSL certificate duration in this way:

• after March 15 2026: validity reduced to 200 days
• after March 15 2027: validity reduced to 100 days
• after March 15 2029: validity reduced to 47 days <--- O_O

For sure bosses will complain with: "hey, we have a Dev Dpt here" ..but they act at geological times, and if they insist I can at least propose to setup a demo or better the core functionality we'd like to have distilled into a Perl module (a group of..). This point is important.

I cant let this small chance to fade out, so I must be prepared ( dormitare de fuga cogitante vetat ).

Nowadays Macaroni Group uses Digicert for almost all SSL certificates. They have some APIs for their CertCentral (the new, shiny, fancy, fashion web interface). I asked to tech support if they have also a SandBox environment (money is involved) and they didnt even know the term.. :(

So here I'm, after this long rant, to ask you how to plan my strategy in the right way.

• A base module to use automation-api let say Digicert::Automation. Maybe there is the need to have a base module for the general API: service-apis Ideally this module should be public even if I already fear the testing part.
• A serie of other modules using the above, private to the company I work for, to manage: customers, contacts, mail, orders info e renewals etc.
• a small DB to record customers, their certificates, contact informations, internal contact.. I'd like to keep this as small as possible, ideally an SQLite one.
• a CLI tool to inspect orders, renew certificates etc.. using the above modules and DB.
• ?? a web interface? I'd skip this part, but it depends how bosses see it.
• a cron job to run daily using the above CLI to monitor orders and automatically renew expiring ones.

What I'd like from your part at the moment are: suggestion on the big picture, its design implementation, on hoW to start coding the base module, previous experience in this.. and whatever you think is important to take in count.

Hopefully this is the first of many request on the matter.

L*