From 4eca202c647955b0da4cd6035237ffed6bf575c9 Mon Sep 17 00:00:00 2001
From: Richard Luhtaru <79766340+rluhtaru@users.noreply.github.com>
Date: Tue, 20 Dec 2022 02:35:22 +0100
Subject: [PATCH] Fix typo in Lecture 14

---
 lectures/lec14.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lectures/lec14.tex b/lectures/lec14.tex
index a90d6ab..a032b58 100644
--- a/lectures/lec14.tex
+++ b/lectures/lec14.tex
@@ -59,7 +59,7 @@ \subsection{Compound Principal: \textquote{B for A}}
 
 \section{Delegation}
 In interacting with the Gmail server $B$, we may like for Alice ($A$) to give $B$ permission to authenticate as \textquote{$B$ for $A$} and to do so for only 60 seconds into the future. To achieve this, $A$ can sign a message that outlines the permission it would like to give to $B$. This signature becomes the proof of authorization. As an example:
-\[ \Sign(\sk-A, \text{\textquote{A delegates to B}}, \text{start}=\text{now}, \text{end}=\text{now}+60) \]
+\[ \Sign(\sk_A, \text{\textquote{A delegates to B}}, \text{start}=\text{now}, \text{end}=\text{now}+60) \]
 
 Google indeed uses a strategy like this. They have a global DoS-resilient HTTP front-end that performs initial authentication. This frontend is then responsible for generating these scoped delegation signatures for each operation that the user would like to do and sending them along to the individual services. These signatures are then used for all following operation.