orting
Do you have any idea what could cause this?
I'm not sure how to go further with this reproducer unless I fix this error.
I would be so grateful for even multiple ideas where the problem could be,
so I can check them.
Thank you for your response.
Lukas
On Tue, Nov 2, 2021 at 11:08 AM Luka
hat are executed to the server (or if the
test is not executing any commands in the server, then whatever it's
executed after the server is started).
On Tue, Oct 12, 2021 at 10:47 PM Sergei Golubchik wrote:
> Hi, Lukas!
>
> On Oct 05, Lukas Javorsky wrote:
> > Hi guys,
> >
>
y we'll need to do it in
> existing versions, not only in a new development branch.
>
> And Connector/C already supports OpenSSL 3.0 (CONC-503), so we have a
> reasonably good idea of what needs to be done.
>
> On Oct 06, Lukas Javorsky wrote:
> > Hi Sergei,
> >
> &
> We have some very simple patch which helps MariaDB to build with the
openssl-3 version, however, the test suite is failing (Failed 56/3396
tests).
The patch is linked in the JIRA ticket as well:
https://jira.mariadb.org/browse/MDEV-25785
On Wed, Oct 6, 2021 at 12:21 PM Lukas Javorsky wr
Hi guys,
I've found few particular tests from the test suite that is failing due to
the OpenSSL-3 version and I want to separate them and give them to the
OpenSSL team in Red Hat.
The idea behind this is to give them a set of commands/config options
(reproducer) for each test and they will try
Hi,
We've created two Jira tickets for the OpenSSL 3.0 support, however, we
didn't really get a response or any detailed information from you about it.
Connector-c: https://jira.mariadb.org/browse/CONC-503
Server: https://jira.mariadb.org/browse/MDEV-25785
It's our big concern to support this
need to protect
our customers against these types of attacks.
I will try to provide as many information as I can in the following feature
requests at jira.mariadb.com
Thank you
Lukas
On Fri, Mar 19, 2021 at 2:11 PM Sergei Golubchik wrote:
> Hi, Lukas!
>
> On Mar 19, Lukas Javorsk
t;> reason to not add a SHA256 sig.
>>
>> All The Bests,
>> Eliezer
>>
>>
>> Eliezer Croitoru
>> Tech Support
>> Mobile: +972-5-28704261
>> Email: ngtech1...@gmail.com
>> Zoom: Coming soon
>>
>>
>> -Original Mes
Hi,
In RHEL-9 we are deprecating, old SHA-1 and MD5 and that's why I want to
ask you if there is any chance that upstream is going to change it, or we
should do it downstream.
These algorithms are no longer considered as safe, so it may be a good
thing to upgrade them.
AFAIK mariadb uses these
bly relevant.
What are you suggesting?
Thanks for help
Lukas
On Tue, Mar 16, 2021 at 1:13 PM Daniel Black wrote:
>
>
> On Mon, Mar 15, 2021 at 10:31 PM Lukas Javorsky
> wrote:
>
>> So IIRC, we don't need the setuid/setgid capability in Fedora/RHEL OS
>> because
So IIRC, we don't need the setuid/setgid capability in Fedora/RHEL OS
because we use systemd services right?
Thanks for clarifying
Lukas
On Sun, Mar 14, 2021 at 12:42 AM Daniel Black wrote:
>
> This was relaxed in https://github.com/MariaDB/server/commit/27e6fd9a5968
> where the setuid is only
Hi guys,
I'm looking into SELinux in Fedora's MariaDB package and I can see that we
have two types in MariaDB that have setuid/setgid capability.
1st:
https://github.com/fedora-selinux/selinux-policy/blob/rawhide/policy/modules/contrib/mysql.te#L70
2nd:
12 matches
Mail list logo
