Probably just reorder ciphers to prioritize chacha and des3.
-
-
-
3DES doesn't seem like a good idea! What about durable data?
- 1 more reply
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Step 1 would be to understand the conditions and cost of how AES would be practically broken as stated in that hypothetical research
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Step 2: don’t naively fall back to securing data using only access control if access control is also susceptible to the same AES breakage
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Step 3: check your IR/DR plans for cost benefit trade offs of keeping at-risk parts of your business online (write a plan if you don’t have one)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
All I’m sure of is that 90% of the time would be trying to determine what dependencies I now need to be worried about.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Probably move to a small island and raise sheep.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
First reaction: obfuscate to buy time
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
1. Disable AES cipher suites for TLS 2. `sio.Config{ CipherSuites: []byte{sio.CHACHA20_POLY1305}, }` 3. New release + security advisory telling users to do a SSE-C copy for existing objects 4. Hoping that others have a backup plan, too...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.