HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
skochinsky
papers
Security & Privacy2016–2016
skochinsky / papers

papers

My presentations and papers

2Distinct people
2Mentions
0Explicit recommenders
47GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

My presentations and papers

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2016-02-05 19:16:04 UTC to 2016-06-16 06:31:29 UTC. Weeks start Monday, UTC.

012016-02-01 00:00:00 UTC to 2016-02-08 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 12016-02-08 00:00:00 UTC to 2016-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-15 00:00:00 UTC to 2016-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-22 00:00:00 UTC to 2016-02-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-29 00:00:00 UTC to 2016-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-07 00:00:00 UTC to 2016-03-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-14 00:00:00 UTC to 2016-03-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-21 00:00:00 UTC to 2016-03-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-28 00:00:00 UTC to 2016-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-04 00:00:00 UTC to 2016-04-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 42016-04-11 00:00:00 UTC to 2016-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-18 00:00:00 UTC to 2016-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-25 00:00:00 UTC to 2016-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-02 00:00:00 UTC to 2016-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-09 00:00:00 UTC to 2016-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-16 00:00:00 UTC to 2016-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-23 00:00:00 UTC to 2016-05-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-30 00:00:00 UTC to 2016-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-06 00:00:00 UTC to 2016-06-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-13 00:00:00 UTC to 2016-06-20 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 13

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 12016-02-01 00:00:00 UTC2016-02-08 00:00:00 UTC101
Feb 82016-02-08 00:00:00 UTC2016-02-15 00:00:00 UTC000
Feb 152016-02-15 00:00:00 UTC2016-02-22 00:00:00 UTC000
Feb 222016-02-22 00:00:00 UTC2016-02-29 00:00:00 UTC000
Feb 292016-02-29 00:00:00 UTC2016-03-07 00:00:00 UTC000
Mar 72016-03-07 00:00:00 UTC2016-03-14 00:00:00 UTC000
Mar 142016-03-14 00:00:00 UTC2016-03-21 00:00:00 UTC000
Mar 212016-03-21 00:00:00 UTC2016-03-28 00:00:00 UTC000
Mar 282016-03-28 00:00:00 UTC2016-04-04 00:00:00 UTC000
Apr 42016-04-04 00:00:00 UTC2016-04-11 00:00:00 UTC000
Apr 112016-04-11 00:00:00 UTC2016-04-18 00:00:00 UTC000
Apr 182016-04-18 00:00:00 UTC2016-04-25 00:00:00 UTC000
Apr 252016-04-25 00:00:00 UTC2016-05-02 00:00:00 UTC000
May 22016-05-02 00:00:00 UTC2016-05-09 00:00:00 UTC000
May 92016-05-09 00:00:00 UTC2016-05-16 00:00:00 UTC000
May 162016-05-16 00:00:00 UTC2016-05-23 00:00:00 UTC000
May 232016-05-23 00:00:00 UTC2016-05-30 00:00:00 UTC000
May 302016-05-30 00:00:00 UTC2016-06-06 00:00:00 UTC000
Jun 62016-06-06 00:00:00 UTC2016-06-13 00:00:00 UTC000
Jun 132016-06-13 00:00:00 UTC2016-06-20 00:00:00 UTC101

What Hacker News says

2 sources
Igor Skochinsky (of IDA Hex-Rays fame, among others) has been studying Intel ME for quite some time. He gave a nice talk at Breakpoint summarizing what he'd discovered (slides here [pdf]: https://github.com/skochinsky/papers/blob/master/2014-10%20%...). Among other things, he finds that ME is capable of running signed Java code which is pushed to the device. Due to the complexity and size of the Java code, it's quite likely to have bugs. ME is a bit scary partly because it's a totally closed-source and proprietary component of your computer with full and essentially unfettered access to everything - RAM, peripherals, and network I/O. Any bug in a publicly-accessible component would have the potential to do serious damage. For example, a bug in the network stack might make it possible for attackers to remotely own your box.
In The Intel ME subsystem can take over your machine, can't be audited

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.