etsd
hat.sh
etsd | hat.sh | |
---|---|---|
4 | 8 | |
48 | 2,028 | |
- | - | |
3.6 | 0.0 | |
9 months ago | 2 months ago | |
JavaScript | JavaScript | |
GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
etsd
-
How I run my servers
A pretty same setup with a bunch of differences:
1. I'm using a single postgresql database for all apps (each with a different user) on a different server; each app has a different db user
2. I use a minio instance for file/media uploads/serving
3. I mostly use nginx but i'm transitioning new apps to caddy because of automatic integration with let's encrypt and much smaller config for common purposes
4. I use a fab-classic (fabric 1x) script to deploy new versions: https://github.com/spapas/etsd/blob/master/fabfile.py
5. For backup I do a logical db backup once per day via cron (using a script similar to this https://spapas.github.io/2016/11/02/postgresql-backup/)
6. One memcache instance of all apps
7. Each app gets a redis instance (if redis is needed): https://gist.github.com/akhdaniel/04e4bb2df76ef534b0cb982c1d...
8. Use systemd for app control
-
Show HN: Enc – A modern and friendly CLI alternative to GnuPG
Yes, you are right on that. If the server is compromised a malicious user may change the client-side code to add a backdoor and steal your private key when you unlock it. He'll be able to steal only the keys that are unlocked while the backdoor stays undetected (not all the data).
The ideal way to resolve that would be to change the service to an API and offer binaries with a correct signature so the user can check and make sure that they get the correct thing. Actually I tried writing the client binaries using electron (https://github.com/spapas/etsd/tree/master/client) but didn't have the time for that :(
You are rigth though, I've added a Risks section to warn for that thingie https://github.com/spapas/etsd/blob/master/README.md#risks
- Show HN: ETSD – Transmit sensitive data encrypted across your organization
hat.sh
-
How secure is it to encrypt a file using 7zip? Can nobody really access the files without knowing the password?
Even if that were to happen, you can run the page locally. Also the entire source is available on github https://github.com/sh-dv/hat.sh
- Major file encryption software Hat.sh now accepts monero donations.
- Hat.sh: Encrypt files securely in the browser
- Upcoming v2.1.1 update · Discussion #40 · sh-dv/hat.sh
-
Hat.sh V2 release - simple, fast, secure client-side file encryption.
On desktops, the encryption is handled by the service-worker. Since we are not using any server-side processing, the app registers a fake download URL (/file) that is handled by the app service-worker fetch api. this service worker is installed and activated in the browsers once the user visits the site.
-
memory efficient in-browser large file encryption using libsodium. [hat.sh v2.0 beta]
github repo branch : https://github.com/sh-dv/hat.sh/tree/v2-beta