full-disclosure

Open Source and information security mailing list archives

Message-ID: <20140428211513.228b1e84@hboeck.de>
Date: Mon, 28 Apr 2014 21:15:13 +0200
From: Hanno Böck <hanno@...eck.de>
To: fulldisclosure@...lists.org
Subject: Re: [FD] Telegram authentication bypass

On Mon, 28 Apr 2014 11:17:31 +0200
jdiaz@...t.inteco.es wrote:

> This may allow
> an attacker leveraging this issue (e.g. by distributing a slightly
> modified client) to obtain almost full control of the victim's
> account.

I haven't read the details, but can you please explain how it is an
"attack" if I can control a user if I manage that he installs a
modified client?
I can do anything if a user installs a client I can modify. That's
no surprise and has nothing to do with the protocol in use.

I'm certainly not a fan of telegram's strange security protocol, but
this seriously sounds like strange FUD (haven't read the paper, maybe
it's just a joke or a fake).

-- 
Hanno Böck
http://hboeck.de/

mail/jabber: hanno@...eck.de
GPG: BBB51E42

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

_______________________________________________
Sent through the Full Disclosure mailing list
http://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives