Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security problem #13

Closed
libora opened this issue Jun 4, 2014 · 7 comments
Closed

security problem #13

libora opened this issue Jun 4, 2014 · 7 comments

Comments

@libora
Copy link

libora commented Jun 4, 2014

Hi, file "config" in folder "tdata" contains the login information and password for proxy in an unencrypted form. It can be very big safety problem especialy for portable version!

@telegramdesktop
Copy link
Collaborator

We can't encrypt this data in such way, that no one will have access to it, as long as we don't use password-protected launch of the application. But we can still encrypt it with some generated and saved key, so that it won't be plain text. Is that what you are talking about?

@sullivanmatt
Copy link

You might be able to leverage the Windows CryptoAPI to have it store the credentials on the application's behalf.

@libora
Copy link
Author

libora commented Jun 4, 2014

Yes, that's the way, do not use a plain text. Generated key would be unique
for each instance of application.
Dne 4. 6. 2014 21:10 "telegramdesktop" notifications@github.com napsal(a):

We can't encrypt this data in such way, that no one will have access to
it, as long as we don't use password-protected launch of the application.
But we can still encrypt it with some generated and saved key, so that it
won't be plain text. Is that what you are talking about?


Reply to this email directly or view it on GitHub
#13 (comment)
.

@edmundlaugasson
Copy link

There is some discussion about Telegram security issues and also one master thesis from September 2015 available talking about Telegram protocol security issues. It would be good if Telegram would rely on proven free and open-source encryption protocol(s) and not reinvent the wheel. There are some competitive alternatives, e.g. Zyptonite, Wire, Tox, etc. It would be good to see comparison table about security features these programs have and compared with Telegram Desktop. Here is one secure messaging comparison table - unfortunately looks like Telegram isn't the securest one.... There is yet another interesting solution - Maidsafe. I really hope that Telegram Desktop will benefit from all of them and offer really secure solution (preferally built-in).

@edmundlaugasson
Copy link

One more idea regarding secret chat - using telegram.me mechanism I would propose to make possible to create link which will directly start secret chat. E.g. https://telegram.me/secret/YourUsernameHere

@john-preston
Copy link
Member

Proxy settings are encrypted for a long time now.

@github-actions
Copy link

github-actions bot commented Mar 9, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants