HTTP status code 451 : Hackathon Overview and Human Rights - - PowerPoint PPT Presentation

http status code 451 hackathon overview and human rights
SMART_READER_LITE
LIVE PREVIEW

HTTP status code 451 : Hackathon Overview and Human Rights - - PowerPoint PPT Presentation

HTTP status code 451 : Hackathon Overview and Human Rights Considerations Outline Last weekends hackathon overview Best New Work Introduction to HTTP 451 status code Hackathon implementations Implementation Report


slide-1
SLIDE 1

HTTP status code 451 : Hackathon Overview and Human Rights Considerations

slide-2
SLIDE 2

Outline

  • Last weekend’s hackathon overview

○ Best New Work

  • Introduction to HTTP 451 status code
  • Hackathon implementations
  • Implementation Report Draft
  • HRC RFC7725 Draft
  • Future Plans
  • Discussion
slide-3
SLIDE 3

Hackathon overview

slide-4
SLIDE 4

Team

Sunil Abraham Maria Paz Canales Daniel Kahn Gillmor Joseph Lorenzo Hall Olga Khrustaleva Daniel Ramsey Christine Runnegar Shivan Kaul Sahib Niels ten Oever Alp Toker Codarren Velvindron Loganaden Velvindron + others

slide-5
SLIDE 5

Brief introduction to HTTP 451

slide-6
SLIDE 6

HTTP 451

  • Access to resource denied because of legal demand
  • Blocking server might not be origin server
  • Response should include details of legal demand
slide-7
SLIDE 7

Purpose

  • Making Internet censorship more transparent
  • Reporting and tracking censorship easier
  • Previously used status code 403 was not applicable
slide-8
SLIDE 8
slide-9
SLIDE 9

Hackathon implementations

slide-10
SLIDE 10

Implementations

  • JavaScript Crawler

○ Node-based web crawler ○ Recognizes 451 status, reports to collector

  • WordPress Plugin

○ Plugin for WordPress CMS ○ Allows a site operator to block content using 451 for specific countries & context

  • Block Collector

○ Reporting endpoint ○ Accepts 451 status reports from crawlers, browser plugin, and wp-plugin

  • Browser Plugin

○ Chrome-based plugin (portable) ○ Recognizes 451 status, displays info, report to collector

  • Python Crawler

○ Desktop app ○ Records status, 451 or otherwise

slide-11
SLIDE 11

Screenshots: JavaScript Crawler

slide-12
SLIDE 12

Screenshot: WordPress plugin

slide-13
SLIDE 13

Screenshot: Block Collector

slide-14
SLIDE 14

Screenshot: Browser Plugin

slide-15
SLIDE 15

Screenshot: Python Crawler

slide-16
SLIDE 16

Implementation Report Draft

slide-17
SLIDE 17

Implementation Report

  • Stakeholders concerned with HTTP status code 451
  • Current usage
  • Potential impact
  • Useful features of a reporting mechanism
  • Current features of 451 and suggestions
  • Case studies of blocking frameworks in different countries

○ Russia, Chile, India, Iran, USA

slide-18
SLIDE 18

HRC RFC 7725 Draft

slide-19
SLIDE 19

Human rights considerations for protocols

Anonymity Accessibility Localization Reliability Confidentiality Integrity Authenticity Adaptability Outcome transparency Connectivity Visibility in a browser Privacy Content Agnosticism Security Internationalization Censorship Resistance Open Standards Heterogeneity Support

slide-20
SLIDE 20

Biggest HRC concerns

  • Privacy?
  • Anonymity?
  • Censorship resistance?
  • Security?
  • Reliability?
slide-21
SLIDE 21

Future Plans

slide-22
SLIDE 22

Future Plans

  • Submit implementation report draft
  • Findings
  • RFC7725bis

○ HRC component

slide-23
SLIDE 23

Links

  • Implementation Report draft

○ https://datatracker.ietf.org/doc/draft-451-imp-report/

  • HRC RFC 7725 draft

○ https://tools.ietf.org/html/draft-manyfolks-hrcrfc7725-00

  • GitHub repository for hackathon

○ https://github.com/451hackathon/

slide-24
SLIDE 24

Discussion