[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Debian derivatives census: Qlustar: welcome!



Hi Roland,

I would like to welcome yourself and Qlustar to the Debian derivatives
census! Would you like to take this opportunity to introduce yourself
and Qlustar to us all? 

https://wiki.debian.org/Derivatives/Census/Qlustar

It would be great if you could join our mailing list and IRC channel:

http://wiki.debian.org/DerivativesFrontDesk

I would encourage you to look at Debian's guidelines for derivatives:

http://wiki.debian.org/Derivatives/Guidelines

You may want to look at our census QA page, some of the mails from there
may apply to Qlustar.

http://wiki.debian.org/Derivatives/CensusQA

I've made a few changes to the Qlustar census page:

http://wiki.debian.org/Derivatives/Census/Qlustar?action=info

The page says that Qlustar modifies Debian binary packages. It is quite
rare that distributions modify Debian binary packages. Does Qlustar
actually do this? If so could you describe what kind of modifications
you are making? If not I guess the page needs to be fixed.

The page is missing a dpkg vendor field. It is important that Debian
derivatives set this properly on installed systems and mention the value
of the field in the derivatives census.

https://wiki.debian.org/Derivatives/Guidelines#Vendor

Some of the Release files in the apt repository for Qlustar are missing
the Valid-Until header, which allows clients to find out when active
network attackers are holding back newer Release files. At minimum,
rolling releases and suites containing security updates should have this
header. With reprepro you can use the ValidFor config option.

https://wiki.debian.org/RepositoryFormat#Date.2CValid-Until

I've added the Qlustar blog to Planet Debian derivatives which helps the
Debian community find out the things that are happening in the world of
Debian derivatives.

http://planet.debian.org/deriv/

Next year the annual Debian conference is in Heidelberg, Germany. This
appears to be relatively close to the Qlustar location, it would be
great if developers from Qlustar could attend DebConf.

http://debconf15.debconf.org/

I would encourage Q-Leap Networks (the Qlustar corporate sponsor) to
contribute financially to ensure the continued survival of Debian and
the success of the annual Debian conference.

http://www.debian.org/donations
http://debconf.org/sponsors/
http://debconf15.debconf.org/become-sponsor.xhtml

I would encourage any attendees to volunteer to ensure the continued the
success of the annual Debian conference, here are some examples of
things that need helpers.

https://wiki.debconf.org/wiki/DebConf13/VolunteerCoordination

I note that Qlustar is based on Debian stable. The Debian release team
recently released a timeline for the freeze for the next Debian stable
release. I would encourage you to review it and prepare your plans for
rebasing on the next Debian release (jessie).

https://lists.debian.org/debian-devel-announce/2014/09/msg00002.html

A great way to help ensure that the next Debian release working well is
to install and run the how-can-i-help tool and try to work on any issues
that come up.

http://www.lucas-nussbaum.net/blog/?p=837
https://packages.debian.org/unstable/how-can-i-help
https://wiki.debian.org/how-can-i-help

You might want to consider adding DNSSEC to your domains, TLSA records
and SSL to some of your domains. SSL on the repository will help Qlustar
users to obscure package names and version numbers from global active
adversaries. You might also want to add HSTS headers.

http://repo.qlustar.com/
http://q-leap.com/

Please feel free to circulate this mail within the Qlustar team.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: