[x3d-public] Encrypted Content

[John Carlson]

Okay, Leonard.  I can support HTTPS in the X3D JSON Loader for loading JSON files, but someone should test it.  I will once I get my HTTPS server running again (it’s in a down virtual box and we’re migrating to a physical server, https://x3d.carlsonsolutiondesign.com.

I assume file:// can go over SFTP if necessary (if there’s no https server). I think node.js is ready to support HTTPS, given a certificate and a key.  Likely it will be a painful transition, but very good for privacy. Hopefully, the hardware will be up to the challenge.

John

Sent from Mail for Windows 10

From: Leonard Daly
Sent: Friday, July 15, 2016 2:13 PM
To: Web3D Consortium; X3D Graphics public mailing list
Subject: [x3d-public] Encrypted Content

There is a very heated discussion going on in the web-vr list concerning the WebVR specification. The browsers companies (at least Google and Mozilla) are considering making this capability require that the content arrived over HTTPS. This seems (to me) to be part of a much larger push to require all content be encrypted.
My point is not to get in a discussion here about the merits of this idea, but to provide preliminary notice that all Web3D content is going to need to support HTTPS at the same Profile, Component/Level as HTTP protocol is supported. It may even be the case that FILE:// won't work or will require a configuration setting change in the browser.

-- 
Leonard Daly
3D Systems & Cloud Consultant
X3D Co-Chair on Sabbatical
LA ACM SIGGRAPH Chair
President, Daly Realism - Creating the Future 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160715/c1cfa9c4/attachment.html>