Merica means freedom to do dumb things. Lemme fly!
https://dev-to-uploads.s3.amazonaws.com/i/it0fk0jbqphcgecnpbq7.jpg
Merica means freedom to do dumb things. Lemme fly!
https://dev-to-uploads.s3.amazonaws.com/i/it0fk0jbqphcgecnpbq7.jpg
Hmmm. No.
You don’t partially decrypt passwords. You either get the full thing or you get gobble.
So if they get 1, they still don’t know you use or or etc. I wouldn’t just straight up say “Netflix” in my service tagging.
You can take this a step further to segregate passwords as well.
Reusing passwords across devices is bad. If one gets compromised you don’t want a password being out into a brute force table to be used with all your other accounts elsewhere.
This method of tagging using HTML markup styles in your passwords lets you keep the same core passphrase but alter the tagging, specific to the service.
You can do this easily while also giving you artificial password complexity.
Example:
Core passpgrase is “yogurt”
Password for gmail becomes markup with a yogurt
I only need to remember yogurt.
Every device just gets a truncated service tag appended to the beginning and end using HTML style tags.
Suddenly you have a 26+ character password that you don’t forget and doesn’t compromise you across other services because each is different.
Most modern cancer drug treatment is sequenced to at least the specific proteins of the type of cancer it is.
Have breast cancer? Cool. We figure out which of the many variations so that we can give you medications for that exact type of breast cancer.
This sort of specific targeting has been increasing and increasing for the last 20 years. MRNA is the next step of that and is highly likely to be a means or become or for treatments in many other areas.
Aluminum oxynitride is transparent aluminum, but alpha aluminum oxide, which is also transparent, is called Corundum.
What is the diagnosis and cure for the disease that has ravaged me for the last 13 years?
Thanks.
You can simply look at the data for avoidable mortality rates among OECD countries. This tells you the impact of healthcare access to early mortality that could have otherwise been avoided with better access to care. Time to care directly impacts these measures.
For 2022, the United States is only better than Latvia, Lithuania, Peru, and Mexico in avoidable deaths per 100,000 people. Every other nation in the data set with values is lower. Sometimes by more than half.
Every other western nation shits all over US stats in infant mortality as well, showing that when you remove obesity from the equation, you still get far worse quality of care from the start of life.
All this when paying 3X the amount to get the care in the first place.
The worst part is the US average person pays more than 4 times the amount of administrative care than then EU average. 4X for administrative costs.
It’s 9 times as much admin cost as countries like Italy who also have some of the shortest wait times to see a physician, or specialist, in the OECD data set!
Imagine paying 3X more per capita, waiting longer, and getting worse measured outcomes for decades… then still have people asking if they are getting a raw deal?
Opinion letter.
None of the accusations in the title can be substantiated, more than a dozen other apps and technologies are backed by the same organization the article mentions funds part of a signal’s budget.
Assertions that TOR has a governmental back door, that the CIA wants people to use Signal, are not substantiated, and the article states at the same time that there are fears the anonymity of Signal threatens western governments. Can’t have it both ways.
The only definitive thing this article can prove or cite is where some OTF funding goes, which was publicly disclosed since it’s inception. It reads like a /r/superstonk GME reeeeeee post equivalent for communication security by a ti foil hat.
9mm? 1 round? Nah.
Notice how I didn’t just use the service name?
Whatever nickname you use for your services. There is no requirement you also use the service name in the tagging template.
The idea that a breach of a service would have someone looking at your individual password is also pretty silly. There would be variations and pattern matching Lagos run against lists of hundreds of thousands to millions of passwords… but the decryption of a complete password to plain text is so reductions at this point, we are talking about the 0.01% case of a then even more silly “let’s look at this guys password in particular” 0.0001% case on top of it…
It’s not a real problem because if your service is at the point it is leaking not just salted and hashed passwords, but plain text passwords: you are in a big problem up no matter what for most users. Almost everyone reuses passwords. The real risk is the simple reuse. Get just a slightly different variation and you are miles more secure in the case of a breach that results in full decryption.
The majority still reuse Password1234! Everywhere. This gives you a easier way to be miles better.
Better still of course is some sort of managed password vault, assuming you trust their implementation. However, this costs zero in the training, or tech literacy upskilling that even the moderate change to a password vault requires. It’s simply an extension of what people already intuitively know. Thus, barrier to entry is easier while giving you several orders more protection.