4 ms·
Thank you for feedback! 1) Yes, we are planning to add more sounds. We have 5 different melodies for now (in Settings), but we'll try to add more and also add
by cifrasoft 11y ago
Thank you for feedback!
1) Yes, we are planning to add more sounds. We have 5 different melodies for now (in Settings), but we'll try to add more and also add an option for custom soundtrack as well.
2) The sound technology is sort of acoustic watermarking. It is based on multicarrier spread spectrum and it uses simple masking mechanism to hide behind host audio signal. It should be quite robust in various noise scenarios and multipath propagation (although every system has limitations)
3) Did you enable 'encryption' in settings? For web-test do not turn on 'encryption' in app settings. If you enable encryption the decoder shall detect wrong sequence (even if your password is blank). We use it to protect our acoustic channel. If an adversary will try to intercept your 'encrypted' acoustic signal he/she will not be able to decipher it and even know if the encryption is enabled or disabled. On the other hand, SoundLogin has internal error check mechanism - probability that the decoder will come up with wrong number because of channel noise is less than 10^-10.
- digital_ins 11y agoYes! I was using it with encryption on. I was playing around with it a little bit. The digital acoustic watermarking idea is awesome. Rather than have a weird buzzing noise, overlaying digital information over these codes is great. If you've got enough traction, you should get a US corp built, because this is a trust-based product (right?). Having an OOO company is a little scary for US users.
- cifrasoft 11y agoThank you, digital_ins. Yes, I know it's scary. If we get some traction - we'll probably convert the SoundLogin project to open-source. We are already talking with potential backers. I think open-source is the best route for trust-based product.