-
Notifications
You must be signed in to change notification settings - Fork 83
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.
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
[Feature Request] Arm version #21
Comments
What happens if you try and compile it? I think the code should be portable except perhaps for the hardware AES instructions. |
raspbian stretch using this gcc version when compiling the source got some error like this: where can i remove the hardware AES instructions from the source code? |
It should not be too difficult. First Next That should work. The implementation will fall back on the portable software implementation of AES. |
i have make change to makefiles and the earlier error was sloved. now it stuck on compiling http_data and install_data.it generate big file in endless loop.i use my linux machine to compile http_data and install_data and make static c source file for it.somehow i able to compile reqrypt client_install.
any clue? |
btw there is some warning when compiling the client_install.
|
Unfortunately, I do not. At the very least, you'd probably need to run it in a debugger to find the crash location, and maybe that can help. The EOF warning is unlikely to be the culprit. |
What about arm aes hardware support? Take look at almost complete implementation https://github.com/CryptoManiac/gravity-sphincs/blob/arm-prerelease/Optimized_Implementation/primitives/aarch64/aes.c |
We could consider adding it, but maybe after the basic ARM client is working. However, hardware support is not so important for the client. Rather, it was mainly intended to help optimize the server a bit. I am not sure how much of a difference it really makes in practice though. |
I compiled |
@svost check my git repo. I have managed to compile client and server on raspberry pi. Btw what devices are you using? |
@puppet13th https://www.scaleway.com/pricing/ |
@svost Arm Instances? Have you checked and my git fork? If your server running an armv8, it should have hardware aes extension, but don't know about support from the gcc. Check aes extension : Check gcc version : I have tested from raspberry pi 3 which have armv8 cpu. It doesn't have aes extension. |
Yes, scaleway cpu has hw aes support, but arm code for aes complitely different (neon vs x86 intrinsics). So, it would be better if all realisations will be placed in one current repo. May be some #ifdef's in c code, plus some editions of https://github.com/basil00/reqrypt/blob/master/configure.ac#L54 - this line serve only x86 and x86_64 realisations, not arm architecture and rewriting cfg.make.in (-maes flag work around) give full support for arm platform. |
i want to use with rpi. can you write for arm version? thanks
The text was updated successfully, but these errors were encountered: