News for hackers. Stuff that matters.
Re:WoSign Incidents Report Update [pdf] by tarancato on Saturday October 08, 2016 @06:19AM (#12666399)
So much money they are making and they can't hire anybody who can write English properly or write a PDF that is not composed of a handful of font faces and sizes.

I also find it funny they have fired the CEO (the PDF does not say he stepped down voluntarily) but he's the one sending that link to the mailing list. I call bs.

Re:WoSign Incidents Report Update [pdf] by hannob on Saturday October 08, 2016 @09:45AM (#12666911)
There are a lot of reasons to criticize Wosign. Lack of English skills isn't one of them.

I didn't realize this until I first visited China, but there are parts of the world where it's really hard to find people fluent in English. If you require people to be fluent in English in order to participate in running the Internet you're locking a large number of world regions out.

Re:WoSign Incidents Report Update [pdf] by AdmiralAsshat on Saturday October 08, 2016 @11:58AM (#12667368)
I wouldn't hold it against a Chinese company for not having a native English speaker. But I would hold it against them for not at least having a native speaker on retainer to proofread a document that they're about to send out to an international community. It just looks unprofessional.

And that's all it is, really. Stuff that just screams, "Did no one proofread this thing before sending it out?" Probably not. Because whoever wrote it was probably the most fluent person at the company.

---

FWIW, I have native-English speaking programmer friends who ask me to proofread their stuff. I don't mind. One is an amazing programmer, but his writing ability is somewhere around 9th-grade proficiency. The fact remains that being able to write correctly is considered a "bare minimum" quality in the professional world, and it doesn't matter if you wrote your own virtual machine in Assembly in your spare time--if you sound like a college dropout in your resume, they'll skip over you.

It is similarly difficult to inspire confidence in a CA when their "transparency report" sounds unprofessionally cobbled together.

Re:WoSign Incidents Report Update [pdf] by wbl on Saturday October 08, 2016 @09:49AM (#12666922)
Learn. You only need a handful of people to read the language in which 99% of all scientific publications are written in.

Reading knowledge of a language can be gotten fairly quickly.

Re:WoSign Incidents Report Update [pdf] by hannob on Saturday October 08, 2016 @10:35AM (#12667065)
This wasn't about reading knowledge, it was about writing knowledge. The original poster was complaining about grammar errors in their own publications. And even learning reading knowledge of a language that is totally different from your own isn't so easy. I spent quite some time trying to learn Mandarin.

Also out of curiosity: How many languages that are not related to your native language can you fluently read?

Re:WoSign Incidents Report Update [pdf] by aianus on Saturday October 08, 2016 @11:12AM (#12667195)
There are millions and millions of people in Canada and the US that are fluent in both English and Mandarin. Hire one of them.
Re:WoSign Incidents Report Update [pdf] by johnnyfaehell on Saturday October 08, 2016 @06:49AM (#12666469)
> So much money they are making and they can't hire anybody who can write English properly

If you're going to make fun of someone's English then you should probably write better English yourself. At the end of the day English isn't their first language and they'll probably very rarely have to use English. I think some slack should be given on this front.

Re:WoSign Incidents Report Update [pdf] by geofft on Saturday October 08, 2016 @07:46AM (#12666597)
> and they'll probably very rarely have to use English.

The CA/Browser Forum Baseline Requirements and the mailing list discussions all happen in English. The major root programs all use English as their language of communication, to the best of my knowledge. The SSL/TLS and X.509 specifications are in English. The major browsers and TLS stacks have technical documentation, code comments, and code review in English. mozilla.dev.security.policy is in English. The international language of scientific research (including cryptographic research) is in English. The CVE program is in English. All of these are reasons not only to have people who are fluent in technical English, but to make hiring such people a priority.

In particular, the inability to communicate precise, subtle technical concepts was very relevant to some of the problems here, like "You may not issue SHA-1 certs after this date" meaning the actual, calendar date of issuance and not the recorded validity period in the certificate. (There was also an element of malice, but it could have gotten sorted faster if communication were easier.) Even if all the others were in some other language, the CA/Browser Forum alone would be enough to make anyone who wants to be a CA (or an HTTPS client implementor) must make fluency in technical English a priority.

It is, of course, highly unfortunate that people from non-Anglophone countries are at a disadvantage here. In an ideal world we wouldn't have that disadvantage. But there doesn't seem to be a way around picking a language to be the scientific lingua franca.

Re:WoSign Incidents Report Update [pdf] by Normal_gaussian on Saturday October 08, 2016 @06:53AM (#12666474)
tarancato isn't making any money from these comments, so it seems reasonable that they are not using some form of proofreader.
Re:WoSign Incidents Report Update [pdf] by johnnyfaehell on Saturday October 08, 2016 @07:12AM (#12666518)
I am not bothered by their English or using a proof reader. I just think it's hypocritical to throw stones at people for not having good English when they don't operate in an English speaking market when yours isn't perfect either.

Also do you honestly think that was written by the business team, do you think the business team would have been able to properly edit a technical document in another language?

Re:WoSign Incidents Report Update [pdf] by cshimmin on Saturday October 08, 2016 @07:19AM (#12666532)
He's not throwing stones at people, he's throwing them at the company, WoSign. FWIW, I agree. They should have gotten (i.e. paid) someone to write a coherent document for this important communication.
Re:WoSign Incidents Report Update [pdf] by johnnyfaehell on Saturday October 08, 2016 @07:37AM (#12666578)
> FWIW, I agree. They should have gotten (i.e. paid) someone to write a coherent document for this important communication.

Seriously you'll be hard press to find a paid translator that can translate technical documents.

Also the document is actually reasonable coherent. Picking on the language level of the document over the technical content of the document seems kind petty.

Re:WoSign Incidents Report Update [pdf] by michaelt on Saturday October 08, 2016 @08:18AM (#12666697)
The CA Browser Forum puts out a lot of documents in english - often full of both technical terms and complex multi-layered clauses and subclauses.

You'd hope they'd have a good technical translator already on their payroll.

Re:WoSign Incidents Report Update [pdf] by uxp on Saturday October 08, 2016 @09:51AM (#12666928)
I'm capable of reading and writing a number of languages, but I'm not proficient at it. This also means that I probably have the writing level of a lower grade school child in those languages, and if I was to try and speak, I'd sound like I was mentally disabled since my vocabulary and general knowledge of the language is lacking.

Japanese is one. I've many times read comments written in Japanese in the Ruby language source code and understood their meaning, but there is absolutely zero ability for me to visit that country and be able to interact with anyone.

The author of this incident report is leagues more capable than I am in writing a report in a foreign language. They didn't insult my mother, or my dog, or call me names by accident. I don't see the justification in insulting their English.

Re:WoSign Incidents Report Update [pdf] by JohnTHaller on Saturday October 08, 2016 @08:59AM (#12666806)
WoSign owns Israel-based CA StartCom (from the shady event where WoSign bought Startcom, didn't disclose it, and started issuing invalid certificates through StartCom). Both operate in multiple English language markets.
Re:WoSign Incidents Report Update [pdf] by tarancato on Saturday October 08, 2016 @06:52AM (#12666473)
I don't speak English natively, and any corrections are welcome. On the other hand I don't run a multi-million business based on writing comments on Hacker News so currently hiring a PR person to proofread these comments is not within the boundaries of my budget.

WoSign runs a business that is basically based on trust, and Nigerian scammers have sent me PDFs that looked far more convincing and trustable than that one WoSign posted.