Medijski sadržaj
- Tweetovi
- Tweetovi i odgovori
- Medijski sadržaj, trenutna stranica.
-
When attackers compromise a browser they don't necessarily need to go deeper and escape the sandbox. They can stay within the sandbox and steal victims data by shutting down SOP and create UXSS. An innovative concept by
@itszn13@BlueHatIL#bluehatilpic.twitter.com/Y5Ry3Zgj1f
-
#FunFact even@gentilkiwi cannot remember all#mimikatz flags
#bluehatil@BlueHatILpic.twitter.com/0wRoCRolaU
-
"0days are expensive; mistakes are free" Excellent quote by
@n0x08@BlueHatILpic.twitter.com/3rJrLmLVTC
-
5/ and one exploit based detection rule to detect
@ollypwn exploit of the degenerate case (private key = 1)pic.twitter.com/w6K1FR5qIq
Prikaži ovu nit -
4/ Detecting rogue certificates with a trusted public key (with an idea stolen from
@gentilkiwi
)pic.twitter.com/inlR9NHS7Z
Prikaži ovu nit -
3/ Detecting non-standard base points (but standard a and b parameters)pic.twitter.com/EX1x1dn5Pt
Prikaži ovu nit -
-
For reference, "named curve" vs "specified curve"pic.twitter.com/OqZuQNHeu1
-
-
A tool to verify
#Tezos Bakers are actually paying their rewards https://twitter.com/tezosatl/status/1213066042429325314 …pic.twitter.com/pvPCvrPXb6
-
Some
#cryptocurrency exchanges take pretty wild fees on@tezos staking (source: https://mytezosbaker.com/ ) Caveat emptor!#Tezospic.twitter.com/Xb6hMN84Uu
-
In theory, rewards should be paid to you even if you switch bakers, but you need to ask Coinbase about their policy. FYI: according to
@mytezosbaker Coinbase takes 25% of your staking rewards, compared to 8%@FigmentNetworks used by@ZenGo.pic.twitter.com/In9WeuLy66
-
Seems like purchase is with
@Tronfoundation$TRX and not with TRC-20 of$USDT@justinsuntron ? @PhPremOfficial ?pic.twitter.com/f5LB9j9dj2
-
#Wireshark#ProTip : although the UI doesn't show#CurveBall related Curve Params yet (@WiresharkNews@Lekensteyn is working on it), you can use: tshark -r kudelski-vuln.pcapng -Y tls.handshake.certificate -O tls -ober.decode_unexpected:TRUE https://twitter.com/TalBeerySec/status/1219537211688996865 …pic.twitter.com/6BfzujYAob
-
-
The rule seems to assume Public Key (PK) is equal to Base Point (BP). This is very exploit specific. For example,
@KudelskiSec choose BP = PK/2 (and private key is 2).pic.twitter.com/wuaHi3Hmds
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
