Commit c212222a authored by Xunnamius (Zara)'s avatar Xunnamius (Zara)

almost all TODOs cleared

parent 0ed8318c
......@@ -9,9 +9,9 @@ by balancing competing security and latency requirements via \emph{cipher
switching} in space or time. We implement SwitchCrypt on an ARM big.LITTLE
mobile processor and test its performance under the popular F2FS LFS. We provide
empirical results demonstrating the conditions under which different switching
strategies are optimal and explore four related cases. In all cases, we find
that SwitchCrypt achieves at least \TODO{XXX} improvement compared to static
approaches.
strategies are optimal and explore four related cases. We find that SwitchCrypt
achieves at least 3.3x in total energy use reduction and a 1.6x to 4.8x
reduction in I/O latency in our cases when compared to static approaches.
\end{abstract}
......@@ -35,8 +35,6 @@ big.LITTLE mobile processor and test its performance under the popular F2FS LFS.
We provide empirical results that demonstrate the conditions under which
different switching strategies would be optimal. We then study SwitchCrypt's
dynamic flexibility through four case studies where latency, energy, and desired
security properties change dynamically. In all cases, we find that SwitchCrypt
achieves at least \TODO{XXX} improvement compared to static approaches that must
pick only a single operating point. \TODO{We need a much stronger statement
about the results, but let us wait until the overhead data is crunched before
constructing that sentence.}}
security properties change dynamically. We find that SwitchCrypt achieves at
least 3.3x in total energy use reduction and a 1.6x to 4.8x reduction in I/O
latency in our cases when compared to static approaches.}
......@@ -82,6 +82,9 @@ dynamically with acceptable overhead.
We implement SwitchCrypt and three switching strategies--\emph{Forward},
\emph{Selective}, and \emph{Mirrored}---along with the ChaCha and Freestyle
stream ciphers through our novel API. We demonstrate cipher switching utility
with empirical data from four case studies. We find that SwitchCrypt achieves at
least \TODO{XXX} improvement compared to static approaches.
stream ciphers through our novel API. We then study SwitchCrypt's dynamic
flexibility through four case studies where latency, energy, and desired
security properties change dynamically. SwitchCrypt achieves a reduction of at
least 3.3x in total energy use when compared to static approaches; further, we
see a reduction of 3.1x to 4.8x for read latency and 1.6x to 2.8x for write
latency compared to static approaches.
......@@ -31,7 +31,7 @@ implementation would be greatly simplified by adding an ``intent'' parameter to
the POSIX \textit{read()} and \textit{write()} system calls, allowing
SwitchCrypt to more exactly map individual I/O operations to specific areas of
the backing store when spatially switching. We simulate this with IPC.
\TODO{This intent parameter could also be a security score or something right?
\TO\DO{This intent parameter could also be a security score or something right?
You should spell out exactly what that intent parameter means and maybe change
its name so its use is clearer.} \PUNT{This is especially important when
considering the selective switching strategy; a production-ready implementation
......@@ -63,7 +63,7 @@ A naive implementation is trivial (\eg{execute the chosen strategy on every I/O
operation}), this navigation must occur with acceptable overhead by preserving
performance wherever possible. The cryptographic driver provides such a
mechanism, tying together cipher switching strategies and the generic stream
cipher API. \TODO{Which cryptographic driver? You need to clarify if you are
cipher API. \TO\DO{Which cryptographic driver? You need to clarify if you are
talking about a piece of our design or something we are using from prior work.}
In the cases of Mirrored and Selective switching, we use offset to determine in
......@@ -72,7 +72,7 @@ which area of the backing store receives I/O.
In the case of Forward switching, it is tempting to implement it such that a
nugget is completely re-ciphered during I/O every time its metadata indicates
that it was previously encrypted using a non-active cipher. However, such a
naive implementation can have disastrous effects on performance. \TODO{It is not
naive implementation can have disastrous effects on performance. \TO\DO{It is not
clear why that would be disastrous.}
First, a nugget is considered \emph{pristine} if it has not had any data written
......@@ -95,7 +95,7 @@ re-keying operation every time. On the other hand, during hard re-cipher, the
nugget's metadata is changed to match the active cipher configuration \emph{and}
the nugget data is encrypted using the new cipher.
\TODO{Maybe repeat that mirrored relies on someone to implement the fast secure
\TO\DO{Maybe repeat that mirrored relies on someone to implement the fast secure
erase, so that you can read the fast region until it is time to panic and then
you quickly erase? Are there other uses of mirrored?}}
......
......@@ -5,7 +5,7 @@ performance often conflicts with other key concerns. In this paper we presented
SwitchCrypt to navigate the security and latency/energy tradeoff space via
\emph{cipher switching} in space and time. We provided empirical results
demonstrating the conditions under which different switching strategies are
optimal and explored four related cases. In all cases, we find that SwitchCrypt
achieves at least \TODO{XXX} improvement compared to static approaches.
optimal and explored four related cases. In all cases, we found that SwitchCrypt
achieves reduced energy usage and I/O latency compared to static approaches.
\PUNT{\TODO{Add David to acknowledgements once we get out of anon reviews.}}
\PUNT{\TO\DO{Add David to acknowledgements once we get out of anon reviews.}}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment