SSL company not allowing secure passwords



  • I recently had an issue where I could not log into a website to manage my SSL orders. After doing some troubleshooting I found that the problem was only if I logged in via the header. More testing revealed that I could use the header to login if I changed my password to something without special characters in it. I notified support a week and a half ago. This was their response:

    Hello Bobby,

    This is a follow-up email in continuation of your following email that was escalated to our development team, they have informed us the following:

    We are not able to re-produce the issue but still we have one doubt(regarding javascript) so based on that we have fixed the issue. Please ask user to try now and if issue persist we recommend users NOT to use special characters like '(single quote), / (forward slash) , \ (backward slash) in their password.

    Feel free to write back to us if you have any further queries.

    Thanks and Regards,



  • @GigaBitWare said:

    we recommend users NOT to use special characters like '(single quote), / (forward slash) , \ (backward slash) in their password

    From an SSL vendor? Kindly name and shame so that we can all calmly go toward the exits.



  • I was trying to avoid naming them. They do allow the special characters, just not in the header log in form. I did try in two different browsers, not sure if windows 8.1 64-bit had anything to do with it. Although I did give them the exact specks even my old password (I was changing it while troubleshooting.) My current password has special charactors so I just use the login page instead.



  • Well, that is special...



  • Still reeks of danger, and should still be named so we can make sure we don't do business there.


  • Discourse touched me in a no-no place

    @flabdablet said:

    we recommend users NOT to use special characters like '(single quote), / (forward slash) , \ (backward slash) in their password

    Wow, you could have had some REAL Bobby Tables fun with that.


  • Discourse touched me in a no-no place

    @GigaBitWare said:

    we have one doubt

    I'd love to know the etymology of people using that word, because it's the wrong one, and I've seen it many times.


  • Discourse touched me in a no-no place

    @FrostCat said:

    I'd love to know the etymology of people using that word, because it's the wrong one, and I've seen it many times.

    I suspect the epicentre is in India; I've not seen anyone else get that one wrong.


  • Discourse touched me in a no-no place

    @dkf said:

    I suspect the epicentre is in India; I've not seen anyone else get that one wrong.

    Oh, absolutely. There's another Indian one about "tell" vs "say".

    I think it would be interesting to see a list of idiomatic wrongs in various languages. Just like you can tell a person who uses "doubt" in that way is probably Indian, I bet there's ways you could pinpoint a foreign speaker of German to a particular nationality by way of some word used only wrong by Americans, or Chinese-people-from-China could tell someone's Russian as opposed to anything else by a certain misused word.



  • @FrostCat said:

    I think it would be interesting to see a list of idiomatic wrongs in various languages. Just like you can tell a person who uses "doubt" in that way is probably Indian, I bet there's ways you could pinpoint a foreign speaker of German to a particular nationality by way of some word used only wrong by Americans, or Chinese-people-from-China could tell someone's Russian as opposed to anything else by a certain misused word.

    Another one in written usage is the omission of articles in English; it seems to be a largely Eastern pattern. AIUI (but please correct me if I'm wrong!), the CJK languages simply never had them to begin with.


  • Discourse touched me in a no-no place

    Might be. I've been told Russian's the same way.


  • Discourse touched me in a no-no place

    @tarunik said:

    Another one in written usage is the omission of articles in English; it seems to be a largely Eastern pattern. AIUI (but please correct me if I'm wrong!), the CJK languages simply never had them to begin with.

    Having done a lot of collaborating with many people over the years, every nation has its characteristic mistakes in how it uses English. For example, German speakers tend to do a good job overall but pick weird words occasionally and often mess up when to capitalise nouns, whereas Italians are usually flowery and have strange sentence construction habits (but they usually get capitalisation right). CJK natives are different; their written English is often actually quite good (if a little stilted) but they put the concepts behind it together oddly. (If they've lived for a few years in an English speaking community, that changes and they become very hard to spot.)

    Filed under: The perils of working at a big university…


  • Discourse touched me in a no-no place

    @dkf said:

    Having done a lot of collaborating with many people over the years, every nation has its characteristic mistakes in how it uses English.

    Yup. And I bet most popular languages have the same kind of thing: there must be, to go along with Engrish, Spangrish, Russish, and Germuntergrautenßßpanzerkraftwagenish[1].

    [1] come on, you know that the word's not that long in German but it should be.



  • @FrostCat said:

    There's another Indian one about "tell" vs "say".

    And "Revert back to me." I've pointed out previously that that particular one has been creeping into the vocabulary of native English speakers.


  • Discourse touched me in a no-no place

    Ugh. You should push back on that, hard. "Sorry, I don't understand what 'revert back to me' means. Did you mean 'reply to me?'"



  • @FrostCat said:

    Did you mean 'reply to me?'"

    When I did, I got told to stop being so silly about it and go and do whatever I was asked to do in the rest of the mail.


  • Discourse touched me in a no-no place


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.