diff options
| author | Christian Brabandt <cb@256bit.org> | 2023-07-11 22:38:29 +0200 |
|---|---|---|
| committer | Christian Brabandt <cb@256bit.org> | 2023-08-09 21:35:38 +0200 |
| commit | 6019fed0c50a31f0f9bb6c80e4e2b97d3f71565a (patch) | |
| tree | d8aea2ec2d35915c9ac0271f27d25e1b50f4c7cc /src/version.c | |
| parent | 92f076e53e22b467fb6d12051fec2d4bdbda88fe (diff) | |
patch 9.0.1682: sodium encryption is not portablev9.0.1682
Problem: crypt: sodium encryption is not portable
Solution: use little-endian byte order for sodium encrypted files
As mentioned in #12586, sodium encryption only works on little ending
architectures, because reading and writing the sodium encryption
parameters are stored in the encrypted files in an arch-dependent way.
This of course fails for big-endian architectures like s390.
So make sure to use little-endian byte order when reading and writing
sodium encrypted files.
fixes: #12586
closes: 12655
Diffstat (limited to 'src/version.c')
| -rw-r--r-- | src/version.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/version.c b/src/version.c index 39f637c185..6903b261d7 100644 --- a/src/version.c +++ b/src/version.c @@ -696,6 +696,8 @@ static char *(features[]) = static int included_patches[] = { /* Add new patch number below this line */ /**/ + 1682, +/**/ 1681, /**/ 1680, |