DuckSoft

> To bad the issue was never crawled to archive.org in the original repository. > That makes it sadly difficult to verify the statement of actually making them aware. Also...

# What an Honour! @signalapp just blocked me! # and @studentmain!   I think it fair to put here now: 

> > We sent the signal team a couple e-mails, privately informing them about our findings. After getting no response in a couple months, we submitted a github issue. Here...

> the Signal team is watching this thread, without actively participating in the conversation. Maybe, yeah. I just don't understand why they don't process the problem itself, rather than "process"...

> Is there a possibility that this is not a bug > its just a pre-preserved backdoor? I'd try my best to resist resorting to conspiracy, but... I don't know....

If you are designing a system whose functions include providing evidence, it had better be able to withstand hostile review. - Ross J. Anderson

DoHs using well-known `/dns-query` path can be probed and blocked. Making your own path can help - or just setup along with nginx and do a simple path rewrite. One...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I am DuckSoft from Qv2ray Developer Community and I prove my identity by GPG signing this message. My opinion is consistent with what is...

@sneak > Let the people who understand the subject speak. Stop making false claims when you are not at all familiar with the subject.

`cargo expand` shows that the code `impl_block_cipher_with_gcm_siv_mode!(Aes128GcmSiv, Aes128);` generates: ```rust #[derive(Clone)] pub struct Aes128GcmSiv { cipher: Aes128, } impl Zeroize for Aes128GcmSiv { fn zeroize(&mut self) { self.cipher.zeroize(); } }...