187 lines
4.5 KiB
TeX
Executable File
187 lines
4.5 KiB
TeX
Executable File
\documentclass[10pt,conference,twocolumn,final,a4paper]{IEEEtran}
|
|
|
|
\usepackage{ifluatex}
|
|
\ifluatex
|
|
\usepackage{fontspec}
|
|
\defaultfontfeatures{Ligatures=TeX} % To support LaTeX quoting style
|
|
%\setromanfont{Vollkorn}
|
|
\else
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage[utf8]{inputenc}
|
|
\fi
|
|
|
|
\usepackage{clrscode}
|
|
\usepackage{xcolor}
|
|
\usepackage[]{graphicx}
|
|
|
|
\usepackage{acronym}
|
|
|
|
\newcommand{\documenttitle}{Here be dragons}
|
|
|
|
\newcommand{\abstracttext}{Abstract goes here}
|
|
|
|
% set pdf metadata
|
|
\usepackage[
|
|
pdftitle={\documenttitle},
|
|
pdfauthor={Oliver Schmidt},
|
|
breaklinks
|
|
]{hyperref}
|
|
%\usepackage{breakurl}
|
|
|
|
\newcommand{\comment}[1]{{\parindent0pt\fbox{\begin{minipage}{0.45\textwidth}{\em #1}\end{minipage}}}}
|
|
\newenvironment{changed}{\red}{\color{black}}
|
|
\newcommand{\todo}[1]{ \color{red} \footnote{ \color{red}[#1] \color{black}} \color{black}}
|
|
\newcommand{\Hide}[1]{%
|
|
{
|
|
\parindent0pt
|
|
\emph{\scriptsize #1}
|
|
}
|
|
}
|
|
%\renewcommand{\Hide}[1]{}
|
|
|
|
|
|
\pagenumbering{arabic}
|
|
|
|
\begin{document}
|
|
|
|
%----------------------------------------------------------------------
|
|
% Title Information, Abstract and Keywords
|
|
%----------------------------------------------------------------------
|
|
\title{\documenttitle}
|
|
|
|
|
|
% % %
|
|
% In case of double blind submissions:
|
|
%\author{
|
|
% \IEEEauthorblockN{Anonymous}
|
|
% \IEEEauthorblockA{Some Research Group\\
|
|
% Some Institution\\
|
|
% Some Email Addresses%
|
|
% }
|
|
%}
|
|
|
|
\author{
|
|
\IEEEauthorblockN{Oliver Schmidt}
|
|
\IEEEauthorblockA{TU Dresden\\
|
|
oliver.schmidt3$[$at$]$mailbox.tu-dresden.de%
|
|
}
|
|
}
|
|
|
|
|
|
\maketitle
|
|
|
|
% force pagenumbering
|
|
\thispagestyle{plain}
|
|
\pagestyle{plain}
|
|
|
|
% % %
|
|
% sources on writing papers:
|
|
% look for a /good/ outline at the end of this text, the /why/ is found at this link:
|
|
% http://homepages.inf.ed.ac.uk/bundy/how-tos/writingGuide.html
|
|
% http://www-net.cs.umass.edu/kurose/writing/
|
|
% http://www.cs.columbia.edu/~hgs/etc/writing-style.html
|
|
% Read ``Zen - or the art of motorcycle maintenance'' to understand what science and research is
|
|
% Read ``The craft of research'' to /really/ learn how to conduct research and report about it! :-)
|
|
% some hints on plagiarism: http://www.williamstallings.com/Extras/Writing_Guide.html
|
|
% read the text above again. the most important part (that we all tend to forget) is only 5 paragraphs
|
|
|
|
\begin{abstract}
|
|
|
|
\abstracttext
|
|
|
|
\end{abstract}
|
|
|
|
\begin{IEEEkeywords}
|
|
% Are NOT: Peer-To-Peer, Anonymity, Privacy.
|
|
% BUT TAKEN FROM THIS LIST:
|
|
% http://www.ieee.org/organizations/pubs/ani_prod/keywrd98.txt
|
|
Security, DRM, Trusted Execution Environments, SGX,
|
|
\end{IEEEkeywords}
|
|
% }
|
|
|
|
\maketitle
|
|
|
|
\IEEEpeerreviewmaketitle
|
|
|
|
\section{Introduction}
|
|
|
|
\IEEEPARstart{I}{n}
|
|
|
|
Motivation: DRM means/ meant lockdown: Bruce Schneier quote, War on General Computation (Cory Doctorow), examples for bad obfuscation DRM
|
|
% % %
|
|
% Literature Survey and Background
|
|
\section{Background}
|
|
\label{sec:background}
|
|
|
|
lockdown techniques: TPM, secure boot
|
|
|
|
TEEs: SGX, TrustZone
|
|
|
|
(InkTag?)
|
|
|
|
Android DRM, EME DRM arch, TBDRM (-> fTPM)
|
|
|
|
|
|
\section{lockdown/ openness}
|
|
|
|
What parts need to be locked down?
|
|
|
|
WiDevine/ Netflix ban from rooted devices
|
|
|
|
- remaining other problems: cultural heritage, inflexibility, tied to a certain technological platform
|
|
|
|
\section{Summary}
|
|
% % %
|
|
% Theory (probably)
|
|
|
|
|
|
\section{Glossary}
|
|
\label{sec:glossary}
|
|
|
|
\nobreak
|
|
|
|
\begin{acronym}[GN6ASL]
|
|
\input{glossary.tex}
|
|
\end{acronym}
|
|
|
|
%\bibliographystyle{IEEEtran}
|
|
%\bibliography{mybib}
|
|
|
|
%----------------------------------------------------------------------
|
|
|
|
\end{document}
|
|
|
|
|
|
% % %
|
|
% A good outline for a computer science paper (according to Al Bundy)
|
|
%
|
|
% Title
|
|
% * - ideally the title should state the hypothesis of the paper
|
|
%
|
|
% Abstract
|
|
% * - state hypothesis and summarise the evidence that supports or refutes it
|
|
%
|
|
% Introduction
|
|
% * - motivate the contribution!
|
|
%
|
|
% Literature Survey
|
|
% * - broad and shallow account of the field, rival approaches, drawbacks of each, major outstanding problems
|
|
%
|
|
% Background
|
|
% * - states previous work in more detail, where this is necessary for understanding
|
|
%
|
|
% Theory
|
|
% * - underlying theory, definitions, theorems etc.
|
|
%
|
|
% Specification
|
|
% * - requirements and specs of implementation
|
|
%
|
|
% Implementation Evaluation Related Work
|
|
% * - narrow but deep comparison with main rivals
|
|
%
|
|
% Further Work Conclusion
|
|
% * - summarise research, discuss significance, restate hypothesis and the evidence for and against it, - recapitulate original motivation, reassess the state of the field in the light of this new contribution
|
|
%
|
|
% Appendices
|
|
%
|