Earlier quoted context omitted.
Hi, great point. Currently, users have to use their phone numbers to login. However, user's phone number is encrypted in the db. To ensure that everyone's comfortable with it, we're adding a new feature which doesn't require the user to login.
This worries me. What exactly do you mean by encrypted in the DB? If you actually mean hashed using a one-way function, it would be very easy to hash every possible phone number (there are not that many) to build a lookup table to deanonymise your users instantly. Even if you individually salt each hash it would not take very long at all to find the phone number for each entry. If you do mean encrypted, then authorit…
'Hush,' anonymous messaging app from developers in Myanmar
21–30 of 51 posts
Re: 'Hush,' anonymous messaging app from developers in Myanmar
#22Re: 'Hush,' anonymous messaging app from developers in Myanmar
#23So then it's not anonymous, only pseudonymous.
Re: 'Hush,' anonymous messaging app from developers in Myanmar
#24I got autostart video and audio ads that you can't pause :( And they repeat.
Re: 'Hush,' anonymous messaging app from developers in Myanmar
#25Earlier quoted context omitted.
Hi, great point. Currently, users have to use their phone numbers to login. However, user's phone number is encrypted in the db. To ensure that everyone's comfortable with it, we're adding a new feature which doesn't require the user to login.
This worries me. What exactly do you mean by encrypted in the DB? If you actually mean hashed using a one-way function, it would be very easy to hash every possible phone number (there are not that many) to build a lookup table to deanonymise your users instantly. Even if you individually salt each hash it would not take very long at all to find the phone number for each entry. If you do mean encrypted, then authorit…
You can't get around this problem unless you invent magic psychic computers. What is the point in finding every possible flaw with security here? There is a gradient of complexity, the time it takes to break these things. Currently, everything that exists is susceptible to being broken, misused, or modified.
If you assume that your attackers know everything, and have the ability to immediately find and apply that knowledge, then yes, it can seem scary. But I tend to think that the more capacity a person has to do, it's really just a bigger intellectual burden.
Re: 'Hush,' anonymous messaging app from developers in Myanmar
#26Great idea, but I don't get why they are based in Myanmar. This is almost asking for trouble from authorities. For something whose direct purpose and sales pitch is to do something that an authoritarian government is against, I would have based the entire company outside the country.
Exactly what I was wondering. What is registering the company in Singapore going to do when the police/military/whoever come to your door?
Re: 'Hush,' anonymous messaging app from developers in Myanmar
#27Earlier quoted context omitted.
Hi, great point. Currently, users have to use their phone numbers to login. However, user's phone number is encrypted in the db. To ensure that everyone's comfortable with it, we're adding a new feature which doesn't require the user to login.
The minimum I would consider responsible is 1. Use a hashcash style proof of work mechanism to register account. The server send a challenge and have the client compute a nonce under the difficulty. This could be turned to take an average of seconds to minutes on your median users device. This isn't a long term solution because eventually an attacker will realize that they can use more powerful machines to create syb…
Re: 'Hush,' anonymous messaging app from developers in Myanmar
#28Re: 'Hush,' anonymous messaging app from developers in Myanmar
#29Re: 'Hush,' anonymous messaging app from developers in Myanmar
#30Earlier quoted context omitted.
This worries me. What exactly do you mean by encrypted in the DB? If you actually mean hashed using a one-way function, it would be very easy to hash every possible phone number (there are not that many) to build a lookup table to deanonymise your users instantly. Even if you individually salt each hash it would not take very long at all to find the phone number for each entry. If you do mean encrypted, then authorit…
Yes, it is possible to match a phone number to a hash. (We are also looking at ways to make it more secure. If you have any suggestion, please let us know.) However, hushes are not connected with the phone number, we created unique token for our user when the hush is created. We needed phone numbers for our upcoming features. The newer version which won't need phone number to login is on its way.
> The newer version which won't need phone number to login is on its way.
So which is it? new features need the phone number but the new version won't require it? Are you gonna ask users for permission to use their phone number to access the new features? Will users who prefer their anonymity be able to interact with users who surrender their identification?
Isn't the unique token good enough?