Discuss January 2013

discuss@lists.centos.org

186 participants
157 discussions

Why is localhost self-signed cert a CA cert?
by Robert Moskowitz 13 Jan '13

13 Jan '13

I am building a mail server on Centos 6.3 and working with OpenSSL to create a self-signed certificate for mail use. Along the line of learning the 'best' options to use for OpenSSL and dealing with the default SSL virtual host for Apache, I discovered that the localhost cert created (I believe) during firstboot has the X509v3 extensions set as a CA cert (eg basicConstraint CA:TRUE). I was once very involved in PKIX and legal issues on certificate policy. Having the localhost cert being a CA cert, thus allowed to sign other certs, MAY have legal implications in the USofA and EU. Why was this chosen? Why is not -extensions v3_req used in the certificate creation? Oh you can see this for yourself with: openssl x509 -in /etc/pki/certs/localhost.crt -text -nameopt multiline -noout|more

3 11

use of hard links and diff in rsync
by ken 12 Jan '13

12 Jan '13

On 01/11/2013 07:08 PM Reindl Harald wrote: > .... > different versions of the backup > daily, weekly, monthly Ah, yes, in that kind of scenario hard links would be useful. > unchanged files are replaced with hard-links > the destination files are virtually on the same place And so then could changes to a file be recorded in the daily version as a diff against the weekly?

3 2

CentOS-announce Digest, Vol 95, Issue 4
by centos-announce-request＠centos.org 12 Jan '13

