test/integration-config.yml was deleted from next today as an unused fixture (#134), but it has been in the public history since commit 86b533d (2025-07-22) and carries an S3 access_key_id and secret_access_key for the bucket vaultik-integration-test on http://ber1app1.local:3900/. Deleting the file does not remove the key from history, and nothing in this repo can tell whether it is still valid.
Only you can act on this: if that key still exists on the storage server at ber1app1, revoke it. The endpoint is a LAN-only name, so exposure is limited to someone already on that network. Recommendation: revoke the key and leave history alone; rewriting history is not worth it for a LAN test bucket.
Acceptable: the key is confirmed revoked or already gone, and this issue is closed.
model: claude-fable-5-1
`test/integration-config.yml` was deleted from `next` today as an unused fixture (https://git.eeqj.de/sneak/vaultik/pulls/134), but it has been in the public history since commit `86b533d` (2025-07-22) and carries an S3 `access_key_id` and `secret_access_key` for the bucket `vaultik-integration-test` on `http://ber1app1.local:3900/`. Deleting the file does not remove the key from history, and nothing in this repo can tell whether it is still valid.
Only you can act on this: if that key still exists on the storage server at `ber1app1`, revoke it. The endpoint is a LAN-only name, so exposure is limited to someone already on that network. Recommendation: revoke the key and leave history alone; rewriting history is not worth it for a LAN test bucket.
Acceptable: the key is confirmed revoked or already gone, and this issue is closed.
model: claude-fable-5-1
sneak
was assigned by clawbot2026-09-21 19:25:41 +02:00
A second key pair, different from the one above: the commented S3 block in config.example.yml on main and next holds a key-shaped access key id and secret for a private endpoint, plus an internal rclone remote name. #172 replaces them with placeholders; whether that key is live, and revoking it if so, is yours. Same recommendation: revoke, no history rewrite.
model: claude-fable-5-1
A second key pair, different from the one above: the commented S3 block in `config.example.yml` on `main` and `next` holds a key-shaped access key id and secret for a private endpoint, plus an internal rclone remote name. https://git.eeqj.de/sneak/vaultik/issues/172 replaces them with placeholders; whether that key is live, and revoking it if so, is yours. Same recommendation: revoke, no history rewrite.
model: claude-fable-5-1
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
test/integration-config.ymlwas deleted fromnexttoday as an unused fixture (#134), but it has been in the public history since commit86b533d(2025-07-22) and carries an S3access_key_idandsecret_access_keyfor the bucketvaultik-integration-testonhttp://ber1app1.local:3900/. Deleting the file does not remove the key from history, and nothing in this repo can tell whether it is still valid.Only you can act on this: if that key still exists on the storage server at
ber1app1, revoke it. The endpoint is a LAN-only name, so exposure is limited to someone already on that network. Recommendation: revoke the key and leave history alone; rewriting history is not worth it for a LAN test bucket.Acceptable: the key is confirmed revoked or already gone, and this issue is closed.
model: claude-fable-5-1
clawbot referenced this issue2026-09-21 19:42:23 +02:00
A second key pair, different from the one above: the commented S3 block in
config.example.ymlonmainandnextholds a key-shaped access key id and secret for a private endpoint, plus an internal rclone remote name. #172 replaces them with placeholders; whether that key is live, and revoking it if so, is yours. Same recommendation: revoke, no history rewrite.model: claude-fable-5-1
all of this is useless test credentials on lan IPs, ignore the security implications as there are none.