Publication of an llvm-based tool that protects against fault injection attacks

Hello,

My team and I have recently published an LLVM-based tool at “Cryptography and Security
in Computing Systems 2016” (CS2), and we would like to add it on the list of LLVM related publications.
The goal of our tool is to automatically protect the code being compiled against fault injection attacks

*Title:* Compilation of a Countermeasure Against Instruction-Skip Fault Attacks
Available at the ACM Digital Library: http://dl.acm.org/citation.cfm?id=2858931
And also here: http://thiernobarry.fr/publications/preprint/T-Barry.pdf

Abstract:

Done, http://llvm.org/pubs/

cheers,
--renato

Hi,

Well, that's a link to a paywall, and it wouldn't be fair to publish a
link asking people to buy it, when there's a free version available.

We do seem to have other links to ACM, so it wouldn't be a first...
Are you concerned with bandwidth? Or just reference?

--renato

If it’s an ACM DL link, then it has the nice feature of counting downloads in a place that’s useful for aggregate bibliometrics. It’s also the canonical version.

ACM has an ‘authorizer’ service that allows people to put links to publications on their personal sites that check the referrer and allow people past the paywall for a single article. They might be willing to extend this for things like the LLVM publications page. I can ask, if there’s some general interest in supporting this.

David

If it’s an ACM DL link, then it has the nice feature of counting downloads in a place that’s useful for aggregate bibliometrics. It’s also the canonical version.

I know, it's very canonical, but buying for personal use when there is
a free version, especially at $15 each, is a bit cheeky.

ACM has an ‘authorizer’ service that allows people to put links to publications on their personal sites that check the referrer and allow people past the paywall for a single article. They might be willing to extend this for things like the LLVM publications page. I can ask, if there’s some general interest in supporting this.

That'd work. We could easily store the PDFs on our website in those
cases (there aren't many, they aren't that big, or too often
downloaded).

An alternative would be to have two URLs in pubs.js.

cheers,
--renato