>AFAIU, all that I can get from that is some (kilo)bytes from random
> memory area. Mostly
> it would be random binary garbage which can be hardly interpreted as
> something useful.
Not exactly. Mostly you get some uninteresting garbage. But with enough time
(matter or hours) you will get
Here are some numbers based on pgbench:
https://www.phoronix.com/scan.php?page=article&item=linux-415-x86pti&num=2.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On Tue, Jan 9, 2018, at 16:34, Leyne, Sean wrote:
> András,
>
> > We've done some test runs with the 'old' kernel (linux-image-4
András,
> We've done some test runs with the 'old' kernel (linux-image-4.9.0-4-
> amd64) and the 'new' one (linux-image-4.9.0-5-amd64).
>
> No. of tests: 6014
> No. of result checks: 253555 (checking column values, stored procedure
> results, etc.)
>
> Average running time on 4.9.0-4: 466 secs
09.01.2018 12:46, Vlad Khorsun via Firebird-devel wrote:
09.01.2018 13:38, Dimitry Sibiryakov wrote:
09.01.2018 12:21, Vlad Khorsun (JIRA) wrote:
Actually, isql connects successfully, but it reads RDB$DATABASE itself right after
attachment (using READ COMMITTED NO RECORD
VERSION WAIT transacti
09.01.2018 12:44, Mark Rotteveel wrote:
The problem with meltdown and spectre is that it could potentially allow you to gather
information that the exploited process would normally not be able to access.
AFAIU, all that I can get from that is some (kilo)bytes from random memory area. Mostly
09.01.2018 13:38, Dimitry Sibiryakov wrote:
09.01.2018 12:21, Vlad Khorsun (JIRA) wrote:
Actually, isql connects successfully, but it reads RDB$DATABASE itself right
after attachment (using READ COMMITTED NO RECORD
VERSION WAIT transaction)
Shouldn't it be changed as well?
For what ?
On 9-1-2018 12:40, Dimitry Sibiryakov wrote:
09.01.2018 12:36, Mark Rotteveel wrote:
it can be exploited by any code running local on your machine. So
anything on that machine that could have a remote code execution
vulnerability, or just a plain malicious update, could then exploit it.
An
09.01.2018 12:36, Mark Rotteveel wrote:
it can be exploited by any code running local on your machine. So anything on that machine
that could have a remote code execution vulnerability, or just a plain malicious update,
could then exploit it.
Anything that can have such vulnerability don't n
09.01.2018 12:21, Vlad Khorsun (JIRA) wrote:
Actually, isql connects successfully, but it reads RDB$DATABASE itself right
after attachment (using READ COMMITTED NO RECORD
VERSION WAIT transaction)
Shouldn't it be changed as well?
--
WBR, SD.
--
On 9-1-2018 11:25, Sergey Mereutsa wrote:
Hi!
Just for your information - if this is your own dedicated server and you
do NOT run untrusted code on it (which can potentially steal your data
and send to someone) - you can safely disable this patch.
Just because you do not defend yourself from
Avoid UPDATE of RDB$DATABASE by ALTER DATABASE statement when possible
--
Key: CORE-5704
URL: http://tracker.firebirdsql.org/browse/CORE-5704
Project: Firebird Core
Issue Ty
, version of virus signature
database 16706 (20180109) __
The message was checked by ESET Mail Security.
http://www.eset.com
--
Check out the vibrant tech community on one of the world's most
engaging tech si
On Tue, 9 Jan 2018 12:25:24 +0200 Sergey Mereutsa wrote
>
> Both vulnerabilities are LOCAL :)
>
Your server also has to be air-gapped from the internet and all its
clients must also be air-gapped from the internet.
If there is any connection to the outside world then all bets are off
as one f
ng time on 4.9.0-4: 466 secs (7 mins 46 secs)
>
> Average running time on 4.9.0-5: 635 secs (10 mins 35 secs)
>
>
>
> The database file and the tmp directory located on ramdisk.
>
>
>
> András
>
>
> __ Information from ESET Mail S
When database validation fixes "orphan page" errors it also should adjust
"lowest free page" marker (pip_min) on corresponding PIP, if necessary
On Tue, 9 Jan 2018 09:52:59 + Omacht András wrote
>
> Average running time on 4.9.0-4: 466 secs (7 mins 46 secs)
> Average running time on 4.9.0-5: 635 secs (10 mins 35 secs)
That is a massive hit.
Has anyone had a chance to run tests on AMD kit?
Paul
--
Paul Reeves
http://www.ibphoen
09.01.2018 11:41, Mark Rotteveel wrote:
On 8-1-2018 15:12, Vlad Khorsun via Firebird-devel wrote:
08.01.2018 15:52, Mark Rotteveel wrote:
I'm really out of my depth here. I've created a full dump of the Firebird
process while Jaybird is hanging:
https://www.dropbox.com/s/ea1fskiqtg1fmxs/fb_4
Average running time on 4.9.0-4: 466 secs (7 mins 46 secs)
Average running time on 4.9.0-5: 635 secs (10 mins 35 secs)
The database file and the tmp directory located on ramdisk.
András
__ Information from ESET Mail Security, version of virus signature
database 16706 (20180109) __
On 8-1-2018 15:12, Vlad Khorsun via Firebird-devel wrote:
08.01.2018 15:52, Mark Rotteveel wrote:
I'm really out of my depth here. I've created a full dump of the
Firebird process while Jaybird is hanging:
https://www.dropbox.com/s/ea1fskiqtg1fmxs/fb_4build840_hang.7z?dl=0
Windows 10 x64, Fi
19 matches
Mail list logo
