New issue
Advanced search Search tips

Issue 669114 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Token generation script does not support IDN

Project Member Reported by arobins@chromium.org, Nov 28 2016

Issue description

The token created for IDN origins is not punycoded. I think that this means the tokens won't be usable on those origins.

./generate_token.py 'https://Ћoogle.com' WebBluetooth
Token details:
 Origin: https://Ћoogle.com:443
 Feature: WebBluetooth
 Expiry: 1483985994 (2017-01-09 18:19:54 UTC)

AuIwE2BMpGu7yTLUicbx21ZfbqC/rnIj1ef9BOj/pGvSeW6Ik0RjM/WbJq1X236BgJnalrv/B+Ox2uad+Z3LIQQAAABVeyJvcmlnaW4iOiJodHRwczovL1x1MDQwYm9vZ2xlLmNvbTo0NDMiLCJmZWF0dXJlIjoiV2ViQmx1ZXRvb3RoIiwiZXhwaXJ5IjoxNDgzOTg1OTk0fQ==

The payload portion of that token is the following:
{"origin":"https://\u040boogle.com:443","feature":"WebBluetooth","expiry":1483985994}

Another case is when the origin doesn't have the scheme. This is what happens:
./generate_token.py 'Ћoogle.com' WebBluetooth
generate_token.py: error: argument origin: Ћoogle.com is not a hostname or a URL
 

Comment 1 by cha...@chromium.org, Mar 31 2017

Owner: ----
Status: Available (was: Untriaged)
Status: WontFix (was: Available)
This should only affect the generation of tokens for test purposes. Any real tokens should be generated by the backend system. If test tokens for IDN origins are needed, this can be addressed at that point (not expected to be too difficult).

Sign in to add a comment