refactor!: rename project to bot-bottle
Assisted-by: Codex
This commit is contained in:
@@ -35,7 +35,7 @@ which naive encoding a misbehaving agent uses.
|
||||
explicitly does not decode base64 or ROT13 in all inspection paths due
|
||||
to processing overhead concerns.
|
||||
- Rolling this in ~100 lines of Python is feasible and is probably the right
|
||||
path for claude-bottle v1. The limiting factor is not the encoding logic
|
||||
path for bot-bottle v1. The limiting factor is not the encoding logic
|
||||
— that is straightforward — but the false-positive rate from common
|
||||
base64 alphabet collisions and the zero coverage against any re-encoding
|
||||
that involves a key (encryption) or destroys byte boundaries (packet
|
||||
@@ -385,7 +385,7 @@ involves:
|
||||
- Steganography (hiding data in image pixels, audio samples, whitespace),
|
||||
|
||||
...will produce output with no detectable relationship to the input plaintext.
|
||||
For claude-bottle's threat model — an untrusted but not adversarially
|
||||
For bot-bottle's threat model — an untrusted but not adversarially
|
||||
sophisticated agent that might accidentally or naively encode secrets before
|
||||
logging or posting them — naive-encoding detection covers the realistic concern.
|
||||
A deliberately adversarial agent with knowledge of its own monitoring is a
|
||||
@@ -393,9 +393,9 @@ different threat model entirely.
|
||||
|
||||
---
|
||||
|
||||
## Integration point in claude-bottle
|
||||
## Integration point in bot-bottle
|
||||
|
||||
The natural choke point for encoding-aware content inspection in claude-bottle
|
||||
The natural choke point for encoding-aware content inspection in bot-bottle
|
||||
is the body of outbound HTTP/HTTPS requests, visible at the egress proxy layer.
|
||||
The egress-guard note documents smokescreen (Stripe,
|
||||
[github.com/stripe/smokescreen](https://github.com/stripe/smokescreen))
|
||||
@@ -450,7 +450,7 @@ and pre-computable. The following techniques defeat it entirely:
|
||||
intercepted by an HTTP proxy at all. The egress-guard note covers DNS
|
||||
separately via a controlled resolver.
|
||||
|
||||
In the claude-bottle context, the primary realistic concern is an agent
|
||||
In the bot-bottle context, the primary realistic concern is an agent
|
||||
that naively embeds a secret in a log line, a curl argument, a JSON body,
|
||||
or a shell heredoc without specifically intending to obfuscate. All of the
|
||||
above bypass techniques require deliberate, adversarially-motivated engineering
|
||||
|
||||
Reference in New Issue
Block a user