Argon2 | Argon2 Bindings for .NET | Binary Executable Format library

You're trying to create a user associated with a new TwoFa instance that has the same primary key value.
If you indicate include in create that means you want to create a user along with a TwoFa record and that's not what you want to get.
If you just want to create a TwoFa record and associate it with an existing user then just indicate UserId without include option:

So in case anyone comes across similar for any reason with me encountering this probably due getting a new machine and IT doing their voodoo magic transferring my old stuff to this new machine.

Anyhow, there were a bunch of things I still needed to install after I got my new machine and i am not able to exactly pin point what caused issues from my question but in the end I was able to resolve. Follow me there below ...

Checking out my python.exe files I found 2 paths. First one added as environment variable

1. C:\Users-----\AppData\Local\Programs\Python\Python310
2. C:\Users----\AppData\Roaming\Python\Python310\

Second one not added. Adding roaming version to path variables did not solve the issue and gave additional errors instead: Fatal error in launcher: Unable to create process using '"C:\Program Files\Python310\python.exe"

So

1. I uninstalled python (done that before didnt help doing just that alone)

2. Deleted all environment variables pointing to python (here is what environment variables are just in case - https://www.computerhope.com/issues/ch000549.htm)

3. Uninstalled python extension from VS code (https://marketplace.visualstudio.com/items?itemName=ms-python.python)

4. Deleted Python folders mentioned in the two paths above

5. Then reinstalled python (clicked add to path during installation)

6. Reinstalled VS code python extension

7. Everything works now.

Best of luck

After a few days I was able to find the solution

Firstly, my code needed to be fixed to correctly call the params needed with the proper name

The problem is redis. With newer versions it saves the keys differently.

If you want to use the same code as Ben, you have to use legacyMode:

What is going on?

The package you are using (argon2) contains bindings to a C implementation of the argon2 algorithm. In other words, the package itself wraps a library written in C, and makes it accessible inside your node.js environment.

That C package is also shipped with your package, and compiled (or downloaded) when you run npm install argon2. That means that after installing argon2, there is a binary shared library on your file system, that is interfacing with your node environment. Because you are installing on MacOS, the binary will be compiled (or downloaded) for Mac. This means you end up with a MACH-O file (which is the format executables for macOS come in) instead of an ELF file (which is format Linux uses for executables).

Now your Lambda (which runs Linux under the hood) effectively complains, that the executable you've built on your Mac is not a Linux executable.

How do you fix this?

In simple terms, you need a way to npm install that will build or download the argon2 version for Linux. There are two different ways to achieve this. Pick one:

1. npm install on Linux

Pretty much as the title says, download and build your dependencies under Linux. You can use a Virtual Machine, or a Docker container to do that. Another option would be to use the AWS build SaaS product (AWS CodeBuild) to do this.

1. npm install --target_arch=x64 --target_platform=linux --target_libc=glibc on Mac

Thankfully argon2 comes with support for node-pre-gyp. They effectively provide you with prebuild binaries, which means that you can just pull the linux binaries end do not have to compile them yourself. To do that, thow away your node_modules folder and run npm install --target_arch=x64 --target_platform=linux. This will download the Linux files, instead of the macOs files. You can then push everything into your lambda. Please note that this means your application will not run locally anymore, since your mac cannot run the Linux executable (you would have to npm install again, leaving out the two parameters to get back to the MacOS version).

Please note that there might be packages apart from argon2 that do not support MacOS, in which case you would have to take the first option.

applaunchservices appears to be Apple-only:

Simple package for registering an app with apple Launch Services to handle UTI and URL. See Apple documentations for details.

I suspect you don't need that, either. Did you create your requirements.txt from a pip freeze? There's likely a bunch of stuff in there you don't need.

I suggest you review that file and remove anything you aren't directly depending on. pip will find transitive dependencies (dependencies your dependencies depend on) and install them automatically.

Prune that file, commit, and redeploy.

The problem is most likely happening because your trying to add the Authorization header before the user is logged-in.

In that situation authToken is undefined and you are assigning it to the header anyways.

You could solve it just adding a guard in your intercept method to first check if you have an authToken before attaching it to the request.

--enable-gd-native-ttf is deprecated as per the image documentation:

To enable support for native TrueType string function add --enable-gd-native-ttf. (This option has no effect and has been removed as of PHP 7.2.0.)

Also --with-gd was replaced with --enable-gd.

https://www.php.net/manual/en/image.installation.php

Judging from the return value of the hash function in class PasswordHasher from argon2-cffi, it appears it can be concluded that the hybrid "flavour" is used by default.