> The repository mentions [0] the Wassenaar agreement, and that I must consult with the laws of my country on whether I am allowed to import/use software which includes encryption algorithms developed in other countries.
> Wat?
> In this day and age 99% (OK, this number is exaggerated, but you get my point) of software includes some sort of encryption. For one, think about all the libs/apps which communicate over the Internet and use encryption libs to talk via HTTPs. Is mentioning The Wassenaar Arrangement [1] in terms of software even necessary nowadays?
> Linux, Windows, MacOS - all have encryption libs built in (at least on the kernel level). They have been made in various countries, yet they are used all over the world. Do they fall under the terms of The Wassenaar Arrangement?
I just tried it with the domain rakso.at and when I enter rakso.at. there is an htst error. Shouldn't it work because it is technically the same domain?
> Wat?
> In this day and age 99% (OK, this number is exaggerated, but you get my point) of software includes some sort of encryption. For one, think about all the libs/apps which communicate over the Internet and use encryption libs to talk via HTTPs. Is mentioning The Wassenaar Arrangement [1] in terms of software even necessary nowadays?
> Linux, Windows, MacOS - all have encryption libs built in (at least on the kernel level). They have been made in various countries, yet they are used all over the world. Do they fall under the terms of The Wassenaar Arrangement?
> --------
> [0] https://github.com/jukefoxer/Signal-Android/tree/feature/wa-...
> [1] https://www.wassenaar.org
It's also mentioned in the original signal repo.I guess they have their reasons to include it and the fork just left it there.