Recent submissions

Comment · 12 years ago
If your goal is just to producing quality papers, this is perfectly great. If your research involves systems and implementations, it sucks to have to write every bits of code yourself. I don't think CS research is just about theory, at least not the line of research I am doing, I am all about making it readily available to others to use.
Comment · 13 years ago
I think he literally meant the CVS given the age of Simon... lol
Comment · 13 years ago
I don't, but I do review papers for people that I don't know if they have a good reputation.
Comment · 13 years ago
Well, I do agree that students can have different quality, and we shouldn't discriminate Indian students. But the problem is that enough Indian students have made bad reputation for all Indian students here (U.S), and to avoid future loss (time and effort of the faculties), we just start to reject any Indian students (at least in my own circle).
Comment · 13 years ago
I used to think if it's IEEE or ACM, they are ok (not good) to publish. Nowadays, I am not so sure after seeing a bunch of low quality "international" conferences in Asian especially in India. ACM seems a little better than IEEE...

Now my rule is to only publish in conferences that I know or are well known in the field....

Aslo reject any requests to serve as a TPC or reviewer for conferences from this region..The papers are normally low quality and waste of my time to read...

Comment · 13 years ago
That's what I am doing for sure now.
Comment · 13 years ago
well, if someone causes you significant lose, will you turn down a norch? That's why we are bashing on them as they are making BS claims about how secure their protocol is.
Comment · 13 years ago
I actually have a theory that this is all a scam... the person who found the bug is actually the authors (or a friend) of the Telegram protocol. They published the security issue and reward themselves so that 1) they don't have to pay anyone else; 2) they get good publicity by doing this; 3) shut others up up front as this is really a very easy bug to figure out (a few others hinted the possibility as the key exchange is unautenticated DH, which is bound to flaws like this)
Comment · 13 years ago
The same reason as why Google provide Gmail for free, 1) to get a huge user base (fame = money, in today's internet world; 2) get a hold of user data
Comment · 13 years ago
Are you trolling or for real? 1) Telegram is NOT open soure. 2) OTR has been around for years.
Comment · 13 years ago
Telegram's contest itself is meaningless regarding the security of its protocol (as others explained in details). Finding bugs such as this deserves 200k more than anything else
Comment · 13 years ago
It's simple unauthenticated Diffie-Hellman key agreement, which is known for MITM attack. Yes, you ask A to accept B's identity upon key exchange, but to what extend A would know B is really B not the server playing along? A plausible method would have A and B exchange certificates separate from the Diffie-Hellman key exchange process, and use those as the identity verification mechanism.
Comment · 13 years ago
unauthenticated Diffie-Hellman key agreement is known for MITM attack.
Comment · 13 years ago
This is like putting messages encrypted with ANY encryption algorithm, and ask people to guess the key. This has nothing to do with whether the communication protocol is secure or not.
Comment · 13 years ago
The Math PhD who designed the should write the protocol up as a paper, submit to top conferences like CCS and S&P. And he will see how badly the reviewers will dump on his protocol.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton