On 12/01/2018 22:38, Mark wrote:
> Don't the OS kernel / BIOS / CPU updates just mitigate against Meltdown,
> preventing applications (executing in ring3) from inferring content of
> kernel memory (in ring0)?
AFAIU, the kernel work-around for Meltdown is /not/ mapping the
kernel inside an appli
On 1/12/18, mozilla-lists.mbou...@spamgourmet.com
wrote:
> Lee wrote:
>> I've got a dell, so I started here:
>> https://www.dell.com/support/article/us/en/19/sln308587/microprocessor-side-channel-vulnerabilities--cve-2017-5715--cve-2017-5753--cve-2017-5754---impact-on-dell-products?lang=en
>>
>> A
Lee wrote:
I've got a dell, so I started here:
https://www.dell.com/support/article/us/en/19/sln308587/microprocessor-side-channel-vulnerabilities--cve-2017-5715--cve-2017-5753--cve-2017-5754---impact-on-dell-products?lang=en
Apply the update, do the powershell bit:
PS C:\temp\2do\SpeculationCon
, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch
for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
Mozilla needs to come up with a patch first. What they have now
only
blocks the obvious timing attack methods.
>>>>>> On 1/7/18, Ray_Net wrote:
>>>>>>>>>>> WaltS48 wrote on 06-01-18 18:05:
>>>>>>>>>>>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>>>>>>>>>>>> I have read:
>>>>>>>>>&g
owser company comes out with patch
for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
Mozilla needs to come up with a patch first. What they have now
only
blocks the obvious timing attack methods.
SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Fire
t;>>> that allows javascript from only whitelisted sites.
>>>>>>>>
>>>>>>>> On 1/7/18, Ray_Net wrote:
>>>>>>>>> WaltS48 wrote on 06-01-18 18:05:
>>>>>>>>>> On 1/6/18 2:36 AM, Ray_Net
cript."
So, will SM issue a patch against the Spectre exploit ?
Mozilla needs to come up with a patch first. What they have now only
blocks the obvious timing attack methods.
SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
doesn't have SharedBuff
gt;>> WaltS48 wrote on 06-01-18 18:05:
>>>>>>>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>>>>>>>> I have read:
>>>>>>>>>
>>>>>>>>> "Disable Javascript until browser company comes out with patch
javascript from only whitelisted sites.
On 1/7/18, Ray_Net wrote:
WaltS48 wrote on 06-01-18 18:05:
On 1/6/18 2:36 AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spect
gt;>>>>>>
>>>>>>> "Disable Javascript until browser company comes out with patch for
>>>>>>> vulnerable Javascript."
>>>>>>>
>>>>>>> So, will SM issue a patch against the Spectre exploit ?
&
wrote:
WaltS48 wrote on 06-01-18 18:05:
On 1/6/18 2:36 AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
Mozilla needs to come up with a patch first.
gt;> On 1/7/18, Ray_Net wrote:
>>> WaltS48 wrote on 06-01-18 18:05:
>>>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>>>> I have read:
>>>>>
>>>>> "Disable Javascript until browser company comes out with patch for
>>>>> vulnera
gt;> On 1/7/18, Ray_Net wrote:
>>> WaltS48 wrote on 06-01-18 18:05:
>>>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>>>> I have read:
>>>>>
>>>>> "Disable Javascript until browser company comes out with patch for
>>>>>
AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
Mozilla needs to come up with a patch first. What they have now only
blocks the obvious timing atta
te:
>>> I have read:
>>>
>>> "Disable Javascript until browser company comes out with patch for
>>> vulnerable Javascript."
>>>
>>> So, will SM issue a patch against the Spectre exploit ?
Mozilla needs to come up with a patch
On 1/7/2018 2:48 AM, Ray_Net wrote:
> WaltS48 wrote on 06-01-18 18:05:
>> On 1/6/18 2:36 AM, Ray_Net wrote:
>>> I have read:
>>>
>>> "Disable Javascript until browser company comes out with patch for
>>> vulnerable Javascript."
>>&g
On 1/7/18 5:48 AM, Ray_Net wrote:
WaltS48 wrote on 06-01-18 18:05:
On 1/6/18 2:36 AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
SeaMonkey 2.49.
WaltS48 wrote on 06-01-18 18:05:
On 1/6/18 2:36 AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
SeaMonkey 2.49.1 is based on Firefox 52 ESR code, a
something else to
selectively allow javascript?
So, will SM issue a patch against the Spectre exploit ?
SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
doesn't have SharedBufferArray enabled.
||
||SharedArrayBuffer| is already disabled in Firefox 52 ESR.
||
|REF: https://
e using something else to
selectively allow javascript?
>> So, will SM issue a patch against the Spectre exploit ?
>
> SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
> doesn't have SharedBufferArray enabled.
> ||
> ||SharedArrayBuffer| is already disable
WaltS48 wrote:
On 1/6/18 2:36 AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ES
On 1/6/18 2:36 AM, Ray_Net wrote:
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
SeaMonkey 2.49.1 is based on Firefox 52 ESR code, and Firefox 52 ESR
do
I have read:
"Disable Javascript until browser company comes out with patch for
vulnerable Javascript."
So, will SM issue a patch against the Spectre exploit ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla
24 matches
Mail list logo