New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 894634 link

Starred by 2 users
Status: Assigned
Owner:
agl@chromium.org
Cc:
kpaulhamus@chromium.org
viswa.karala@chromium.org
█ piperc@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Security Key V1 Attestation replacement fails

Project Member Reported by piperc@chromium.org, Oct 11 
Chrome Version: 69.0.3497.100 
OS: All

What steps will reproduce the problem?
(1) Try and enroll a V1 security key
(2) Do not allow RP to see make/model of key
(3) Error is returned:
"attestation certificate replacement failed: Error: bad magic number", source: chrome-extension://kmendfapggjehodndflmmgagdbamhnfd/enroller.js (454)

What is the expected result?
Enrollment response is a successful one with the attestation cert replaced.

What happens instead?
An error response is returned.

Comment 1 by viswa.karala@chromium.org, Oct 23

Cc: viswa.karala@chromium.org
Labels: Needs-Triage-M69 Triaged-ET TE-NeedsTriageFromHYD
Thanks for filing the issue!

As per comment# 0 from the reporter issue seems to be related to security key which is not available at ET team, hence routing this issue to Inhouse for further triaging the issue.

Thanks!

Comment 2 by agl@chromium.org, Oct 23

Labels: -TE-NeedsTriageFromHYD -Needs-Triage-M69
(This is in hand. I'm waiting for hardware to arrive.)

Comment 3 by benhenry@google.com, Jan 11

Status: Assigned (was: Unconfirmed)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment