VS Code's sign-in keeps its place; recordings checked for secrets
CI / test (push) Successful in 9m14s
CI / test (push) Successful in 9m14s
From review. - /profile asked before signing in keeps its query for ten minutes, and the sign-in (password or OIDC) returns to it: VS Code's sign-in state came back lost, and the confirmation came every time. Only /profile is ever returned to. - The extension keeps an https gateway at https when a link names it by plain http (a proxy ending TLS unannounced), so the key is never sent in the clear. The install command says --force, since dev builds share a version and VS Code kept the old one. - Every frame of every install recording is checked for a key, a password or a private key, not only the page. - The admin API document again matches the API: f94d902's MCPServerRequest.clear was not in it. - CHANGELOG for this round's fixes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
258591b3f2
commit
ecf5545a7a
11 files changed
+133
-6
No files matched your search
@@ -121,3 +121,10 @@ test('errorMessage says what to do about a refused key', () => {
|
||||
assert.match(lib.errorMessage(429, '{"error":{"message":"rate limit"}}'), /rate limit/);
|
||||
assert.match(lib.errorMessage(500, 'boom'), /500: boom/);
|
||||
});
|
||||
|
||||
test('a link to the same gateway by plain http is a downgrade', () => {
|
||||
assert.equal(lib.downgrades('https://llm.example.com', 'http://llm.example.com'), true);
|
||||
assert.equal(lib.downgrades('https://llm.example.com', 'https://llm.example.com'), false);
|
||||
assert.equal(lib.downgrades('http://llm.example.com', 'https://llm.example.com'), false);
|
||||
assert.equal(lib.downgrades('https://a.example.com', 'http://b.example.com'), false);
|
||||
});
|
||||
Reference in new issue
Block a user