Skip to content

Patching typos #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ClementLohCK wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Patching typos #31

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
397287a
fix: fix typo
ClementLohCK Aug 6, 2023
733be0c
fix: fix typo
ClementLohCK Aug 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _assignments/pa2_2_ap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ Now both client and server must implement `MODE: 3`, which signifies the `authen
- another M1 from server: size of incoming M2 in bytes (this is `server_signed.crt`)
- another M2 from server: `server_signed.crt`

2. Upon receiving `MODE: 3`, the server will send these four messages above _immediately_, in sequence one after another. There's no need to send another `MODE` to the client because are still under the AP -- and the sequence <span style="color:#f77729;"><b>must be</b></span> as such: client send MODE 3, then <span style="color:#f77729;"><b>TWO</b></span> messages, and expecting <span style="color:#f77729;"><b>FOUR</b></span> messages from the server.
2. Upon receiving `MODE: 3`, the server will send these four messages above _immediately_, in sequence one after another. There's no need to send another `MODE` to the client because they are still under the AP -- and the sequence <span style="color:#f77729;"><b>must be</b></span> as such: client send MODE 3, then <span style="color:#f77729;"><b>TWO</b></span> messages, and expecting <span style="color:#f77729;"><b>FOUR</b></span> messages from the server.

3. Once the client receives both replies from the server, it will perform the `CHECK` as specified above using the CA's public key extracted from `csertificate.crt`. If check is successful, the regular non-secure FTP should proceed where we can key in the file names one by one for the server to receive. Otherwise, send a `MODE 2` to close connection immediately.

Expand Down
2 changes: 1 addition & 1 deletion _assignments/pa2_3_cp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Figure out <span style="color:#f77729;"><b>which key</b></span> to use to encryp


### Expanding the FTP
Make a <span style="color:#f77729;"><b>copy</b></span> of Task 1 files: `ClientWithSecurityAP.py` and `ClientWithSecurityAP.py` each, and name it as `ClientWithSecurityCP1.py` and `ServerWithSecurityCP1.py`.
Make a <span style="color:#f77729;"><b>copy</b></span> of Task 1 files: `ClientWithSecurityAP.py` and `ServerWithSecurityAP.py` each, and name it as `ClientWithSecurityCP1.py` and `ServerWithSecurityCP1.py`.
> Leave the original files as is. You should have 6 `.py` files now under `source/`.

There's no need to implement any new `MODE` in this task.
Expand Down