Elk Grove Village plans to opt out of Cook County minimum wage law

1 Share
Elk Grove Village plans to opt out of a Cook County ordinance raising the minimum wage and requiring sick-leave time.
Read the whole story
Share this story

Pet expo begins at Arlington Park

1 Share
The 25th annual Chicagoland Family Pet Expo opened Friday and tuns through Sunday at Arlington Park in Arlington Heights.
Read the whole story
Share this story

Password Rules Are Bullshit

3 Comments and 19 Shares

Of the many, many, many bad things about passwords, you know what the worst is? Password rules.

Let this pledge be duly noted on the permanent record of the Internet. I don't know if there's an afterlife, but I'll be finding out soon enough, and I plan to go out mad as hell.

The world is absolutely awash in terrible password rules:

But I don't need to tell you this. The more likely you are to use a truly random password generation tool, like us über-geeks are supposed to, the more likely you have suffered mightily – and daily – under this regime.

Have you seen the classic XKCD about passwords?

To anyone who understands information theory and security and is in an infuriating argument with someone who does not (possibly involving mixed case), I sincerely apologize.

We can certainly debate whether "correct horse battery staple" is a viable password strategy or not, but the argument here is mostly that length matters.

That's What She Said

No, seriously, it does. I'll go so far as to say your password is too damn short. These days, given the state of cloud computing and GPU password hash cracking, any password of 8 characters or less is perilously close to no password at all.

So then perhaps we have one rule, that passwords must not be short. A long password is much more likely to be secure than a short one … right?

What about this four character password?


What about this eight character password?


Or this (hypothetical, but all too real) seven character password?

You may also be surprised, if you paste the above four Unicode emojis into your favorite login dialog (go ahead – try it), to discover that it … isn't in fact four characters.

Oh dear.

"💩".length === 2

Our old pal Unicode strikes again.

As it turns out, even the simple rule that "your password must be of reasonable length" … ain't necessarily so. Particularly if we stop thinking like Ugly ASCII Americans.

And what of those nice, long passwords? Are they always secure?


Of course not, because have you met any users lately?

I changed all my passwords to

They consistently ruin every piece of software I've ever written. Yes, yes, I know you, Mr. or Ms. über-geek, know all about the concept of entropy. But expressing your love of entropy as terrible, idiosyncratic password rules …

  • must contain uppercase
  • must contain lowercase
  • must contain a number
  • must contain a special character

… is a spectacular failure of imagination in a world of Unicode and Emoji.

As we built Discourse, I discovered that the login dialog was a remarkably complex piece of software, despite its surface simplicity. The primary password rule we used was also the simplest one: length. Since I wrote that, we've already increased our minimum password default length from 8 to 10 characters. And if you happen to be an admin or moderator, we decided the minimum has to be even more, 15 characters.

I also advocated checking passwords against the 100,000 most common passwords. If you look at 10 million passwords from data breaches in 2016, you'll find the top 25 most used passwords are:


Even this data betrays some ASCII-centrism. The numbers are the same in any culture I suppose, but I find it hard to believe the average Chinese person will ever choose the passwords "password", "quertyuiop", or "mynoob". So this list has to be customizable, localizable.

(One interesting idea is to search for common shorter password matches inside longer passwords, but I think this would cause too many false positives.)

If you examine the data, this also turns into an argument in favor of password length. Note that only 5 of the top 25 passwords are 10 characters, so if we require 10 character passwords, we've already reduced our exposure to the most common passwords by 80%. I saw this originally when I gathered millions and millions of leaked passwords for Discourse research, then filtered the list down to just those passwords reflecting our new minimum requirement of 10 characters or more.

