[benjamin-di]

Summary

The Docker image installs a managed Chromium policy that turns off the password manager and address and card autofill, so the login viewer's browser no longer offers to save the LinkedIn password into the profile. The README and Docker Hub guide explain this and advise skipping the passkey option, which cannot reach the container.

The policy contains exactly those three settings and applies to every browser launch in the image. The viewer's launch flags and passkey behavior are unchanged.

Part of #1403.

Verification

• Rebased onto main 8c3bb5ab572c, head b434c3205ed1. Contribution patches are unchanged.
• Full suite: 8,505 passed, 109 failed and 896 skipped. Both rebased branches have identical failing test identities. A selected rerun of all 109 on exact upstream also fails all 109; no candidate-only failure was found. This is not a full-green result or a second full upstream suite.
• Ruff lint/format, architecture generation, policy traces, strict public scan and whitespace checks pass. Whole-repository type checking reports the identical 389 diagnostics on both candidates and upstream after checkout-path normalization.
• The Docker policy assertions pass; no new detector measurements or repeat save-password UI observation was performed.
• No Docker image build, native host/browser qualification or live LinkedIn check was performed for this rebase. Earlier detector measurements remain historical evidence with their stated scope.

Synthetic prompt

Install a managed Chromium policy in the Docker image that turns off the password manager and address and card autofill, and nothing else. Pin its contents with a test and document the measured kiosk and wider-policy results as not adopted.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The policy affects browser launches within the Docker image, across login and server workflows.

The required detector measurements for the shipped policy must be completed before merging.

Findings

1.  Shipped policy lacks required measurements ▶

Fix with agent prompt

### Issue 1
scripts/chromium-policy.json:2-4
The image installs this three-setting browser policy, but the recorded detector results cover an older, wider policy. `docs/browser-fingerprint.md` explicitly says this subset was not measured on its own.

`AGENTS.md` requires measurements against the four detectors for launch-configuration changes. Measure this exact policy and record the results before merging to satisfy that requirement.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The Docker image adds a managed browser policy that disables password saving and address and card autofill.

• Docker browsers stop offering password saving and address or card autofill.

Both earlier, unnumbered findings are addressed: the redundant kiosk test is gone, and the stale measurement paragraph now links to the dated comparison.

_{Reviews (14) · Last reviewed commit: "fix(docker): Keep only the password and ..." · Reviewed by Greptile}

[benjamin-di]

Completed the native amd64 four-detector comparison, with three cold launches each of upstream, policy only, kiosk only and combined. Kiosk raises CreepJS's like-headless score 44% → 50% via the fullscreen heuristic; lies remain zero, and all fpscanner/rebrowser outcomes are unchanged. Existing warnings, unavailable WebGPU signals, offline CSP limits and raw JA4 variation are documented. The policy loading control and all teardown checks passed. Arm64 remains unmeasured. This commit only adds evidence to the documentation.

[benjamin-di]

Could you grant an exception to the required attribution footer and check-bot-coauthors for this PR and #1383? I cannot supply the required footer. The code, regression tests and validation results remain available in the PR descriptions.

[greptile-apps]

Shipped policy lacks required measurements

The image installs this three-setting browser policy, but the recorded detector results cover an older, wider policy. docs/browser-fingerprint.md explicitly says this subset was not measured on its own.

AGENTS.md requires measurements against the four detectors for launch-configuration changes. Measure this exact policy and record the results before merging to satisfy that requirement.

Context Used: AGENTS.md (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: scripts/chromium-policy.json
Line: 2-4

Comment:
**Shipped policy lacks required measurements**

The image installs this three-setting browser policy, but the recorded detector results cover an older, wider policy. `docs/browser-fingerprint.md` explicitly says this subset was not measured on its own.

`AGENTS.md` requires measurements against the four detectors for launch-configuration changes. Measure this exact policy and record the results before merging to satisfy that requirement.

**Context Used:** AGENTS.md ([source](https://github.com/stickerdaniel/linkedin-mcp-server/blob/main/AGENTS.md))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!