121–130 of 150 posts
And this is a perfect reminder that you should never try some crazy things on your only administrator account on your production machine. Had he test his point on a dummy account : delete account = problem solved
And this is a perfect reminder that you should never try some crazy things on your only administrator account on your production machine. Had he test his point on a dummy account : delete account = problem solved
And this is a perfect reminder that if you allow some crazy input in your system you will eventually get someone who inputs something crazy. Had Apple properly validated the input and accounted for this case or disallowed it entirely they could have avoided this. Don't mean to troll but there are two sides to every issue like this: blame the user or blame the developer.
Apple dropped the ball here by allowing a password to be set to something that could not be typed at the login screen.
The user was stupid for performing this experiment without an escape hatch.
Stating one does not exclude the other.
And this is a perfect reminder that you should never try some crazy things on your only administrator account on your production machine. Had he test his point on a dummy account : delete account = problem solved
And this is a perfect reminder that if you allow some crazy input in your system you will eventually get someone who inputs something crazy. Had Apple properly validated the input and accounted for this case or disallowed it entirely they could have avoided this. Don't mean to troll but there are two sides to every issue like this: blame the user or blame the developer.
This is clearly an input validation issue first and foremost, and we can blame Apple for that, but it's also a completely weird use case and obviously a non-standard path to password input given you don't have emoji keys on keyboards.
I don't expect average end users to know that unicode support in software is still iffy, but I would expect them to realize that having to bring up an alternate input dialog is deviating from computing norms. Doing weird things should trigger a red flag in everyone's heads that "maybe I shouldn't try this first on something I value". Doesn't even matter if it's a computer, you wouldn't try refueling your primary car with wine, despite it containing a plausibly similar sounding percentage of ethanol.
A client once had an issue where his account got compromised and everything pointed to having his actual login details leaked. His password was something like his username plus an assortment of random characters. It turned out that the system his account was on basically ignored everything after the 8th character, so that you were able to login with the username as the password. Also, during the early days of inline…
Would love it if there were some kind of markup standard that password managers could read to determine the site's password rules when generating strong passwords. I have the problem now with sites that don't tell you their password policy - I'll try several times to generate a password in LastPass and then end up with several entries for the same site, which I now need to inspect to determine which one is the one I…
We only run into trouble because sites incorporate silly requirements like "you must have at least one symbol, even if your password is 48 characters long." Fixing that really seems like the better and more attainable goal.
I have had something similar bite me, although mine was easily fixed. I used swedish (åäö) characters for my disk encryption password. This worked fine, until I did a dist-upgrade and had my boot keyboard reset to US QWERTY (using a custom swedish version of capewell-dvorak). The solution for me was to stick on LTS distros.
I'm pretty sure the standard US layout offers more than enough symbols to write an excellent password. I tend to prefer extremely long passwords/phrases over things that require stupid characters (had trouble with WiFi keys using the French "é" back in 2008, all my passwords are ASCII since)
And this is a perfect reminder that you should never try some crazy things on your only administrator account on your production machine. Had he test his point on a dummy account : delete account = problem solved
Well, really, it should just work or OSX should prevent this from happening in the first place. Emoji are common among non-technical users---exactly the market that Apple supposedly caters to---and why would anyone expect a non-technical user to know that using emoji in a password would be considered "crazy", without knowing the extensive legacy of pre-Unicode systems, the location of many emoji outside the Basic Mul…
Earlier quoted context omitted.
That's insanely insecure. Can't believe client side validation would be used for a login system other than as a first check
I still needed the password (or so I assume). It was just a first check that was stricter than it should have been.
Earlier quoted context omitted.
I have two books in my queue actually, and this is one of them. There are parts of my content-property model I'm not ready to share, but most of it has been structured into a cohesive framework of how I: 1. find niches 2. automate site creation 3. optimize w/ gpt (google publisher tag) I'm sorry to say I won't be releasing that first... The first is due within the next 12-14 days, after which it should take me 1-2 mo…
Automated site creation... what, you're taking some public domain content, loading it up with ads, then hoping it ends up higher in the SERP than the original source? How is this different than filling amazon with autogenerated kindle "books" made from Wikipedia articles?
If I have an idea (e.g. a "ES2015 to ECMA6" converter), I'd look for a library to do this (if there isn't an open source one, I'd consider building my own as a learning experience).
Setting up the webpage up (converter/form) is trivial since it's really just one page and a few settings.
The really cool part is I've built laravel commands to do the hard work for me. They can:
- buy domains based on a keyword search with some common regex-like patterns
- set up a git hook to continuously deploy to an AWS micro instance via codedeploy/CircleCI
- manage different adsense codes across properties
So, if you're wondering these are things that have utility. I'm optimizing the pains of setting up each site, though.
I do build adservers for a living, but never once have I created a crappy content-farm click-baiting blog -- they are the scourge of the internet >:{
[edit] lastly, I'm not sure if you have a problem with google ads (doubleclick/google publisher network) but I think they're pretty sensible in what they allow... no reasonable person would take issue with that.
Earlier quoted context omitted.
And this is a perfect reminder that if you allow some crazy input in your system you will eventually get someone who inputs something crazy. Had Apple properly validated the input and accounted for this case or disallowed it entirely they could have avoided this. Don't mean to troll but there are two sides to every issue like this: blame the user or blame the developer.
Can't we do both? Apple dropped the ball here by allowing a password to be set to something that could not be typed at the login screen. The user was stupid for performing this experiment without an escape hatch. Stating one does not exclude the other.
I don't backup my C:\ drive before I "experiment" with the cut & paste tool.
If you saw an emoji keyboard pop-up on your change password screen it would be natural to just assume that the OS was now accepting emojis in passwords.
Earlier quoted context omitted.
Can't we do both? Apple dropped the ball here by allowing a password to be set to something that could not be typed at the login screen. The user was stupid for performing this experiment without an escape hatch. Stating one does not exclude the other.
You're assuming the user thinks they are performing an "experiment". When I use core OS functionality I don't think I'm "experimenting", I'm using the system. I don't backup my C:\ drive before I "experiment" with the cut & paste tool. If you saw an emoji keyboard pop-up on your change password screen it would be natural to just assume that the OS was now accepting emojis in passwords.
"I wanted to check if it's possible to use emoji in a password for my Account on OS Yosemite."
You're correct in general, but in this particular case they clearly saw this as something that might not work. They just didn't anticipate how badly "not work" could go.