ci(dev2): keep migration workflow logs private; add encrypted read-only query - #262
Merged
Merged
Conversation
…ly query This repo is public, so its Actions logs are too. inspect listed every Supabase stack on dev2; it now prints only the ThreatCrush database. New query mode runs SQL in a read-only session and prints only ciphertext: the result is AES-encrypted with a fresh key sealed to an RSA public key the caller supplies.
ThreatCrush Security Scan16 finding(s) HIGH/CRITICAL: 1 | MEDIUM: 7 | LOW: 8
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This repo is public, and so are its Actions logs.
inspectno longer lists the other Supabase stacks on dev2. The first version printed every Supabase container name and image on the box. Those runs are deleted. It now prints only the database that holds the ThreatCrush schema.querymode. It runs the given SQL in a read-only session (PGOPTIONS=-c default_transaction_read_only=on). All psql output, errors included, goes to a file on the runner. What gets printed is that file encrypted with AES-256 under a fresh key, plus the key sealed to the RSA public key (pubkeyinput, base64 PEM) with OAEP-SHA256. Decrypt locally with the private key.How verified
I ran the step bodies from the YAML locally against the local Supabase container, with
sshreplaced by a local shell:CREATE TABLEis rejected with "cannot execute CREATE TABLE in a read-only transaction", and no table is created.inspectprints onlysupabase_db_threatcrush.actionlintis clean.