> -Original Message-
> From: cctalk On Behalf Of Paul Koning via
> cctalk
> Sent: 03 October 2019 16:28
> To: Stefan Skoglund
> Cc: General Discussion: On-Topic and Off-Topic Posts
> Subject: Re: VAX + Spectre
>
>
>
> > On Oct 3, 2019, a
> On Oct 3, 2019, at 10:55 AM, Stefan Skoglund wrote:
>
> tor 2019-10-03 klockan 09:45 -0400 skrev Paul Koning via cctalk:
>>> On Oct 3, 2019, at 8:25 AM, Maciej W. Rozycki >>> wrote:
>>>
>>> On Thu, 3 Oct 2019, Maciej W. Rozycki wrote:
>>>
> You need an extremely high resolution timer
tor 2019-10-03 klockan 09:45 -0400 skrev Paul Koning via cctalk:
> > On Oct 3, 2019, at 8:25 AM, Maciej W. Rozycki > > wrote:
> >
> > On Thu, 3 Oct 2019, Maciej W. Rozycki wrote:
> >
> > > > You need an extremely high resolution timer to detect slight
> > > > differences in
> > > > execution
> On Oct 3, 2019, at 8:25 AM, Maciej W. Rozycki wrote:
>
> On Thu, 3 Oct 2019, Maciej W. Rozycki wrote:
>
>>> You need an extremely high resolution timer to detect slight differences in
>>> execution time of speculatively-executed threads. The VAX 11/780 certainly
>>> did
>>> not do
On Thu, 3 Oct 2019, Maciej W. Rozycki wrote:
> > You need an extremely high resolution timer to detect slight differences in
> > execution time of speculatively-executed threads. The VAX 11/780 certainly
> > did
> > not do speculative execution, and my guess is that all VAXen did not,
> >
On Tue, 17 Sep 2019, Jon Elson via cctalk wrote:
> > "Spectre" is one of two notorious bugs of modern CPUs involving speculative
> > execution. I rather doubt that VAX is affected by this but I suspect others
> > here have a lot more knowledge.
> >
> >
> You need an extremely high resolution
On Sun, 22 Sep 2019, Nemo via cctalk wrote:
We had a secure (but not tempest) room built for us by an authorised
contractor and they forgot to install A/C. It was unusable until a
portable A/C was placed in it with complicated baffles letting the hot
air out.
Nobody except a college
On 18/09/2019, Guy Sotomayor Jr via cctalk wrote:
>
[...]
> Yea, I had to make a trip to a “secure facility” once and there were entire
> “tempest” rooms with conditioned power and no external communications
> equipment.
We had a secure (but not tempest) room built for us by an authorised
> On Sep 18, 2019, at 9:59 AM, Chris Elmquist wrote:
>
> On Wednesday (09/18/2019 at 09:19AM -0700), Guy Sotomayor Jr via cctalk wrote:
>>
>>
>>> On Sep 18, 2019, at 12:42 AM, Liam Proven via cctalk
>>> wrote:
>>>
>>> On Wed, 18 Sep 2019 at 02:19, Paul Koning via cctalk
>>> wrote:
>
On Wednesday (09/18/2019 at 09:19AM -0700), Guy Sotomayor Jr via cctalk wrote:
>
>
> > On Sep 18, 2019, at 12:42 AM, Liam Proven via cctalk
> > wrote:
> >
> > On Wed, 18 Sep 2019 at 02:19, Paul Koning via cctalk
> > wrote:
> >>> ...
> >> Speaking of timing, that reminds me of two amazing
> On Sep 18, 2019, at 12:42 AM, Liam Proven via cctalk
> wrote:
>
> On Wed, 18 Sep 2019 at 02:19, Paul Koning via cctalk
> wrote:
>>> ...
>> Speaking of timing, that reminds me of two amazing security holes written up
>> in the past few years. Nothing to do with the Spectre etc. issue.
>>
On Wed, 18 Sep 2019 at 02:19, Paul Koning via cctalk
wrote:
> > ...
> Speaking of timing, that reminds me of two amazing security holes written up
> in the past few years. Nothing to do with the Spectre etc. issue.
>
> One is the recovery of speech from an encrypted VoIP channel such as Skype,
Windows _is_ Bells and Whistles, plus a couple of gongs.
No ... The GONGS is the chinese knock off.
On 9/17/2019 1:08 PM, Fred Cisin via cctalk wrote:
On Tue, 17 Sep 2019, Paul Koning via cctalk wrote:
I could easily imagine a computer science exam question "Describe in
one paragraph the specific design error that enabled the Meltdown
attack".
I used to have some related questions in my
> On Sep 17, 2019, at 6:51 PM, dwight via cctalk wrote:
>
> ...
> This latest one is bad for a touch typer or those that always enter the
> password in the same way. It looks for the timing of when you hit keys and
> then makes guesses on what keys would typically take that length of time
Discussion: On-Topic and Off-Topic Posts ;
SIMH
Subject: Re: [Simh] Fwd: VAX + Spectre
I can simplify the question a bit. I have to be careful as I work for
Intel and I've been involved with a small bit of it on our end and some of
the lawyers are a bit touchy about the whole situation. So I
of modern CPUs involving
> speculative execution. I rather doubt that VAX is affected by this but I
> suspect others here have a lot more knowledge.
> >
> > paul
> >
> >> Begin forwarded message:
> >>
> >> From: co...@sdf.org
> >> Subject
On Tue, 17 Sep 2019 at 21:09, Fred Cisin via cctalk
wrote:
> One student (who later became my best friend and buddy)
> skipped the technical details and said, "The primary design error for
> MacOS and Windoze (sic) is that they placed a lower priority on security,
> than on being able to
On 9/17/19 3:08 PM, Fred Cisin via cctalk wrote:
> On Tue, 17 Sep 2019, Paul Koning via cctalk wrote:
>> I could easily imagine a computer science exam question "Describe in
>> one paragraph the specific design error that enabled the Meltdown
>> attack".
>
> I used to have some related questions
On Tue, 17 Sep 2019, Paul Koning via cctalk wrote:
I could easily imagine a computer science exam question "Describe in one
paragraph the specific design error that enabled the Meltdown attack".
I used to have some related questions in my microcomputer operating
systems class. One student
> On Sep 17, 2019, at 2:35 PM, allison via cctalk wrote:
>
>>> ...
>
> I see this as a question of the number of angels that can dance on the
> point of a pin. But could GCC compile code that has system access to
> do nasties is a more complex question. Then again how does it get
> system
Tue, Sep 17, 2019 at 9:55 AM Paul Koning
>> wrote:
>>> "Spectre" is one of two notorious bugs of modern CPUs involving
>> speculative execution. I rather doubt that VAX is affected by this but I
>> suspect others here have a lot more knowledge.
>>>
>
actice.
> > ᐧ
> >
> > On Tue, Sep 17, 2019 at 9:55 AM Paul Koning
> wrote:
> > "Spectre" is one of two notorious bugs of modern CPUs involving
> speculative execution. I rather doubt that VAX is affected by this but I
> suspect others here have a lot more
e have a lot more knowledge.
>
> paul
>
>> Begin forwarded message:
>>
>> From: co...@sdf.org
>> Subject: VAX + Spectre
>> Date: September 17, 2019 at 5:32:42 AM EDT
>> To: port-...@netbsd.org
>>
>> So, this is a bug report:
>> https:/
rwarded message:
>
> *From: *co...@sdf.org
> *Subject: **VAX + Spectre*
> *Date: *September 17, 2019 at 5:32:42 AM EDT
> *To: *port-...@netbsd.org
>
> So, this is a bug report:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86811
>
> GCC would like to know if VAX needs S
On 09/17/2019 08:55 AM, Paul Koning via cctalk wrote:
"Spectre" is one of two notorious bugs of modern CPUs involving speculative
execution. I rather doubt that VAX is affected by this but I suspect others here have a
lot more knowledge.
You need an extremely high resolution timer to detect
> "Spectre" is one of two notorious bugs of modern CPUs involving speculative
> execution. I rather doubt that VAX is affected by this but I suspect others
> here have a lot more knowledge.
However, even speculative execution isn't enough to make Spectre possible or
feasible. For example, the
rather doubt that VAX is affected by this but I suspect others
> here have a lot more knowledge.
>
> paul
>
>> Begin forwarded message:
>>
>> From: co...@sdf.org <mailto:co...@sdf.org>
>> Subject: VAX + Spectre
>> Date: September 17, 2019 at
"Spectre" is one of two notorious bugs of modern CPUs involving speculative
execution. I rather doubt that VAX is affected by this but I suspect others
here have a lot more knowledge.
paul
> Begin forwarded message:
>
> From: co...@sdf.org
> Subject: VAX + Spe
29 matches
Mail list logo