It suddenly became a tiny list. (If you've done similar common password research, please do share your results in the comments.)

I'd like to offer the following common sense advice to my fellow developers:

1. Password rules are bullshit

  • They don't work.
  • They heavily penalize your ideal audience, people that use real random password generators. Hey guess what, that password randomly didn't have a number or symbol in it. I just double checked my math textbook, and yep, it's possible. I'm pretty sure.
  • They frustrate average users, who then become uncooperative and use "creative" workarounds that make their passwords less secure.
  • They are often wrong, in the sense that the rules chosen are grossly incomplete and/or insane, per the many shaming links I've shared above.
  • Seriously, for the love of God, stop with this arbitrary password rule nonsense already. If you won't take my word for it, read this 2016 NIST password rules recommendation. It's right there, "no composition rules". However, I do see one error, it should have said "no bullshit composition rules".

2. Enforce a minimum Unicode password length

One rule is at least easy to remember, understand, and enforce. This is the proverbial one rule to bring them all, and in the darkness bind them.

  • It's simple. Users can count. Most of them, anyway.
  • It works. The data shows us it works; just download any common password list of your choice and group by password length.
  • The math doesn't lie. All other things being equal, a longer password will be more random – and thus more secure – than a short password.
  • Accept that even this one rule isn't inviolate. A minimum password length of 6 on a Chinese site might be perfectly reasonable. A 20 character password can be ridiculously insecure.
  • If you don't allow (almost) every single unicode character in the password input field, you are probably doing it wrong.
  • It's a bit of an implementation detail, but make sure maximum password length is reasonable as well.

3. Check for common passwords

As I've already noted, the definition of "common" depends on your audience, and language, but it is a terrible disservice to users when you let them choose passwords that exist in the list of 10k, 100k, or million most common known passwords from data breaches. There's no question that a hacker will submit these common passwords in a hack attempt – and it's shocking how far you can get, even with aggressive password attempt rate limiting, using just the 1,000 most common passwords.

  • 1.6% have a password from the top 10 passwords
  • 4.4% have a password from the top 100 passwords
  • 9.7% have a password from the top 500 passwords
  • 13.2% have a password from the top 1,000 passwords
  • 30% have a password from the top 10,000 passwords

Lucky you, there are millions and millions of real breached password lists out there to sift through. It is sort of fun to do data forensics, because these aren't hypothetical synthetic Jack the Ripper password rules some bored programmer dreamed up, these are real passwords used by real users.

Do the research. Collect the data. Protect your users from themselves.

4. Check for basic entropy

No need to get fancy here; pick the measure of entropy that satisfies you deep in the truthiness of your gut. But remember you have to be able to explain it to users when they fail the check, too.

entropy visualized

I had a bit of a sad when I realized that we were perfectly fine with users selecting a 10 character password that was literally "aaaaaaaaaa". In my opinion, the simplest way to do this is to ensure that there are at least (x) unique characters out of (y) total characters. And that's what we do as of the current beta version of Discourse. But I'd love your ideas in the comments, too. The simpler and clearer the better!

5. Check for special case passwords

I'm embarrassed to admit that when building the Discourse login, as I discussed in The God Login, we missed two common cases that you really have to block:

  • password equal to username
  • password equal to email address

🤦 If you are using Discourse versions earlier than 1.4, I'm so sorry and please upgrade immediately.

Similarly, you might also want to block other special cases like

  • password equal to URL or domain of website
  • password equal to app name

In short, try to think outside the password input box, like a user would.

🔔 Clarification

A few people have interpeted this post as "all the other password rules are bullshit, except these four I will now list." That's not what I'm trying to say here.

The idea is to focus on the one understandable, simple, practical, works-in-real-life-in-every-situation rule: length. Users can enter (almost) anything, in proper Unicode, provided it's long enough. That's the one rule to bind them all that we need to teach users: length!

Items #3 through #5 are more like genie-special-exception checks, a you can't wish for infinite wishes kind of thing. It doesn't need to be discussed up front because it should be really rare. You must stop users from having passwords that equal their username, or aaaaaaaaaaa or 0123456789, but only as post-entry checks, not as rules that need to be explained in advance.

So TL;DR: one rule. Length. Enter whatever you want, just make sure it's long enough to be a reasonable password.

[advertisement] Building out your tech team? Stack Overflow Careers helps you hire from the largest community for programmers on the planet. We built our site with developers like you in mind.
Read the whole story
47 days ago
42 days ago
At my previous employer, they used to give you a prize (just a lolly) when you first started, if you could pick a password that passed the stupid rules restrictions on the first try. Hardly anyone ever did it, even though the rules were listed clearly!
Share this story
3 public comments
46 days ago
We need to check the last points (username, app name)
Milton Keynes, UK
48 days ago
True story: work wants to roll out Microsoft Office 365, and I was one of the first trial users. I got a post-it with an 8 character password from the IT grunt tapped to be the AD admin. As is my habit, I immediately changed the password with a random one created by a password manager. The password was 20 characters. The change password form accepts the new password and prints a happy "password changed!" message. I log out, then try to log back in; the login page then informs me that the maximum … *maximum* password length is 16 characters and rejects my login. Okay … truncate it to 16, maybe the change form cut it off. Login fails. Go back to IT grunt to get a password reset, get a new 8-character password. Login fails. Reset again. Be very careful copying down password, very careful entering it back in. Login fails.
So, it turns out that there is no length validation on Office 365 password change forms, and going over the 16-character minimum mentioned nowhere on the page will *permanently* lock your account. 👍
47 days ago
Why is there even an upper limit? If the password is properly salted and hashed then only the hash should matter.
47 days ago
From what I found, it is some backward-compatible dependency thing with Active Directory syncing, which Microsoft has not cared enough about to fix. Possibly something with early Windows versions storing passwords as reversible hashes, and definitions of the protocols for remote logins defining a now-too-short field for passwords. The limitation could have made sense in the early 1990s, but then got carried forward far too long, and we are still stuck with it 25 years later.
47 days ago
Ah, I can see how that would happen. In my experience, many of the problems with Windows can be traced to poor early implementation that was never (or becomes increasingly difficult to) fix.
48 days ago
Possibly the worst password rule is the one that demands you change your password on a regular basis. Either people will start writing down their passwords, or come up with a pattern that ensures their passwords are always easy to guess.
48 days ago
What's wrong with writing down passwords? A written copy is extremely useful, if you secure it the same way you do your money and credit cards, i.e. carry it in your pocket.
48 days ago
Point taken, wffurr. I was thinking more about the corporate environment which is where I usually see mad password rules like these. The number of times I have seen passwords on post-it notes, whichg are stuck somewhere convenient, is quite frightening.
48 days ago
That said, the best approach is to use a password manager to store randomly generated passwords. Of course, my current employer bans the use of password mangers.
47 days ago
Must change password every 21 days. Cannot reuse last 50 passwords. **These** rules make my passwords less secure than they could be. I have given up generating passwords that I can reasonably type that follow the rules. I mean, 21 days?!?
47 days ago
21 days? Ouch! The worst I saw was every 30 days, and I know a number of people using a combination on month and year for their password.
47 days ago
And the new password can only have (IIRC) one point of similarity with the previous one.
47 days ago
That's just painful. It's rules like that which are just asking everyone to write their password on the nearest available post-it note.
47 days ago
That's weirdly strict. We have a change every 90 days and you can't use your last 2 passwords. That's it. Simple enough to rotate a handful of passwords 4 times a year.
47 days ago
this one drives me crazy. the damn auditors eat password expiry up and are always pushing for less time. total bs.
47 days ago
There is a government personnel website I've used where (1) the average user logs in about 2x/year, (2) the password resets monthly.
43 days ago
The NIST guidelines link in the post also strongly recommend against arbitrary password expiration. I sent the NIST document to my corporate IT when they changed password expiration rules just recently. It hasn't impacted any change, but at least I tried to talk sense to power.
42 days ago
@WorldMaker: I'm impressed that you tried to talk sense, but the main problem with large corporations is that they tend to adopt a checkbox approach to these things. People have to prove that they are doing _something_ about security; no-one ever asks whether what they are doing is actually useful.
41 days ago
@expatpaul: Arguably as a software developer a part of my role is to evaluate and better the company's software. Even if that just means writing a ticket every few weeks to try to argue true industry best practices against fads and security theater. Of course, without a CTO title they don't have to listen to me, but I can hope they might at least read it. Even if they are hearing stupid crap from outside security consultants and terrible software vendors that should be destroyed for the betterment of the corporate world like Oracle. The only way we might see change is to keep talking sense to power and hope someone listens or promotes us until they have to listen.
41 days ago
As long as companies want to do business with companies the require SOC2, HIPPA, SOX, etc. (not to mention their own compliance BS), it doesn't really matter. At least NIST is on board.

Study Links Depression With Gut Bacteria Imbalance

1 Share

The future of depression treatment might be chilling in the dairy case. A study published this week in Nature Scientific Reports finds that beneficial bacteria commonly found in yogurt can help relieve depression-like symptoms in mice.

Over the last few decades, scientists have begun exploring the connections between our brains and all the microbes that live on and inside our bodies, and they've learned that those little microbes have an awful lot of power. Some studies have shown that bacterial imbalances can affect nervous system function, while others have suggested that people with bacterial imbalances may be more prone to anxiety and depression.

To test these hypotheses, researchers at the University of Virginia decided to begin at the overlap between the nervous system and mood: stress. Stress increases depression risk; it also affects, and is affected by, the function of the nervous system.

The scientists began by collecting a group of unlucky mice and subjecting them to a variety of intense stressors. Some were kept in crowded cages; others had to sit under strobe lights or listen to loud noises. Predictably, the stressful situations took a toll, and the mice began exhibiting what the researchers called “despair behavior.”

The researchers collected poop samples from the mice before and after the stress sessions, then ran genetic analyses to determine the species and quantities of bacteria living in each mouse’s gut. The results showed that the stress resulted in a pretty significant drop in a microbe called Lactobacillus—the same type of so-called "good" bacteria found in yogurt.

But the rodents’ despair would not prove permanent. The researchers began giving the mice small doses of Lactobacillus with their meals, and, over time, their symptoms resolved.

Lead author Alban Gaultier. Image Credit: Josh Barney | University of Virginia Health System

"This is the most consistent change we've seen across different experiments and different settings we call microbiome profiles," co-author Ioana Marin said in a statement. "This is a consistent change. We see Lactobacillus levels correlate directly with the behavior of these mice."

The team hopes to take their experiments into the human body next. Lead author Alban Gaultier said he has “big hope” that probiotics could someday augment or even replace side-effect–heavy antidepressant drugs. “It would be magical just to change your diet,” he said, “to change the bacteria you take, and fix your health—and your mood.”

March 10, 2017 - 10:30am
Read the whole story
Share this story

A New Food Delivery Service Caters to People With Digestive Disorders

1 Share

To make life easier for patients with digestive disorders, Epicured, a new meal delivery service spotted by The Mighty, provides subscribers with meals that are compliant with their treatment plans.

People with digestive disorders often have a hard time finding or cooking health-appropriate foods. Individuals with celiac disease—a genetic digestive disorder that causes harm to the small intestine—can’t eat gluten. Meanwhile, experts still don’t know what causes conditions like Crohn’s Disease or Irritable Bowel Syndrome (IBS), but research suggests that following a low FODMAP diet may improve symptoms.

Renee Cherkezian, a nurse, and Richard Bennett, an entrepreneur and former healthcare professional, launched Epicured in 2016. Other companies provide gluten-free meal plans, but Epicured bills itself as the only food delivery service that’s FODMAP-compliant, too. (For the uninitiated, FODMAP is an acronym for fermentable oligosaccharides, disaccharides, monosaccharides, and polyols—all short chain carbohydrates, found in dairy products, wheat, certain fruits, onions, sweeteners, and more.)

Epicured’s menu changes seasonally; current offerings include everything from baked lasagna to Thai green curry to Tikka Masala. Not only are these choices diverse, they’re all 100 percent low FODMAP and gluten-free. “Many of our customers have not been able to derive a lot of pleasure from food, and we want to give them back that ability,” Bennett told The Mighty.

Epicured’s services are currently only available in the New York metro area, but the company plans to expand to include other East Coast cities. (Check here to see if Epicured delivers to you.) Before placing an order, though, consult with a doctor to make sure the meal plans fit your individual health needs.

[h/t The Mighty]

March 6, 2017 - 3:00am
Read the whole story
Share this story

Colorectal cancer rare but rising among millennials, Gen X

1 Share

Digestive system anatomyDigestive system anatomyHey Paul Studios/Flickr

WASHINGTON (AP) - Colorectal cancer mostly strikes middle-aged and older people, but new research shows a disturbing rise in cases among young adults.

Tuesday's study by the American Cancer Society is a reminder that while this type of cancer is rare in the young, no one should ignore symptoms just because the person is a 20- or 30-something.

"We think these are very important findings," said cancer society epidemiologist Rebecca Siegel, who led the research. "We're not claiming they have a high risk of disease. It's just increasing rapidly."

It's a puzzle in what otherwise has been progress against the nation's third most common cause of cancer. There are about 135,000 new cases of colorectal cancer each year, the vast majority among people 50 and older. Fewer than 15,000 diagnoses are made annually in people younger than 50.

Overall, rates have been dropping in recent decades, by about 3 percent a year since 2003. That's thanks in part to screening tests such as colonoscopies that not only can diagnose tumors early but prevent them by removing precancerous growths. Such screening typically starts at age 50.

The cancer society has long known cases were rising among young people, but the study published Tuesday in the Journal of the National Cancer Institute took a closer look - and found rectal cancer is driving the problem.

Rates of rectal cancer are increasing by about 3 percent a year in 20- and 30-somethings, and by 2 percent a year among the 40- to 54-year-old age group, the study found. Colon cancer rates are rising by smaller amounts in those age groups.

In fact, someone born in 1990 appears to have double the risk of colon cancer and four times the risk of rectal cancer as the generation born in 1950, Siegel said.

"It appears as though the underlying risk of disease is increasing," she said.

No one knows why. Risk factors include obesity, lack of physical activity, a diet high in red or processed meat and low in fruits and vegetables, smoking, heavy alcohol use, having inflammatory bowel disease or a family history of colorectal cancer.

The new study confirms what Dr. John Marshall sees in his Georgetown University clinic, where a growing number of patients are well under 50 and he recently saw a a 17-year-old.

"It's a very serious problem," said Marshall, who directs Georgetown's Center for the Cure of Gastrointestinal Cancer. Few have traditional risk factors, he added, saying other suspects include changes in the protective bacteria that line people's digestive tracts.

Too often, younger patients aren't diagnosed quickly.

"If somebody comes in at 28 years of age with some rectal bleeding, most emergency rooms or primary care docs are going to say it's probably a tear, it's probably nothing," Marshall said.

Symptoms include blood in stool; changes in bowel habits such as diarrhea, constipation or narrowing of stool that lasts more than a few days; unintended weight loss; and cramps or abdominal pain.

Even before Tuesday's study, the cancer society had been set to review its screening guidelines this year. Marshall doesn't expect screening to be seen as practical for younger people.

Read the whole story
Share this story
Next Page of Stories