tinnitus can be caused for other reasons than loud music, some that are not that well understood. Any sensorineural hearing loss can be accompanied by tinnitus. Autoimmune inner disease (AIED) and meniere's disease can bring about tinnitus. Tinnitus sucks. I think the best guess is nerve cells in the inner ear firing improperly and generating a random noisy signal that gets interpreted wrong by the brain.
I've got otosclerosis which causes tinnitus too. It sucks, but thankfully you get used to it somewhat and listening to background music brings me a lot of relief.
all right - sounds like you know a lot about it. Is it fair to say most tinnitus in the world is preventable, and most (as a percentage of people suffering from tinnitus) have had as a direct cause loud noise? (So that if they had had earing protection, they would not have tinnitus.)
The GP's points are all a bit weak, especially if this method uses a good KDF like bcrypt to generate the keys.
I used SuperGenPass for a while, before switching to KeePass, and the major drawbacks I found were:
1) No way to change a password. None at all. If a site required you to make up a new password, you're out of luck (or you have to come up with a new master password every time and remember which master password to use for which site).
2) If a website is incompatible with the generated password, you're out of luck. My bank (because of course it would be the bank, cat sharing websites are more secure) would throw a fit because I had a number in my password and refuse to set it.
3) If someone has a keylogger or otherwise steals your master password, you're done for everywhere. This is not so with password databases, because the attacker also needs the file.
4) It's just not really that much more convenient than KeePass + KeePassAndroid. Hell, the latter is more convenient because I don't have to keep retyping my password, I can store it in memory protected by my fingerprint, which is something that no SuperGenPass-compatible app I've found does.
> 3) If someone has a keylogger or otherwise steals your master password, you're done for everywhere. This is not so with password databases, because the attacker also needs the file.
It's about equivalent though. If someone can keylog you, they can probably obtain the file. If that's through malware then they simply grab the file with the malware, if that's through a hardware keylogger then they just grab it off your machine when you're not around. Even if you used FDE, you're dead in the water because they logged your FDE password too.
Heck, if I were the malware author I'd inject into KeePass or similar and dump your decrypted database as soon as you login, immediately bypassing any anti-keylogger tools, keyboards, alternative authentication methods for your password manager, etc that you might have used.
It's important to think about realistic threat models with things like this. If you're keylogged you're already screwed unless you use your password database on a separate machine.
#2 - the password generation options are part of the input to the generation function for LessPass. Problem of course is that you have to either remember those or store them somewhere, at which point you might as well store the password database.
In principle you could add a post-generation step that takes a description of the site's particular brand of password limitation damnfoolery and munges the output to fit. Then this profile would need to be saved somewhere so the same step could be done at password filling time.
(Still less sensible than doing this once and encrypting the result.)
If there's any format regularity in the output, like it's in one of the PKCS message formats, that could be detected. Or if it's a fixed length that could give it away.
Webcam hack. Social engineering. Binoculars. All the things.
Just sweeping them up en masse and trying popular keys.
> If there's any format regularity in the output, like it's in one of the PKCS message formats, that could be detected.
After entering some junk data, and incrementing the counter field, /every/ generated password has started with one of [aeiouy], so there clearly is some regularity in the output, and I guess more if analysed in detail.
Same here, it seems like every password starts with one of these [aeiouy] characters. So it seems these passwords are not as safe as they seem. Brute force may not be necessary to break these passwords. Is there any alternative services out there that require no storage?
I suspect that if a hacker were focused on a person (say a person under investigation or a celebrity), they could simply use that as one of many strategies in compromising the password.
The path to reducing emissions is much clearer than the path to efficiently scrub CO2 from the atmosphere. Also, scrubbing CO2 from the atmosphere gets harder and harder as CO2 emissions grow. There is some research to sequester CO2, but I don't think we have an ideas that are better than planting trees.
Antivaxxers are calm because they believe they are making the healthiest choice for their kids. Vaxxers are upset because they feel antivaxxers are just relying on the success of vaccinations to diminish disease prevalence and don't really have to worry about their kids running into the disease.
If I knew everyone else in the world was vaccinated, I might choose not to vaccinate my kid. It's a mostly unnecessary risk for my kid since they would be unlikely to encounter it in a completely vaccinated world. But that sort of thinking is horrible for public health.
Bioweapons are hard to deploy in a targeted fashion. Also, development of an antibiotic resistant bacteria that would be truly dangerous to a population requires great care during development not to kill those doing the development themselves. Also, I think we tend to overestimate the resources available to terrorists.
I still remember entering Horde territory on a PvP server for the first time trying to complete the baby Alliance warlock quests. It was a huge thrill, and I felt completely immersed. I had many other fun times in the game and seeing the other beautifully crafted zones, however, the time commitment I wanted to sink into the game to fully enjoy it couldn't be sustained. I had to quit for personal well being reasons.
And prokaryotic cells are much, much smaller than eurkaryotic cells. I think the mass of a eukaryotic cell is over 1000x the mass of a prokaryotic cell.
I've heard that the goal for many football players is not long term health but to get out there and play while the opportunity is there. Reducing inflammation works so that you feel like you can go out and play again without adequate recovery. When the average football player has only a few months for a few years to make their mark, playing through injury or pain is the goal rather than the proper recovery.
Which then makes sense for them in a way, but makes treating inflammation something that maybe isn't as important for the general population (as most of us are hopefully in it for the long haul)
Or generate and store excess energy during the day. I think the current challenge is that current energy storage solutions do not scale to the size of power plants?
Even the day storing may not be option, my home town chennai got a record rain in last one month with almost no sun for most of the days. Also the only thing that helped people are fossil fuel which is Candle and LPG stoves. The regular coal based thermal power was not there due to shutdown of plant as well as tranmission lines. LPG stove made people stay on first and second floor for two weeks with no need to come down.
I know I sound sarcastic but Tony Seba might find a solution by the year 2030: how to store energy to cover the needs of a city like New York(a city that never sleeps). He has been right on the spot regarding his previous predictions, right?
Do volunteer firefighters provide their own equipment as well? I could believe that most firefighters are volunteer. I would be surprised to hear that most firefighting was volunteer.
