This post is a work-in-progress. This paragraph will be removed when it is completed.
This post is mostly for my own benefit. It will track the redesign of process_vuxml.pl which follows on from How FreshPorts processes vuxml entries. In that previous post, defects were identified and a proposed change put forth. In this post, I’ll document how I intend to proceed.
Temp table
I’m going to create a temp table, consisting of:
- vid
- hash (I will also refer to that as a checksum)
The data from security/vuxml/vuln.xml will be imported into that table.
freshports.dvl=# \d vuxml_import
Table "public.vuxml_import"
Column | Type | Collation | Nullable | Default
----------+------+-----------+----------+---------
vid | text | | not null |
checksum | text | | not null |
Indexes:
"vuxml_import_vid" PRIMARY KEY, btree (vid)
freshports.dvl=#
It took me most of an hour to get to this point. First, I had to grant access to from this laptop to the database server via port 5432 (pf firewall rules). Second, I had to modify the PostgreSQL pg_hba.conf rules to all this laptop to connect. Both of those items involved Ansible configuration changes.
