Browse Source

Typos

master
Leon Etienne 2 months ago
parent
commit
93f46d388c
  1. 8
      src/projects/code-it-yourself/gcrypt.md

8
src/projects/code-it-yourself/gcrypt.md

@ -19,7 +19,7 @@ Skip right to the [command line tool implementation](#worth-a-look-gcrypt-cli)!
GCrypt is a feistel block cipher implemented in C++ with the functional goal of providing a pythonic API.
It comes with a wrapper class making it even easier to use, and can be easily installed as a git submodule.
Besides simple en- and decryption, it also supports calculating hashsums, and provides an extensive pseude random number generator (prng).
Besides simple en- and decryption, it also supports calculating hashsums, and provides an extensive pseudo random number generator (prng).
## Features
* It has very easy syntax
@ -190,7 +190,7 @@ The realized featureset includes:
* A variety of ciphertext formats
* Encryption & Decryption (files, streams, parameters)
* Hashing (files, streams, parameters)
* Optional puffering (not digesting an input block-by-block, but all at once)
* Optional buffering (not digesting an input block-by-block, but all at once)
* Printing progress (it is still slow after all)
### A few usage examples
@ -229,10 +229,10 @@ File `decrypted_cat.jpg` will be created. You can now open it again. Its content
#### Encrypting large files takes time. How's the progress?
```sh
$ gcrypt -e --keyask --infile "cat.jpg" --puffer-input --progress
$ gcrypt -e --keyask --infile "cat.jpg" --buffer-input --progress
```
Something along the lines of `Encrypting... (Block 200 / 1148 - 17.4216%)` will be regularly, but not too often, printed to stderr.
Obviously, to print progress, we have to know the size of the input. Hence, it has to be puffered.
Obviously, to print progress, we have to know the size of the input. Hence, it has to be buffered.
#### Any cipher can also compute hashsums
```sh

Loading…
Cancel
Save