Fedora 27 Server Beta status (3rd round) is NO-GO
by Jan Kurik
Release status of the Fedora 27 Server Beta is NO-GO.
The next Go/No-Go meeting is planned on Thursday, November 2nd
together with second round of F27 Final Go/No-Go meeting. The F27
Server Beta release slips for one week. The slip also affects the F27
Server GA, it moves to 2017-Dec-19 having Go/No-Go meeting on
2017-Dec-14.
For more information please check the F27 Server Beta Go/No-Go meeting
minutes [1].
[1] https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-26/f27-final-a...
Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
5 years, 7 months
F28 System Wide Change: NSS Default File Format SQL
by Jan Kurik
= System Wide Change: NSS Default File Format SQL =
https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
Change owner(s):
* Kai Engert <kaie(a)redhat.com>
Change the NSS library default to use the sqlite based data storage,
when applications don't specify their preferred storage file format.
== Detailed Description ==
Applications that use the NSS library often use a database for storage
of keys, certificates and trust. NSS supports two different file
formats, one called DBM (based on berkeley DB files) and another one
called SQL (based on sqlite DB files).
Today's default file format used by NSS, used when applications omit
the type parameter, is the older DBM file format, which forbids
parallel access to the storage. The suggestion is to change the
default file format to SQL, which allows parallel access to the
storage.
Applications, or users using the NSS command line utilities, often
provide the database storage location using a simple directory path
parameter. Some might not be aware, or forget, that the parameter can
be prefixed with a type modifier, either "dbm:" or "sql:".
As a result, when not providing this parameter, the file format used
will be the fragile DBM file format. This is particuarly problematic,
if a user attempts to modify the NSS storage using command line tools,
while another process, such as a daemon, is running concurrently,
which also accesses the same database in the DBM file format. This
often results in corrupted database storage, which cannot be
recovered.
By changing the default, all applications that currently use the DBM
file format, will automatically be migrated to the SQL file format.
NSS has the ability to discover if a storage location (a directory)
contains the DBM file format. If configured to use the modern SQL
format, NSS will automatically perform a one-time conversion from the
DBM to the SQL format.
The same applies to the NSS command line utilities. If the NSS library
default is changed to SQL, the NSS tools will also trigger the
one-time conversion, or access the already converted files.
== Scope ==
* Proposal owners:
A small downstream patch needs to be applied to the NSS library
package, which changes the library default.
* Other developers:
It's up to developers of NSS applications, if they accept the new
default and an automatic conversion, or if they prefer to continue to
use the classic DBM storage format. Although not recommended,
developers can easily do so, by adding a "dbm:" prefix to the storage
parameter they provide to NSS at NSS library initialization time.
* Release engineering: [1]
No help should be necessary. No mass rebuild necessary.
* Policies and guidelines: N/A
* Trademark approval: N/A
[1] https://pagure.io/releng/issue/6883
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
5 years, 7 months
Heads Up - openssl makefile and scripts for creating self signed
certificates
by Tomas Mraz
I was asked here to merge pull request that moves the openssl makefile
and scripts for creating self signed certificates to /usr/share/doc.
I am not sure this is the right thing to do as these are definitely
still used currently.
Although it is much easier now to set up proper certificates for your
servers with Let's Encrypt, it is still not fully automatable process
(it needs at least some set up at the beginning for the first issued
certificate). Thus it cannot be included for example in rpm packages
%post scripts, etc.
At least I would like to know from maintainers of packages that depend
on openssl whether they currently use the makefile or the scripts to
create self signed certificate for the service.
Tomas Mraz
5 years, 7 months
Fedora 27 Final Release Readiness Meeting on Thursday, October 26 @
19:00 UTC
by Jan Kurik
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 27
Final Release Readiness Meeting meeting.
The meeting is going to be held on Thursday, Oct 26, 2017 at 19:00
UTC. Please check the [1] link for your time zone.
We will meet to make sure we are coordinated and ready for the Final
release of Fedora 27. Please note that this meeting is going to be
held even if the release is delayed at the Go/No-Go meeting on the
same day two hours earlier.
You may received this message several times, but it is by purpose to
open this meeting to the teams and to raise awareness, so hopefully
more team representatives will come to this meeting. This meeting
works best when we have representatives from all of the teams.
For more information please check the [2] link.
[1] https://apps.fedoraproject.org/calendar/meeting/7385/
[2] https://fedoraproject.org/wiki/Release_Readiness_Meetings
Thank you for your support,
Regards, Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
5 years, 7 months