12 Jan '13

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CentOS 5.9 i386 and x86_64 Packages Available in the Continuous Release (CR) Repository (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Jan 2013 07:46:19 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CentOS 5.9 i386 and x86_64 Packages Available in the Continuous Release (CR) Repository To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <50F017AB.10406(a)centos.org> Content-Type: text/plain; charset="iso-8859-1" The CentOS-5.9 Packages for the i386 and x86_64 Architectures are now available via the Continuous Release (CR) Repository. The CR Announcements for CentOS-5.9 can be viewed here: http://lists.centos.org/pipermail/centos-cr-announce/2013-January/thread.ht… More information about the CR Repository and how to install it is available here: http://wiki.centos.org/AdditionalResources/Repositories/CR As explained in the above link, we are still doing advanced QA testing on CentOS-5.9 and there may be some minor changes before the final release. This "opt-in" CR Repo process allows earlier access to our best effort packages now while we complete the final CentOS-5.9 QA processes, spin the ISOs and create an installable tree. Thanks, Johnny Hughes

1 0

Re: [CentOS] Building Dovecot CentOS 5 RPMs with custom LDAP packages
by Nikolaos Milas 12 Jan '13

12 Jan '13

On 11/1/2013 1:44 μμ, fakessh @ wrote: > I do not know the only thing I can tell you that laziness is a value in > the computer You are partly right. However, IMHO building dovecot using standard openldap-devel on CentOS 5 means that, even though the final RPM works, it will use *ancient* openldap v2.3 libraries. If we manage to use custom openldap libaries (like those from LTB Openldap builds) then Dovecot can be built against modern/current Openldap v2.4 libraries. That may provide significant improvements to the final RPM, in terms of LDAP usage. In any case, I found the solution (based on the documentation: http://wiki2.dovecot.org/CompilingSource) I added the following lines (marked below with ++) in your spec file: %build export PATH=/usr/kerberos/bin:$PATH #required for fdpass.c line 125,190: dereferencing type-punned pointer will break strict-aliasing rules ++ export CPPFLAGS="${CPPFLAGS} -I/usr/local/openldap/include" ++ export LDFLAGS="${LDFLAGS} -L/usr/local/openldap/lib64" export CFLAGS="$RPM_OPT_FLAGS -fno-strict-aliasing" %configure INSTALL_DATA="install -c -p -m644" \ --docdir=%{_docdir}/%{name}-%{version} \ --disable-static \ --disable-rpath \ --with-nss \ --with-shadow \ --with-pam \ --with-gssapi=plugin \ --with-ldap=plugin \ ... So, this produces a dovecot package based on Openldap 2.4 libraries(follows excerpt from the rpmbuild output): ... Requires(interp): /bin/sh /bin/sh /bin/sh /bin/sh Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires(pre): /bin/sh shadow-utils Requires(post): /bin/sh chkconfig shadow-utils Requires(preun): /bin/sh chkconfig initscripts shadow-utils Requires(postun): /bin/sh initscripts Requires: /bin/bash /bin/sh config(dovecot) = 1:2.1.13-3.centme initscripts ... libldap-2.4.so.2()(64bit) ... ... It was initially using: libldap-2.3.so.0()(64bit) Regards, Nick

1 1

Re: [CentOS] grub issues on reinstall. [resolved-ish]
by zGreenfelder 12 Jan '13

12 Jan '13

>> running find /grub/grub.conf from the grub shell when the machine >> tries to boot returns (hd0,0) >> and /dev/sdi1 is where /boot mounts. >> > That's *very* odd. You don't have an HBA or something else - flash key? > anything? What's on this system that it sees stuff that high? > > Directly related: look at your BIOS, and see what drives it sees, and > what's bootable, in what order. Perhaps you can move up the boot drive? > <snip> > So I went back to this tonight and fought, fought and fought some more. there was no HBA sort of thing, just a little home machine, the BIOS could see all the drives and were all in the order I expected, but I never got anywhere with trying to write to the MBRs of any of the drives. I could go into recovery mode and get the installed system to come up that way, utilities like grub-install seemed to hang in attempting to write to the devices. I ended up just bailing, took a USB key installed it (it showed up as /dev/sda) and installed grub to the MBR there so now I can boot. Thanks for the suggestions. -- Even the Magic 8 ball has an opinion on email clients: Outlook not so good.

1 0

ddumbfs-1.1 a inline dedup filesystem based on fuse
by Alain Spineux 12 Jan '13

12 Jan '13

Hi I have uploaded a new release of ddumbfs. More information here : http://www.magiksys.net/ddumbfs/index.html You can download RPMs and sources here : http://www.magiksys.net/download/ddumbfs/ enjoy -- Alain Spineux | aspineux gmail com Monitor your iT & Backups | http://www.magikmon.com Free Backup front-end | http://www.magikmon.com/mksbackup Your email 100% available | http://www.emailgency.com

1 0

grub issues on reinstall.
by zGreenfelder 11 Jan '13

11 Jan '13

Hi all. sorry for an immediate question after subscribing, but I've managed to back myself into a frustrating corner. I've done some googling and come up dry, I figured I should try to post to the list while I dig through the archives. I have an issue with grub on a centos reinstall. my system previously had 1x 120g ide drive, 3 1tb sata drives in raid 5 md, 2 300 g in a raid 1 md,the /boot partition was on the ide drive, os on the raid 1 in a volume group and everything seemed fine. I downloaded the x86_86 iso a few days back and decided to just to a complete reinstall rather than burn myself with some odd upgrade path trying to put newer, larger drives into a md with a much smaller drive. I've since purchased some new drives and changed to 1 120 ide, 4 1 tb sata, 2 3tb sata. I've tried a few different combinations of install locations (e.g reused the ide as /boot, a 512 mb slice from a 1tb drive for /boot) but every layout I try seems to end up with a grub config that can not find the OS (if memory serves, the message comes back as error 15: file not found, hit return to reboot) the thing that seems odd to me is when I do the reinstall, the hdds seem to start much higher than I'd expect. there's no /dev/sda, b, c, d, ... I think they start at i. does anyone have some suggestions for what to try for this issue? Thanks. -- Even the Magic 8 ball has an opinion on email clients: Outlook not so good.

2 3

Building Dovecot CentOS 5 RPMs with custom LDAP packages
by Nikolaos Milas 11 Jan '13

11 Jan '13

Hi, We are (still) mainly using CentOS 5 (5.8 x86_64). As CentOS / EL 5 standard OpenLDAP packages are rather old (2.3.x), we've been using LTB OpenLDAP packages ( http://ltb-project.org/wiki/download#openldap) which get installed in non-standard file system locations. I am not much experienced in building RPMs and preparing spec files. We are currently using dovecot RPM packages from the atrpms repo (http://packages.atrpms.net/dist/el5/dovecot/) I would like to re-build Dovecot packages based on the LTB OpenLDAP RPM packages (OpenLDAP v2.4.x), esp. because I see that ATRPMs Dovecot RPM packages are built using OpenLDAP v2.3 devel code (i.e. standard CentOS OpenLDAP devel packages). In http://dl.atrpms.net/all/dovecot.spec I see: ------------------------------------------------ BuildRequires: openldap-devel, cyrus-sasl-devel ... Obsoletes: %{name}-pgsql < %{epoch}:%{version}-%{release}, %{name}-mysql < %{epoch}:%{version}-%{release}, %{name}-sqlite < %{epoch}:%{version}-%{release}, %{name}-ldap < %{epoch}:%{version}-%{release}, $ Conflicts: %{name}-pgsql > %{epoch}:%{version}-%{release}, %{name}-mysql > %{epoch}:%{version}-%{release}, %{name}-sqlite > %{epoch}:%{version}-%{release}, %{name}-ldap > %{epoch}:%{version}-%{release}, $ ------------------------------------------------ So, I guess I can/should change the former line to: BuildRequires: openldap-ltb-debuginfo, cyrus-sasl-devel Note: The final Dovecot RPM and the associated executables (included therein) do not need any LDAP dynamic library in order to run with LDAP support; i.e. after building, the produced package does not require any ldap package on the system. Question 1: What other changes/additions should we make in the spec file in order to specify that we will be using (if needed) LDAP libraries from: /usr/local/openldap/lib64 and include files from: /usr/local/openldap/include (rather than from /usr/lib64 and /usr/include, respectively, which are the standard file paths used in native openldap-devel RPM)? Question 2: How the Obsoletes and Conflicts lines should be changed? Any other associated info would be appreciated. Thanks, Nick

2 3

GnuTLS v3.1.6 on CentOS 6.3
by Bry8 Star 11 Jan '13

11 Jan '13

Hi, on CentOS 6.3 (32-bit) current & default GnuTLS is version 2.8.5-4.el6_2.2 gnutls.i686 ( where can i get a src rpm for at-least trying it from a 2nd/different directory ? ) Can someone kindly point to an article that will help to effectively upgrade to GnuTLS v3.1.1 or later+stable version, on CentOS 6.3 (32-bit) ? Need the DANE supported GnuTLS, will be used for various GnuTLS depended apps. Thanks in advance, -- Bright Star.

2 2

Andreas Reschke is out of the office
by Andreas Reschke 11 Jan '13

11 Jan '13

Ich werde ab 11.01.2013 nicht im Büro sein. Ich kehre zurück am 21.01.2013.

1 0

← Newer
1
...
9
10
11
12
13
14
15
16
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2013