Yes

The millions of issues it has are the dollars he's not getting because he hired shitty devs.

"Moral Decisions", such as whether it's right to shoot up a school or not.

Our Federal Government is invested with tens of thousands of people who's job is to suck the fun out of everything.

The terminology being used is intentionally misleading.

The way its being said, most people who aren't that interested think its one single continuous flight, which is impressive.

There really isn't anything particularly impressive about this once you take that out of the equation.

Voyager was impressive. https://en.wikipedia.org/wiki/...

IT actually DID fly around the world without stopping, and it did the entire flight in 9 days, and they didn't stop to take breaks to avoid weather, they flew AROUND a Typhoon FFS.

This solar powered aircraft is more like a training run for one someone actually wants to do it properly.

The amount of effort it takes to do proper password handling versus the amount of effort it takes to just store one long enough to authenticate a user is so little different that treating them differently just shows a lack of knowledge about security in general.

Sending a clear text password for 'recovery' tells me that you didn't even bother to hash it ... that is NEVER AN ACCEPTABLE PRACTICE. If you think it is, or if someone treats it like it is, it shows you that they aren't capable of treating the different bits of data at different security levels since the extra 3 lines of code to hash the password for safer storage was apparently too much for them.

If you(they, whoever) care so little about the password that its not hashed, then its not worth having a password for in the first place. On modern processors, even doing hashing in ASSEMBLY is not a ridiculous task, every other higher level language has a library that does it in one function call in most cases.

There is no excuse that justifies storing a password in clear text. Ever.

Yes.

People who think they have a clue and are clever ... then decide to share their awesomeness and cleverness with others in a way that makes us all worse off ... yes, that makes me angry.

But hey, you go ahead and deflect. No sense in acknowledging the problem and doing something about it, you go ahead and pretend you've done nothing wrong and I'm the bad guy for pointing out how you're just as stupid as the article you're replying to ... but you don't even realize it or why, and you're bragging about your poorly thought out methods.

You think you know what your doing and don't, and on top of that you've decided to attempt to corrupt other people with your broken methods. You are the definition of a security problem.

You haven't been developing web apps very long, have you?

Steps 5 and 6 are horrible from a UX perspective and actually lower security a tiny bit.

By emailing out a single use password you make it possible for someone to eaves drop on the email train and login to your site using the single use password that you sent over email ... in clear text, over a system that may end up easily being stored on disk and snoop-able on many computers.

There is absolutely no reason to email them the password, you've already verified the email address is viewed by the user, doing it again just exposes that information to other people who may not know the users 2 security questions, but do already have access to the users' email.

You've effectively made your security questions useless if someone hacks the email account in the first place, which is often the case before using that to spider out and discover other services the user has. (You check the users sent/inbox/archive for emails from certain email addresses that are used by various services and can quickly tell the user does use specific services.)

Emailing a password is ALWAYS BAD PRACTICE.

ALWAYS.

Did you hear me? ALWAYS.

When you think you've figured out a way to make it 'safe'. Jab an unsharpened pencil in your eye as punishment and remember: ITS ALWAYS A BAD IDEA TO EMAIL PASSWORDS.

I'll go ahead and not bother pointing out how bad of an idea 'pre-defined' security questions are at this point, seems like you probably need to do some brushing up one security practices from someone who knows a bit about what they are doing. FFS, there are frameworks for every major web dev environment for user auth recovery. You shouldn't even be rolling your own.

Really? Sliden'Joy?

Their first action should be hire a marketing guy who will probably have them change the name lest it be automatically banned by various internet filters as a sex toy.

Apple backs up my passwords with an encryption key which is also protected by a separate password.

Apple CAN NOT read my passwords, so they can not share them.

Not sure about Google, but I hope it does the same.

Microsoft is uploading passwords clear text or in some other equally dangerous form thats decryptable so they can be shared.

Some discoveries. Very slowly. With very limited flexibility and substantially reduced spinoff benefits.

And at a trivial fraction of the price-tag. If the Mars-mission roboticists had the same budget as it'd take for a good manned mission, things might look very different.

Strange, but I'm finding I agree with this.

Fortunately, when it comes to public policy, everyone's opinion is of equal worth.

I think it's safe to say that in any SHTF event, it's the people who believe themselves to be smart who will suffer the worst.

What's sad is that UOP really could have done it! If they offered actual counseling guidance, and curricula that didn't just suck, and made sure that their clients passed classes with rigor, they could have *easily* made a profitable college with good reviews and earned trust.

Instead, they violated that trust, and probably deserve to be shut down.