Earlier quoted context omitted.
If you extrapolate my comment into points I wasn't trying to make, I think you'll find those arguments very easy to tear down. If that's a productive exercise for you, be my guest.
I don't really see the straw man here, but my larger point wasn't about this particular argument at all. Just the fickle commitment to the discussion.
Tox: secure messaging for everyone
111–120 of 214 posts
Re: Tox: secure messaging for everyone
#112Earlier quoted context omitted.
You don't actually seem to be using the logo anywhere, though. On your site you write that "I had (have) plans to write an Instant Messenger client with proper support for privacy. This was the logo concept for the project"[1], but this project does not actually seem to exist (at least not in any public manner). As such, why not just leave the logo of Tox in peace? Especially since it's a FOSS project with noble goal…
> As such, why not just leave the logo of Tox in peace? I have plans for it. It wasn't just an idle doodle.
Re: Tox: secure messaging for everyone
#113Re: Tox: secure messaging for everyone
#114Since you managed to kill the website: https://github.com/irungentoo/ProjectTox-Core Tox is a completely decentralized secure messaging service which aims to replace skype. It it still in heavy development. So far we have IM working almost perfectly but no completed GUI yet except for a basic ncurses interface used to test the core. For the detailed info on how everything works see: https://github.com/irungentoo/Proj…
Re: Tox: secure messaging for everyone
#115Oh, I see you helped yourselves to my Secure Chat logo - http://dribbble.com/shots/479881-Secure-Chat http://logopond.com/gallery/detail/165288 https://www.google.ca/search?q=secure+chat+logo - first page hit too Not cool at all, "cool guys around the world". -- (edit) Regardless of whether this was copied, over-inspired or independently conceived (but let's be realistic here), the generally accepted rule of the game…
Re: Tox: secure messaging for everyone
#116Earlier quoted context omitted.
Honestly, I don't see the concept being so unique and original that someone else couldn't have come up with it independently, and frankly the Tox logo has a much nicer balance (in the Tox logo, the person/keyhole works much better, whereas in yours it doesn't really work as a "keyhole" in my opinion) than the versions you linked. EDIT: The logo was originally made in /gd/ (4chan's graphic design board), and since the…
Cool story bro. However, these links seem to prove GP's claim: that his design has priority.
Re: Tox: secure messaging for everyone
#117Oh, I see you helped yourselves to my Secure Chat logo - http://dribbble.com/shots/479881-Secure-Chat http://logopond.com/gallery/detail/165288 https://www.google.ca/search?q=secure+chat+logo - first page hit too Not cool at all, "cool guys around the world". -- (edit) Regardless of whether this was copied, over-inspired or independently conceived (but let's be realistic here), the generally accepted rule of the game…
Both your logos might look nicer if the avatar moved up and to the left to make the chat bubble look more like a chat bubble.
Re: Tox: secure messaging for everyone
#118Unconvinced. * Lossless UDP? Is there a reason not to do TCP? * There is no way to know if the public key is genuine, so the system is very sensitive to MITM. * The key exchange is inadequate. Why not do DH if it's just to have session keys? * The system is very easy to brute force as the acknowledgement is based on a known plain text. This is very bad . A quick glance at https://github.com/irungentoo/ProjectTox-Core…
>Lossless UDP? Is there a reason not to do TCP? Hole punching. >There is no way to know if the public key is genuine, so the system is very sensitive to MITM. If you want to add someone you need their public key (their id) which is 32bytes (It's small because we use ECC instead of RSA). Unless someone somehow replaces the key (your id) when you give it to your friend the system should be secure. >The key exchange is…
I will give you a high level example of what he is talking about. your software displays a public key to perform encryption. what 'the NSA' can do is put a proxy (or use your isp) in between you and the person you are sending data to. Then they can pose as the person you are sending data to by hosting their own public key to both you and the person you want to send data to. now they can decrypt information that you send, and then encrypt it with their private key and send it to the other person. NOW THE NSA CAN SPY ON YOU USING YOUR APP.
man in the middle attacks can get much more complex than that, but this should help you understand what is going on.
If you are attempting to write security software you should really at least learn crypto AND networking. it seems like you have not accomplished either of these.