diff options
author | jaseg <git-bigdata-wsl-arch@jaseg.de> | 2020-05-22 18:30:32 +0200 |
---|---|---|
committer | jaseg <git-bigdata-wsl-arch@jaseg.de> | 2020-05-22 18:30:32 +0200 |
commit | 6ca243854267ad2155c5e1b9115efe092437e7fd (patch) | |
tree | c1d2228700af26aceaa4a8906a2742b77773936e /ma | |
parent | f48490243c030cb456031116f32a9231d7918096 (diff) | |
download | master-thesis-6ca243854267ad2155c5e1b9115efe092437e7fd.tar.gz master-thesis-6ca243854267ad2155c5e1b9115efe092437e7fd.tar.bz2 master-thesis-6ca243854267ad2155c5e1b9115efe092437e7fd.zip |
ma: work out small issues
Diffstat (limited to 'ma')
-rw-r--r-- | ma/safety_reset.tex | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/ma/safety_reset.tex b/ma/safety_reset.tex index 5314bac..bb0d46d 100644 --- a/ma/safety_reset.tex +++ b/ma/safety_reset.tex @@ -1046,8 +1046,7 @@ denial-of-service attacks on our system by any of the four attacker types. All r from the \emph{reset authority} and are cryptographically secured to provide authentication and tamper detection. Under this model, attacks on the electrical grid components between the \emph{reset authority} and the customer device degrade into man-in-the-middle attacks. To ensure the \textsc{safety} criterion from Section \ref{sec_criteria} holds we -must % TODO check whether this \ref displays as intended -make sure our cryptography is secure against man-in-the-middle attacks and we must try to harden the system against +must make sure our cryptography is secure against man-in-the-middle attacks and we must try to harden the system against denial-of-service attacks by the attacker types listed above. Given our attacker model we cannot fully guard against this sort of attack but we can at least choose a commmunication channel that is resilient against denial of service attacks under the above model. @@ -1623,6 +1622,7 @@ realistically be up to $\mathcal O\left(10^3\right)$, which is easily enough for % FIXME here and in previous ~2 pages get transmitter/receiver and sender/listener terminology straight. Also perhaps do % some sort of scenario definition introducing those terms somewhere. +% Also sort out term for "safety reset controller" throughout document \chapter{Practical implementation} @@ -1737,12 +1737,11 @@ that more complex perform worse when the input signal deviates from their models \subsection{Frequency sensor hardware design} \label{sec-fsensor} -Our safety reset controller % FIXME is this the right term? -will have to measure mains frequency to later demodulate a reset signal transmitted through it. Since we have decided to -do our own frequency measurement system here we can use this frequency measurement setup as a prototype for the -frequency measurement subcomponent of the demodulation system we will later develop. Since we do not plan to do a -large-scale field deployment of our measurement setup we can keep the hardware implementation simple by moving most of -the signal processing to a regular computer and concentrating our hardware efforts on raw signal capture. +Our safety reset controller will have to measure mains frequency to later demodulate a reset signal transmitted through +it. Since we have decided to do our own frequency measurement system here we can use this frequency measurement setup as +a prototype for the frequency measurement subcomponent of the demodulation system we will later develop. Since we do not +plan to do a large-scale field deployment of our measurement setup we can keep the hardware implementation simple by +moving most of the signal processing to a regular computer and concentrating our hardware efforts on raw signal capture. \begin{figure} \begin{center} |