Discover and read the best of Twitter Threads about #SPECTRE
Most recents (15)
[BREAKING] A chiral aperiodic monotile finally discovered!
[速報] 鏡像なしの非周期モノタイルが発見される。
それも前回のTile(1,1)にマッチングルールをつけた形とな！辺を変形できるのでデザインしがいがありそう
何に見える？身近な何かに見立てみよう！
#aperiodic
[速報] 鏡像なしの非周期モノタイルが発見される。
それも前回のTile(1,1)にマッチングルールをつけた形とな！辺を変形できるのでデザインしがいがありそう
何に見える？身近な何かに見立てみよう！
#aperiodic
早速亀の辺を曲げて描いてみました
Now, I am curved!
Now, I am curved!
もっと変形させたら変な妖怪が出てきました
Today's Twitter threads (a Twitter thread).
Inside: The real scandal is overclassification; The Australian Chokepoint Capitalism Tour; and more!
Archived at: pluralistic.net/2023/01/30/i-c…
#Pluralistic 1/
Inside: The real scandal is overclassification; The Australian Chokepoint Capitalism Tour; and more!
Archived at: pluralistic.net/2023/01/30/i-c…
#Pluralistic 1/
The real scandal is overclassification: I'd explain it, but I'd have to kill you.
2/
2/
The Australian Chokepoint Capitalism Tour: Brisbane, Melbourne, Sydney and Canberra (twice!).
3/
3/
Merci @Libertadsolidar pour cette nécessaire mise au point concernant la lunaire PDL @FranceInsoumise.
#pasunpartipourreleverlautre en matière de #prévention #santépublique.
La fameuse #triplémie #VRS #sarscov2 #grippe n'est plus un #spectre mais une #réalité.
1/
#pasunpartipourreleverlautre en matière de #prévention #santépublique.
La fameuse #triplémie #VRS #sarscov2 #grippe n'est plus un #spectre mais une #réalité.
1/
Dans les 13 personnes de mon cercle rapproché (France entière) :
🔹2 sont en isolement total pour éviter une contamination avant une opération planifiée de longue date sur 🦀
🔹1 ado est remis sur pied a priori sans #séquelle mais laisse son bp au tapis
🔹ma nièce (7 ans et
2/
🔹2 sont en isolement total pour éviter une contamination avant une opération planifiée de longue date sur 🦀
🔹1 ado est remis sur pied a priori sans #séquelle mais laisse son bp au tapis
🔹ma nièce (7 ans et
2/
a minima 4 infections) est hospitalisée.
Sur cet échantillon cela fait 15% de malades.
Poursuivre sur les #mythes du #covidismild #vivreavec devient de jour en jour plus criminel, surtout sachant que sur #BQ11 plus aucun AC monoclonal avec tout ce que cela induit pour les
3/
Sur cet échantillon cela fait 15% de malades.
Poursuivre sur les #mythes du #covidismild #vivreavec devient de jour en jour plus criminel, surtout sachant que sur #BQ11 plus aucun AC monoclonal avec tout ce que cela induit pour les
3/
En novembre 1924 les ouvrières des conserveries de Douarnenez commence une longue grève, la grève Penn Sardin
Grève magnifique que je vous raconte !
Grève magnifique que je vous raconte !
1)Depuis l’invention de la conserve en 1820, une partie du littoral breton est tournée vers la pèche et la conserve, avec une répartition bien genrée des taches, les hommes en mer, les femmes à l’usine. (tableaux Mathurin Meheut)
2)les conserverie poussent comme des champignons sur tout le littoral breton, 160 conserveries à la fin du siècle et près de 14 000 ouvrières, des Penn Sardin (tête de sardines) comme on disait.
1. voglio rispondere a chi mi dice che l'assassinio di #Regeni sarebbe un complotto dei servizi UK a danno dell'#Italia e dell' #ENI, perché questa tendenza nazionale a NON guardare mai quello che abbiamo davanti e a guardare sempre quello che c'è dietro, mi manda ai matti
2. questa tendenza nazionale a NON guardare più i FATTI che abbiamo davanti e a cercare sempre oscure macchinazioni che ci potrebbero essere dietro, ci sta trasformando in quella povera gente che vive nei regimi e crede che tutti i loro guai siano dovuti al *nemico*
🐙Genesis of the OSS
The Office of Strategic Services (OSS) was a wartime intelligence agency of the United States during World War II, and a predecessor to the Central Intelligence Agency (CIA).
ibiblio.org/hyperwar/USG/J…
The Office of Strategic Services (OSS) was a wartime intelligence agency of the United States during World War II, and a predecessor to the Central Intelligence Agency (CIA).
ibiblio.org/hyperwar/USG/J…
The OSS was formed as an agency of the Joint Chiefs of Staff (JCS)[3] to coordinate espionage activities behind enemy lines for all branches of the US Armed Forces.
Other OSS functions included the use of propaganda, subversion, & post-war planning.
ibiblio.org/hyperwar/USG/J…
Other OSS functions included the use of propaganda, subversion, & post-war planning.
ibiblio.org/hyperwar/USG/J…
The organization was developed with British assistance.
Until some months after Pearl Harbor, the bulk of OSS intelligence came from the UK.
British Security Co-ordination (BSC) trained the first OSS agents in Canada.
ibiblio.org/hyperwar/USG/J…
Until some months after Pearl Harbor, the bulk of OSS intelligence came from the UK.
British Security Co-ordination (BSC) trained the first OSS agents in Canada.
ibiblio.org/hyperwar/USG/J…
1.So, ages ago I did an enormous amount of research in an attempt to convince folks I admired to not take Jeffrey Epstein’s 💰or collaborate with him. Background/prior thread: bobbin.herokuapp.com/thread/1164745…
last tweet:
last tweet:
2.But first: a prolly silly attempt to offer a bias & conflict check. It is crushing to me how many men (& institutions) I like & admire are featured in these links. Thus, I’m sure who I call out specifically evidences these biases?
3 In terms of conflicts: sharing this completely conflicts with my self interest, but I guess this is overridden by a naïve attachment to the idea of justice & progress—and an expectation that these men & institutions stop obfuscating & do better NOW.
Or my stupidity? Or trauma?
Or my stupidity? Or trauma?
Speculative Side-Channel Attacks is misleading terminology and usually used incorrectly. We should all avoid using it and @intel, you should avoid using it too. Not only because it is misleading, but because it hinders successful communication on mitigations.
Let me elaborate:
Let me elaborate:
A side-channel attack uses measurements of side effects to gather enough *meta data* (power consumption, runtime, cache state, etc) to *infer* secret information.
#meltdown #spectre #zombieload and related attacks and variants do not leak meta data. They leak the actual data.
#meltdown #spectre #zombieload and related attacks and variants do not leak meta data. They leak the actual data.
There is no need to infer secret information from meta data, there is no meta data involved. Hence, they are *no side-channel attacks*.
"But they use flush+reload". Sure, but that doesn't make the attack a side-channel attack. Let's assume the following:
"But they use flush+reload". Sure, but that doesn't make the attack a side-channel attack. Let's assume the following:
From what I understand, the latest #OpenBSD vs #Intel thing went a little bit like that:
- OpenBSD: Can we be a part of this rumored Intel bug embargo?
- Intel: No. Go away.
- OpenBSD: Can we be a part of this rumored Intel bug embargo?
- Intel: No. Go away.
- OpenBSD: dev do their homework, fix FPU bug, publish patch.
- Theo (at @BSDCan): we are worried, we don't have access to info. Please help us.
- Intel: publishes official advisory: intel.com/content/www/us…
- Theo (at @BSDCan): we are worried, we don't have access to info. Please help us.
- Intel: publishes official advisory: intel.com/content/www/us…
Now everybody and their dogs are going crazy over #OpenBSD developpers doing their jobs , correcting stuff and "violating"an embargo... That they were *never* a part of. Because Intel did not want them to receive information!
Thread time! Why can't they just quickly patch #meltdown or #spectre and push out another cpu? Why could it possibly take years? Why don't they use AGILE or x/y/z? Lots of reasons:
(note: my goal is not to criticize chip manufacturers - it's to defend the constraints they have)
(note: my goal is not to criticize chip manufacturers - it's to defend the constraints they have)
Let's start with a standard software product many are familiar with and work off that. First, every time you hit 'build' it's called a 'stepping', costs millions of dollars & takes several months. If you want a profitable product, you may only get 10 chances to press 'build'.
On top of that, half those 'builds' are not 'full layer steppings' meaning you can't change any logic gates, just how they're connected. Even with a full layer stepping you can't shuffle stuff around anywhere like you can with library files and whatnot.
Here's my layman's not-totally-accurate-but-gets-the-point-across story about how #meltdown & #spectre type attacks work:
Let's say you go to a library that has a 'special collection' you're not allowed access to, but you want to to read one of the books. 1/10
Let's say you go to a library that has a 'special collection' you're not allowed access to, but you want to to read one of the books. 1/10
You go in and go to the librarian and say "I'd like special book #1, and the Sue Grafton novel that corresponds to the first letter of page 1 of that book." 2/10
The librarian dutifully goes and gets special book #1, looks at page 1, sees 'C', and also grabs 'C is for Corpse', and comes back to the desk, but does not show you the books. 3/10
Here are a few insights on the #Meltdown and #Spectre vulnerabilities based on my recent @RANDCorporation research. /1 rand.org/pubs/research_…
First, this is yet another reminder that vulnerabilities can last a long time (our data showed vulnerabilities lasted 6.9 years before being publicly disclosed) and have a low chance of being discovered (5.7% per year). /2
Explainer on #Spectre & #Meltdown:
When a processor reaches a conditional branch in code (e.g. an 'if' clause), it tries to predict which branch will be taken before it actually knows the result. It executes that branch ahead of time - a feature called "speculative execution".
When a processor reaches a conditional branch in code (e.g. an 'if' clause), it tries to predict which branch will be taken before it actually knows the result. It executes that branch ahead of time - a feature called "speculative execution".
The idea is that if it gets the prediction right (which modern processors are quite good at) it'll already have executed the next bit of code by the time the actually-selected branch is known. If it gets it wrong, execution unwinds back and the correct branch is executed instead.
What makes the processor so good at branch prediction is that it stores details about previous branch operations, in what's called the Branch History Buffer (BHB). If a particular branch instruction took path A before, it'll probably take path A again, rather than path B.
Some of you might be hearing about #Spectre and #Meltdown today, which allow memory from other processes and the kernel itself to be read. They exploit CPU designs.
I'm still doing my reading, but a good place to start if you're technically inclined is spectreattack.com
I'm still doing my reading, but a good place to start if you're technically inclined is spectreattack.com
Spectre involves training the CPU to speculatively run invalid code in the victim's address space, and then using a side-channel (such as cache timings) to infer details about the victim's memory.
It affects at least AMD, Intel and ARM CPUs
The sample exploit reads 10KB/s.
It affects at least AMD, Intel and ARM CPUs
The sample exploit reads 10KB/s.
Spectre also includes sample code for breaking out of the JavaScript sandbox on chrome.
It's very, very clever.
It's very, very clever.
A huge hardware BUG hit all Intel CPU x86. A software patch for Linux is ready. We are testing it and will start to deploy it in the next hours.
Maximum tomorrow, a new kernel will be proposed for all customers VPS, PCI, Baremetal. We will upgrade all the images for Public Cloud, Private Cloud, VPS.
