4 ms·
This is a bad point. The difference between using AES-128 and AES-256 from a code standpoint is trivial. The only explanation for this is either gross incompete
by restingrobot 7y ago
This is a bad point. The difference between using AES-128 and AES-256 from a code standpoint is trivial. The only explanation for this is either gross incompetence or malevolence. Personally I don't use Zoom, nor would I recommend its use for even personal conversation.
- dpeck 7y agothe difference is a copy and paste from an older StackOverflow post.
- restingrobot 7y agoUsing code without understanding its implications would fall in the gross incompetence category.
- AshamedCaptain 7y agoAnd my point is that this happens all the time. Natural selection seems to favor the type of company that would just copy&paste from SO (then spend their resources on some fancy viral marketing) instead of the one that would stop to think about it.
- catalogia 7y agoPeople shouldn't be surprised, but they should be upset.
- Igelau 7y agoAwfully big talk on a Friday!
- lukeschlather 7y agoHave you studied the performance implications of different key sizes on real-time video applications? A little bit of reading suggests AES-256 carries a significant performance penalty vs. AES-128. I would be keen to hear from someone who has tried it in real-world situations and can demonstrate AES-256 working well on e.g. low-end android devices/cheap laptops without issue. I use Zoom regularly. Their video works well. I would like to have AES-256 but also I suspect this is not a casual choice, and I'm not sure it's as clear-cut as you're assuming.