F-33. A voice reply produced nothing at all: no marker, no event, no error. Four independent gates each dropped it, and fixing any one alone would have changed nothing observable. The mapper reached `map_media` for image, record, file and video alike, but its only emitting branch was gated on the frame being an image, and the `attachment_saved` fallback rejected every other type outright. Both now carry whatever type arrived, with the frame type as the marker's alt text so the renderer knows what to expect before any bytes exist. `pending_media` was also a single slot, so a second attachment in one reply overwrote the first before it was paired; it is a bounded queue now, and an `attachment_saved` with no id no longer consumes the media frame still waiting for one. The download judged a candidate path successful only if the bytes sniffed as an image — this server answers unknown paths with its own text under HTTP 200, so sniffing is load-bearing and cannot simply be dropped. Audio and video signatures are recognised now, and a declared Content-Type is trusted when it names media rather than only images. SILK is included deliberately: it is what AstrBot relays for QQ and WeChat voice, no browser decodes it, and recognising it is what lets the UI say so instead of rendering a player whose play button does nothing. The CSP had no `media-src`, so it fell back to `default-src 'self'` and an `<audio src="blob:">` was refused — in release builds only, since the dev server serves no CSP at all. That is the same divergence as F-04 and the inline-script trap in pet.html, so the policy now has a test of its own that pins each directive the app depends on, including that script-src still refuses inline. The renderer chose `<img>` unconditionally. The element now follows the media type of the bytes that actually arrived, falling back to the marker's declared kind for the placeholder and the failure message. `map_media` also kept a private copy of the message-id handling that included the reopen-suffix overwrite fixed earlier in `adopt_message_id`; it shares the one implementation now. Protocol tests 22 -> 26, Rust client 99 -> 101, frontend 35 -> 43. All six mutations of the new assertions were confirmed to fail. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
60 行
2.3 KiB
TypeScript
60 行
2.3 KiB
TypeScript
import { describe, expect, it } from "vitest";
|
|
|
|
import tauriConfigJson from "../../src-tauri/tauri.conf.json?raw";
|
|
|
|
/**
|
|
* The shipped Content-Security-Policy, asserted directly.
|
|
*
|
|
* Tauri serves this header from its asset resolver, which the Vite dev server
|
|
* bypasses — so a missing directive costs nothing in development and breaks the
|
|
* release build only. That divergence has already produced two defects here
|
|
* (F-04's missing `blob:` for images, and an inline script that would have been
|
|
* refused), so each directive the app depends on is pinned rather than assumed.
|
|
*/
|
|
describe("the shipped content security policy", () => {
|
|
const csp = (
|
|
JSON.parse(tauriConfigJson) as {
|
|
app: { security: { csp: string } };
|
|
}
|
|
).app.security.csp;
|
|
|
|
const directive = (name: string) => {
|
|
const found = csp
|
|
.split(";")
|
|
.map((part) => part.trim())
|
|
.find((part) => part === name || part.startsWith(`${name} `));
|
|
expect(
|
|
found,
|
|
`${name} is absent, so it falls back to default-src`,
|
|
).toBeDefined();
|
|
return found ?? "";
|
|
};
|
|
|
|
it("lets an image attachment render from a blob url", () => {
|
|
expect(directive("img-src")).toContain("blob:");
|
|
});
|
|
|
|
it("lets a voice attachment play from a blob url", () => {
|
|
// Without its own directive, an <audio src="blob:"> falls back to
|
|
// default-src 'self', which has no blob: — so a voice reply downloads
|
|
// successfully and then refuses to play, in release builds only.
|
|
expect(directive("media-src")).toContain("blob:");
|
|
});
|
|
|
|
it("still refuses inline script", () => {
|
|
// tauri-utils only nonces `script[src^='http']`, so inline script cannot be
|
|
// made to work here — the pet window uses a separate entry document instead.
|
|
// Relaxing this would silently reopen that hole.
|
|
expect(directive("script-src")).not.toContain("unsafe-inline");
|
|
expect(directive("script-src")).not.toContain("unsafe-eval");
|
|
});
|
|
|
|
it("does not let the renderer reach arbitrary hosts", () => {
|
|
// An attachment is proxied through Rust and handed over as bytes precisely
|
|
// so the webview never talks to a host the server named.
|
|
expect(directive("default-src")).toBe("default-src 'self'");
|
|
for (const name of ["img-src", "media-src"]) {
|
|
expect(directive(name)).not.toMatch(/\shttps?:\/\/(?!asset\.localhost)/);
|
|
}
|
|
});
|
|
});
|