On 11.9.2023. 2:48, Mike Larkin wrote:
> On Sun, Sep 10, 2023 at 01:36:33AM +0200, Hrvoje Popovski wrote:
>> Hi all,
>>
>> I've installed latest snapshot with uefi on Dell R7615 with AMD EPYC
>> 9554P, with some NVMe disks on BOSS-N1 adapter and with Samsung NVMe
>> disks directly connected to
This adds another compliance check for the X.509 subject name.
Only commonName, and optionally serialNumber, are permitted in the
certificate subject name. See RFC 6487 section 4.4 and 4.5.
It seems the one CA who was not compliant with this requirement got
their act together, so now is an
On Sun, Sep 10, 2023 at 01:36:33AM +0200, Hrvoje Popovski wrote:
> Hi all,
>
> I've installed latest snapshot with uefi on Dell R7615 with AMD EPYC
> 9554P, with some NVMe disks on BOSS-N1 adapter and with Samsung NVMe
> disks directly connected to backplane and installation was fast and
> without
Replace selinfo remnants with knote(9) API. Mechanical conversion
because `fuse_rd_filtops' left non MP safe. knote_locked(9) used because
the path covered by kernel lock.
We have some places where selinfo is still used. All of them could be
mechanically converted in this way and obsolete
On 2023/09/09 13:49, Sagar Acharya wrote:
> Thanks Peter, your comments were very helpful and I made some progress
>
> I have currently hosted server at 587. I have also set
>
> _submission._tcp.humaaraartha.in. SRV
>
> records which point to 587. However, I think such a thing is not
