MyCrypto | source tool that allows you to manage your Ethereum | Cryptocurrency library

Followed @GProst suggestions and analysed a bit and the below fix worked and I don't know the solution yet.

As per the Kendo UI angular documentation,

Sets the FormData key which contains the files submitted to saveUrl. The default value is files.

So, I just changed the parameter name from file to files and it worked.

Please check multer usage documentation carefully.

You're passing fileService.upload as a second argument to router.post method and fileService.upload is an object and not a function (which the error message points).

Instead, you should pass fileService.upload.single('avatar') or use other upload methods like array, fields, any, none.

The answer was the validation actor. I thought it was a password field, but it actually specifies the security header. Removing it got me passed the error

So I figured it out.

It was skipping the validation

No, you're not doing it the right way. MD5 is - or rather was - a cryptographically secure hash. It is not directly applicable to hash passwords. To hash passwords you need a password hash that contains a random salt and work factor (cost or iteration count, depending on the password hash used). Examples of these are bcrypt, PBKDF2 and the newer Argon2. Here is a random article that discusses the use of password hashes.

As for the encoding, I would always try to keep to existing standards, where they exist. For password hashing the applicable standard is the Modular Crypt Format. If you are designing a new scheme without strong interoperability requirements then you may also use the Password Hashing Format.

Both use a type of base 64 encoding as output format for the salt and password. An example is the bcrypt output $2a$10$N9qo8uLOickgx2ZMRZoMyeIjZAgcfl7p92ldGxad68LJZdL17lhWy where 2a indicates bcrypt and the format, 10 is the cost (work factor) and N9qo8uLOickgx2ZMRZoMye is the radix 64 encoding of the salt; the rest is the password hash. Note that there is no dollar sign separator between the salt and the password.

I've taken the above example from the bcrypt Wikipedia page which is an interesting starting point for getting more information, including possibly the MD5 hash output for crypt (which as indicated, you should not use).

Almost forgot, yes, 16 random bytes / 128 bits of salt is plenty; nobody would blink an eye if you used 8 bytes, more than 32 bytes is overdoing it.

if you trying to sum some values then they need to numeric (when you importing data to mongo try to set type for values)

You can add anything to the request via custom headers:

As David mentioned you have a syntax error in your command. The easiest way to achieve what you're after is to use MongoDB Compass and just imprt through the GUI. (as shown below):

Then just select the CSV option to import and upload the file to your collection:

Your API method: