I mean…you have the container right there on your machine. If you’re concerned, just run your own registry and push copies there when needed. This of course is all unnecessary, as you only need the Dockerfile to build a clean image from scratch, and it will obviously work if it’s already been published.
LOVELY COMMENT.
What are you getting at?
So why don’t we just rename the group to “Puritan Self-Hosting Only”? Where is your line?
Stop giving the purists cred here.
If it works for you, use it. Christ.
Ain’t nobody gonna buy your stupid Nazibots either, di ckhead. You are universally despised.
The simplest and most pragmatic option.
Interesting if true…
This again? 🙄
I did answer your questions, but if I missed something, feel free to ask and I can clarify.
The clients (apps) enforce key symmetry for your own keys, server identity, and the exchanged with the other person part of a conversation. Constantly. There is no way to MITM that.
The clients are open source, and audited regularly, and yes, builds are binary reproduceable and fingerprinted on release.
That’s not to say someone can’t build a malicious copy that does dumb stuff and put it in your phone to replace the other copy, but the server would catch and reject it if it’s fingerprints don’t match the previously known good copy, or a public version.
Now you’re just coming up with weird things to justify the paranoia. None of this has anything to do with Signal itself, which is as secure as it gets.
The closest you’re probably going to get to a half decent looking WYSIWYG editor is something templatized top to bottom. Odoo, Ghost…things like that.
I don’t use any Meta products, so not sure how you mean. If you are a user that has been sending e2e messages, then you can surely decrypt said messages if you’re a participant in those messages transactions.
It doesn’t matter if it’s criminal or civil. The costs to bring such a case are massive, and you’re leaving yourself open to a behemoth like Meta just dragging out the case for lengthy periods of time which drastically increase those costs.
No law firm files suit against a giant company like this unless they have rock solid proof they will, at the very least, land a settlement plus recuperation of costs. Just not a thing.
🤣🤣🤣
You need a juice and a nap, Ke-mo sah-bee.
Do you know what size channel attacks are? Because nothing you’ve even tried to bring up describes one at all, or how it applies to your original comments.
Well they did this whole stupid “rebranding” of it becoming e2e after Facebook bought them a few years back, but literally every security researchers was like “Nahhhh, pass”.
What in the world are you talking about here, bud? Your comments are making zero sense.
Look, seriously, if my comment is being upvoted, it’s because I responded to yours, and people understand what I am saying in response.
You, unfortunately, clearly do not understand what I’m saying because you do not grasp how any of this works.
Again, it’s nearly impossible to scrub the entire internet of the code to just run a single command and build a docker image of whatever you were running yourself. If you have the image locally, you can just push it anywhere you want.
Keep Dockerfile, keep checkouts of what you’re running, or push images locally. All very simple.