Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

NASA guy to White House: Be really careful with that HTTPS stuff

What's wrong with a 'waiver process'?

A webserver and database administrator at NASA has penned an epic plea on the White House's GitHub repository to include a waiver process as part of the HTTPS-Only project, which is intended to improve security for citizens visiting federal websites, but may interfere with niche services.

Joe Hourclé has taken to GitHub to criticise the HTTPS-Only website's claims that "there is no such thing as insensitive web traffic".

"Yet there is," writes Hourclé. "Due to many institutions having policies against FTP and peer-to-peer protocols, HTTP has become the de facto standard in sharing scientific data."

Restricting the use of HTTP may affect a number of scientific analysis tools, according to Hourclé, although whether these would be included in the HTTPS-Only roll-out is not clear.

The webserver admin states he has seen "nothing that would indicate [there will be exemptions to this policy] and my complaint is specifically because I think that there should be a waiver process".

Hourclé's main gripe is "top-down solutions" that "they try to force down our throats when they don't actually understand what our needs are. I've seen it happen in both government and when I worked for a university, where someone convinces higher-up management to buy services/products from their company, and it's a waste, just a hole to pour money into".

Mandating the deprecation of HTTP could be disruptive for host security too, Hourclé claims, as HTTPS provides an increased attack surface and frequent improper implementation could decrease the availability of the service for the user and increase the security risk for those maintaining the server.

Additionally, Hourclé warns of the effect the policy may have on those without computers at home, as many public institutions which offer internet access are mandated to filter it by state or local laws and may block HTTPS entirely.

Following calls of support from the ACLU and Mozilla, and its implementation by Netflix, the secure hypertext transfer protocol looks as if it may eventually be standard across the web, even if plain-old HTTP still has use cases alongside it.

The Register was unable to contact NASA as of publication. ®

Similar topics

TIP US OFF

Send us news


Other stories you might like