[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#848695: marked as done (ITP: telegram -- Official desktop client for the Telegram instant messaging protocol)

Your message dated Mon, 19 Dec 2016 21:10:01 +0500
with message-id <[🔎] 20161219161001.fx6yrobrwivpyn5b@belkar.wrar.name>
and subject line Re: Bug#848695: ITP: telegram -- Official desktop client for the Telegram instant messaging protocol
has caused the Debian Bug report #848695,
regarding ITP: telegram -- Official desktop client for the Telegram instant messaging protocol
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
848695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848695
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: "Nicolas Braud-Santoni" <nicolas@braud-santoni.eu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

* Package name    : telegram
  Version         : 0.10.20
  Upstream Author : The Telegram Developers
* URL             : https://desktop.telegram.org/
* License         : GPL-3
  Programming Lang: C++
  Description     : Official desktop client for the Telegram instant messaging protocol

Telegram is a popular, multi-platform, open, instant messaging protocol,
which seems especially popular on mobile, but has a desktop client.

While the protocol probably shouldn't be relied on for confidentiality
[0,1], the UI pushes users towards insecure communication as the default,
and the developers have made quixotic attempts at arguing why their
protocol is secure rather than fixing it [2], I believe that there is
value in packaging Telegram rather than having users download and
install unsigned binaries [3].

I plan to maintain the package inside collab-maint.


Best,

  nicoo


[0] https://core.telegram.org/mtproto#general-description
[1] https://gizmodo.com/why-you-should-stop-using-telegram-right-now-1782557415
[2] https://core.telegram.org/techfaq#q-why-don-39t-you-go-for-a-standard-encrypt-then-mac-approach
    https://core.telegram.org/techfaq#q-do-you-use-ige-ige-is-broken
[3] https://desktop.telegram.org/

-----BEGIN PGP SIGNATURE-----

iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAlhYAr0ZHG5pY29sYXNA
YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z4zztD/4+xoHIcewrb5YcfBwgN18T
lyTEp/95AXxO3lKIC08Etg6R7Y4bzrOwV3MK/sYhcyNP41RE5A6wYGTLquNff7vY
LnmS4nwMMhrTaWe/voblkfnVCJs1Auzi6Xns21Sh+abiyHu2jaPk5Z8mfi1Wusrc
T8Ab4qMYW0CkfZlyCc7NjPhF8mIm8pZPyTakWYkRJarssfuqwR0ty6IuC6+Xs1cH
L60fNYzgkqc6CvnswC5+i7qzsJlIutCqTjpcyDN4NtwlzL1NUmpugpIhD1C+l96A
7leDB/v/6kjBrZoJ/VWJISkFRMIOcmSvUYHetIkf+Jd4KrpyccUR4lleRmhRkNCf
YOZpo9mNwZ6msAVLwgWjqxj3nnOSS1+S6ymyTZKeCRsikpC7aBgHguJ9YwcJbUUN
bpBuU9nQ6JbHsW1H/mgQzrAXw5P2TG/43N47+1PxFpMh6k4UAnQhsEJ9YjKDNcqz
HouSCnmuytyPQKm/OruVoAdI6R2oVMCAvcuMZv7Bg/5UjLd69T3TgZDJCfyd5LOa
YIZV2MZbK16PZTKomsYSQgP0nExlutAD2lynUGR32g44ygdKHZ6ze1Ag8NkVRN3/
AESadMu5Gy1Mm+fzU52IFPlTatZY/jrmFaGIThYoioCXQLhe80H9qek6rrG2feXG
7r0UQSu4rleI/fJsvo0kIA==
=ty8M
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Really, please read
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767418, and if, and only
if, both the GPL+OpenSSL and patched Qt issues are resolved then retitle
it to ITP. Closing this one.

-- 
WBR, wRAR

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: