ONC import doesn't accept Windows line endings
Reported by
ray.rizz...@gmail.com,
Aug 18 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8350.68.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Platform: 8350.68.0 (Official Build) stable-channel wolf Steps to reproduce the problem: 1. Create a valid ONC file on windows 2. Verify in hex line endings ar 0x0d 0x0a 3. Import the file 4. see that vpn is not created in network, and check chrome_user_log under chrome://system/ for lines like these: [663:663:0817/083207:ERROR:device_event_log_impl.cc(140)] [08:32:07.978] Network: onc_utils.cc:61 Invalid JSON Dictionary: Line: 6, column: 18, Syntax error. [663:663:0817/083207:ERROR:onc_utils.cc(419)] ONC loaded from user import is not a valid JSON dictionary. What is the expected behavior? a new VPN in networking What went wrong? parsing error Did this work before? N/A Chrome version: 52.0.2743.116 Channel: stable OS Version: 8350.68.0 Flash Version: Shockwave Flash 22.0 r0 The ONC import should directly give status feedback. Better yet, there should be a .ovpn import or at least a .ovpn to ONC converter so that a degree in rocket science is not required.
,
Oct 12 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by dhadd...@chromium.org
, Oct 11 2016