Track security flags for automatically added initial chat content
Categories
(Core :: Machine Learning: General, task)
Tracking
()
People
(Reporter: simonf, Assigned: simonf)
References
Details
(Whiteboard: [genai][security])
Attachments
(4 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
We currently proactively provide the open tab and - if there are matching ones - memories about the user to the LLM. This requires setting the tracking flags correctly.
Updated•6 months ago
|
Updated•6 months ago
|
Comment 1•6 months ago
|
||
Sets conversation securityProperties (untrusted_input, private_data) when
initial chat content is automatically injected in generatePrompt(). Tab
metadata from content pages (http/https) is treated as untrusted and
private. Internal pages (about:, chrome:) stay clean unless memories or
@mentions are also injected. Flags are monotonic and only set when content
is actually included. Tracking only, no tool gating changes.
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
| Assignee | ||
Comment 2•5 months ago
|
||
Updated•5 months ago
|
| Assignee | ||
Comment 3•5 months ago
|
||
Updated•5 months ago
|
Comment 5•5 months ago
|
||
Backout for causing xpcshell failures at ChatConversation.js
Backout link
Push with failure
Failure log
Failure log for TV
Failure line TEST-UNEXPECTED-FAIL | browser/components/aiwindow/ui/test/xpcshell/test_ChatConversation.js | xpcshell return code: 0
| Assignee | ||
Updated•5 months ago
|
Comment 7•5 months ago
|
||
| bugherder | ||
Comment 8•5 months ago
|
||
[Tracking Requested - why for this release]:
We'll want this for 150 to make sure security stuff for smart window chats works correctly
Updated•5 months ago
|
Comment 10•5 months ago
|
||
| bugherder | ||
Comment 11•5 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D288663
Updated•5 months ago
|
Comment 12•5 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: This is a required security behavior for the Smart Window MVP.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: This risk is lower, as the feature still needs to be turned on.
- String changes made/needed?: None
- Is Android affected?: no
Comment 13•5 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D288860
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Comment 14•5 months ago
|
||
| uplift | ||
Description
•