summaryrefslogtreecommitdiff
path: root/content/projects/python-encryption
diff options
context:
space:
mode:
authorBenjamin Chausse <benjamin@chausse.xyz>2024-02-10 10:04:14 -0500
committerBenjamin Chausse <benjamin@chausse.xyz>2024-02-10 10:04:14 -0500
commit8bd3be35bccd742bfa91793851443724d279824e (patch)
tree59861a1b592f8edfabefc55b30b3d18374174a35 /content/projects/python-encryption
parent5d58e8018c549c3b59c498eadbfcdb6955d02d70 (diff)
Update project structure + new shortcodes
Diffstat (limited to 'content/projects/python-encryption')
-rw-r--r--content/projects/python-encryption/index.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/projects/python-encryption/index.md b/content/projects/python-encryption/index.md
index 3ebd70b..c8207c6 100644
--- a/content/projects/python-encryption/index.md
+++ b/content/projects/python-encryption/index.md
@@ -31,11 +31,11 @@ viewed from that perspective, an entire article could be thought of as one big
integer in base255. I decided to start by converting the source message one
might want to encrypt into decimal form as shown by this animation:
-![How the message gets encoded](msg-encode.gif)
+{{< img src="msg-encode.gif" alt="How the message gets encoded" caption="" >}}
The thing is, if a message can be converted from base255 to decimal, so can
the password protecting the original message. You would then have both the message
and the password in a format that feels much more intuitive to manipulate.
So this is what I did:
-![How the password gets encoded](psswd-encode.gif)
+{{< img src="psswd-encode.gif" alt="How the password gets encoded" >}}