mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

573
comptes actifs

#webapi

0 message0 participant0 message aujourd’hui

File encryption with a browser.

I've been exploring the #WebCryptoAPI and I'm impressed!

When combined with the #FileSystemAPI, it offers a seemingly secure way to #encrypt and #store files directly on your device. Think #localstorage, but with #encryption!

I know #webapps can have #security vulnerabilities since the code is served over the web, so I've #OpenSourced my demo! You can check it out, and it should even work if #selfhosted on #GitHubPages.

Live Demo: dim.positive-intentions.com/?p

Demo Code: github.com/positive-intentions

Hook Code: github.com/positive-intentions

IMPORTANT NOTES (PLEASE READ!):
* This is NOT a product. It's for #testing and #demonstration purposes only.
* It has NOT been reviewed or audited. Do NOT use for sensitive data.
* The "password encryption" currently uses a hardcoded password. This is for demonstration, not security.
* This is NOT meant to replace robust solutions like #VeraCrypt. It's just a #proofofconcept to show what's possible with #browser #APIs.

dim.positive-intentions.com@storybook/core - Storybook

Question for the .Net developers. When working with a service layer and WebAPI where do you put the user input *format* validation? controller/endpoint, service, or both?

I'm currently using fluentvalidation for format validation, validated at the WebAPI endpoint(s), and business logic validation within the service layer. Any serious formatting issues would cause a model exception, which seems fair as if invalid user data reaches the service layer I consider it exceptional