We can not use botan on arm, so we need to look for another way to do password hashing #5

Closed
opened 2023-06-20 18:21:50 +02:00 by migration-script · 0 comments

Summary

Botan uses (x86) inline assembler and thus can't be used on arm. We need some other way to hash our passwords.

Basic information

Description

As mentioned above, botan is not compatible with arm. Thus compilation fails.

Expected behaviour

Program compiles sucessfully.

Actual behaviour

Compilation fails.

Reproduction steps

  • Install ldc and dub on an arm machine
  • dub build --compiler=ldc2

Other things to be mentioned

One possible replacment for botan would be to just use SHA2, which is included in phobos. The Raspberry Pi is slow enough as it is that SHA2 should be secure enough. However, we would need to generate salts manually and phobos does not contain a cryptographically secure PRNG. Any suggestions?

## Summary ## Botan uses (x86) inline assembler and thus can't be used on arm. We need some other way to hash our passwords. ## Basic information ## - Version: https://git.f3l.de/fsimphy/calendar-webapp/commit/1e860a5363432e13786c7dd894e6037f3aff4bd3 - Platform: armv6h, armv7h ## Description ## As mentioned above, botan is not compatible with arm. Thus compilation fails. ### Expected behaviour ### Program compiles sucessfully. ### Actual behaviour ### Compilation fails. ### Reproduction steps ## - Install `ldc` and `dub` on an arm machine - `dub build --compiler=ldc2` ## Other things to be mentioned ## One possible replacment for botan would be to just use SHA2, which is included in phobos. The Raspberry Pi is slow enough as it is that SHA2 should be secure enough. However, we would need to generate salts manually and phobos does not contain a cryptographically secure PRNG. Any suggestions?
migration-script added this to the 0.1 milestone 2023-06-20 18:21:50 +02:00
migration-script added the
Priority: Critical
Tech: Security
Tech: Library
Type: Bug
labels 2023-06-20 18:21:50 +02:00
saluu was assigned by migration-script 2023-06-20 18:21:50 +02:00
Sign in to join this conversation.
No description provided.