Re: [CentOS] login case sensitivity

[Yves Bellefeuille]

FHDATA wrote:

>  some users' login fails since they type upper
>  case for their user ids  ,etc ...

Wouldn't it be better to explain to the users that the userid is case
sensitive? You probably don't want a system where Fhdata, FHData and
FHDATA are all possible and are different users.

-- 
Yves Bellefeuille


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] login case sensitivity

[FHDATA]

hello,

some users' login fails since they type upper
case for their user ids  ,etc ...

how can case sensitivity be disabled so they can login
with mix of upper and lower case?

this is what i tried:

in /etc/sssd/sssd.conf i tested this below

[domain/default]
case_sensitive = false


i stopped  sssd, deleted all inside /var/sss/db and
started  sssd  but that did not  help 



thank you,
F-


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] lightdm dependency

[Jon LaBadie]

On Tue, Sep 05, 2017 at 10:56:42AM +0200, Philippe BOURDEU d'AGUERRE wrote:
> Le 05/09/2017 à 07:01, Jon LaBadie a écrit :
> > On a CentOS 7 system I'm trying to install lightdm.
> > Yum says it requires "glib2(x86-64) >= 2.50.3".
> > glib2 2.46 is installed but I have not found a
> > 2.50 version.  Have I overlooked it in some repo?
> > 
> Same problem here. You can find glib2 2.50.3 in cr repository.

Is it reasonable to install a single "cr" package
or would I need to update lots of things to their
cr versions?

jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Network Interrogation

[John R Pierce]

On 9/5/2017 12:30 PM, m.r...@5-cent.us wrote:

Why it doesn't like C6, which I am assuming is fully updated, is a
question for their support, if the o/p from the package doesn't tell you.



wild guess, (snicker), its because  the C6 box isn't running their junkware.


--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Network Interrogation

[m . roth]

Chris Olson wrote:
>
> Small private networks are a necessary part of our business.
> We also run some small networks with Internet connectivity
> through firewall routers.  The smallest of these networks
> has only a printer and a mix of five CentOS and Windows 7
> machines.
>
> We use a commercial protection product on the W7 system.

First suggestion: it's a commercial product. Why not open a support ticket
with them?

> A recent update to this protection product has caused it
> to start probing the network for other systems.  There is
> sometimes a message following scans indicating that there
> are other systems on our network that are unprotected. It
> appears that the two systems it is naming are a CentOS 6
> system and the HP printer.

Second: I'd log into the printer, and check a number of things: first,
does it have bonjour enabled? Does it have "network printing" enabled? And
are its cert, the CA, and the *other* cert all valid? The last, which
sometimes you can only find under networking, not under security, there
may be an option to regenerate a new self-signed cert.

Why it doesn't like C6, which I am assuming is fully updated, is a
question for their support, if the o/p from the package doesn't tell you.

  mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] Xen CentOS 7.3 server + CentOS 7.3 VM fails to boot after CR updates (applied to VM)!

[Kevin Stange]

On 09/04/2017 05:27 PM, Johnny Hughes wrote:
> On 09/04/2017 03:59 PM, Kevin Stange wrote:
>> On 09/02/2017 08:11 AM, Johnny Hughes wrote:
>>> On 09/01/2017 02:41 PM, Kevin Stange wrote:
 On 08/31/2017 07:50 AM, PJ Welsh wrote:
> A recently created and fully functional CentOS 7.3 VM fails to boot
> after applying CR updates:
 
> Server OS is CentOS 7.3 using Xen (no CR updates):
> rpm -qa xen\*
> xen-hypervisor-4.6.3-15.el7.x86_64
> xen-4.6.3-15.el7.x86_64
> xen-licenses-4.6.3-15.el7.x86_64
> xen-libs-4.6.3-15.el7.x86_64
> xen-runtime-4.6.3-15.el7.x86_64
>
> uname -a
> Linux tsxen2.xx.com  4.9.39-29.el7.x86_64 #1 SMP
> Fri Jul 21 15:09:00 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> Sadly, the other issue is that the grub menu will not display for me to
> select another kernel to see if it is just a kernel issue.
>
> The dracut prompt does not show any /dev/disk folder either.
>

 I'm seeing this as well.  My host is 4.9.44-29 and Xen 4.4.4-26 from
 testing repo, my guest is 3.10.0-693.1.1.  Guest boots fine with
 514.26.2.  The kernel messages that appear to kick off the failure for
 me start with a page allocation failure.  It eventually reaches dracut
 failures due to systemd/udev not setting up properly, but I think the
 root is this:

 [1.970630] [ cut here ]
 [1.970651] WARNING: CPU: 2 PID: 225 at mm/vmalloc.c:131
 vmap_page_range_noflush+0x2c1/0x350
 [1.970660] Modules linked in:
 [1.970668] CPU: 2 PID: 225 Comm: systemd-udevd Not tainted
 3.10.0-693.1.1.el7.x86_64 #1
 [1.970677]   8cddc75d 8803e8587bd8
 816a3d91
 [1.970688]  8803e8587c18 810879c8 0083811c14e8
 8800066eb000
 [1.970698]  0001 8803e86d6940 c000
 
 [1.970708] Call Trace:
 [1.970725]  [] dump_stack+0x19/0x1b
 [1.970736]  [] __warn+0xd8/0x100
 [1.970742]  [] warn_slowpath_null+0x1d/0x20
 [1.970748]  [] vmap_page_range_noflush+0x2c1/0x350
 [1.970758]  [] map_vm_area+0x2e/0x40
 [1.970765]  [] __vmalloc_node_range+0x170/0x270
 [1.970774]  [] ? module_alloc_update_bounds+0x14/0x70
 [1.970781]  [] ? module_alloc_update_bounds+0x14/0x70
 [1.970792]  [] module_alloc+0x73/0xd0
 [1.970798]  [] ? module_alloc_update_bounds+0x14/0x70
 [1.970804]  [] module_alloc_update_bounds+0x14/0x70
 [1.970811]  [] load_module+0xb02/0x29e0
 [1.970817]  [] ? vmap_page_range_noflush+0x257/0x350
 [1.970823]  [] ? map_vm_area+0x2e/0x40
 [1.970829]  [] ? __vmalloc_node_range+0x170/0x270
 [1.970838]  [] ? SyS_init_module+0x99/0x110
 [1.970846]  [] SyS_init_module+0xc5/0x110
 [1.970856]  [] system_call_fastpath+0x16/0x1b
 [1.970862] ---[ end trace 2117480876ed90d2 ]---
 [1.970869] vmalloc: allocation failure, allocated 24576 of 28672 bytes
 [1.970874] systemd-udevd: page allocation failure: order:0, mode:0xd2
 [1.970883] CPU: 2 PID: 225 Comm: systemd-udevd Tainted: GW
   3.10.0-693.1.1.el7.x86_64 #1
 [1.970894]  00d2 8cddc75d 8803e8587c48
 816a3d91
 [1.970910]  8803e8587cd8 81188810 8190ea38
 8803e8587c68
 [1.970923]  0018 8803e8587ce8 8803e8587c88
 8cddc75d
 [1.970939] Call Trace:
 [1.970946]  [] dump_stack+0x19/0x1b
 [1.970961]  [] warn_alloc_failed+0x110/0x180
 [1.970971]  [] __vmalloc_node_range+0x234/0x270
 [1.970981]  [] ? module_alloc_update_bounds+0x14/0x70
 [1.970989]  [] ? module_alloc_update_bounds+0x14/0x70
 [1.970999]  [] module_alloc+0x73/0xd0
 [1.971031]  [] ? module_alloc_update_bounds+0x14/0x70
 [1.971038]  [] module_alloc_update_bounds+0x14/0x70
 [1.971046]  [] load_module+0xb02/0x29e0
 [1.971052]  [] ? vmap_page_range_noflush+0x257/0x350
 [1.971061]  [] ? map_vm_area+0x2e/0x40
 [1.971067]  [] ? __vmalloc_node_range+0x170/0x270
 [1.971075]  [] ? SyS_init_module+0x99/0x110
 [1.971081]  [] SyS_init_module+0xc5/0x110
 [1.971088]  [] system_call_fastpath+0x16/0x1b
 [1.971094] Mem-Info:
 [1.971103] active_anon:875 inactive_anon:2049 isolated_anon:0
 [1.971103]  active_file:791 inactive_file:8841 isolated_file:0
 [1.971103]  unevictable:0 dirty:0 writeback:0 unstable:0
 [1.971103]  slab_reclaimable:1732 slab_unreclaimable:1629
 [1.971103]  mapped:1464 shmem:2053 pagetables:480 bounce:0
 [1.971103]  free:4065966 free_pcp:763 free_cma:0
 [1.971131] Node 0 DMA free:15912kB min:12kB low:12kB high:16kB
 

Re: [CentOS-virt] Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes

[Nathan March]

> > I have no issues rolling this patch in , while we wait on upstream, if
> > it makes our tree more stable.
> >
> 
> I think we should do that.. What do others think?
> 

I've had the patch deployed to a group of 32 hosts (with hundreds of vms)
for about 10 days now and no sign of any issues.

So I support it =)

Cheers,
Nathan

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] Kernel 4.12 and nVidia Driver

[Phil Perry]

On 05/09/17 14:11, Alexander Dalloz wrote:

Am 05.09.2017 um 06:16 schrieb Eugene Poole:
I tried to move to the latest stable kernel (4.12) so I could take 


"latest stable kernel (4.12) - that's not a CentOS project kernel. Can 
we guess that you are using the ELrepo kernel-ml?


advantage of my newest custom system (Intel Core I7 6-core; 64 GB RAM; 
MSI nVidia graphics card; 2 - 120 GB SSD; 2 - 4TB WD Black) on a UEFI 
Asrock mother board.


I've had the machine for 3-months but I couldn't get it to work until 
I found out that the Nouveau driver was causing me all the 'hardware' 
issues. I moved to the nVidia driver along with DKMS and all of my 
issues went away until I attempted to upgrade kernel 4.12 ...


It seems that DKMS doesn't automatically upgrade when the kernel is 
upgraded.  Will this issue go away if I change my graphics card to a AMD?


A bit dated, but it holds basic info about DKMS

https://wiki.centos.org/HowTos/BuildingKernelModules#head-d313bd351f90d4f25a2143b7bbcff73f927731f0 



Instead of using DKMS, the kmod-nvidia driver from ELrepo does not fit 
for your graphics card? Or any of the other kmod-nvidia* kernel module 
packages from there?


https://elrepo.org/tiki/kmod-nvidia



The elrepo kmod-nvidia drivers (or any kmods for that point) will only 
work with the distro kernel as they depend on the stable kernel ABI that 
Red Hat maintains in their kernel releases. They will not work with 
non-distro kernels.




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Network Interrogation

[Valeri Galtsev]

On Tue, September 5, 2017 7:33 am, Chris Olson wrote:
>
> Small private networks are a necessary part of our business.
> We also run some small networks with Internet connectivity
> through firewall routers.  The smallest of these networks
> has only a printer and a mix of five CentOS and Windows 7
> machines.
>
> We use a commercial protection product on the W7 system.
> This product has worked well guarding against unwanted
> software on the system for about three and a half years.
> Scans are scheduled and performed routinely once a week
> or on demand at various times.
>
> A recent update to this protection product has caused it
> to start probing the network for other systems.  There is
> sometimes a message following scans indicating that there
> are other systems on our network that are unprotected. It
> appears that the two systems it is naming are a CentOS 6
> system and the HP printer.
>
> This network probing does not happen with every scan that
> is run by the protection software and we have not been able
> to determine what causes that probing to be initiated. We
> also do not know exactly what is happening over the network
> during the probing activity.  The protection software support
> folks have been no help in figuring out what is going on.

Discontinue your use of this "product". Use something that is known to
work and has grate reputation. For home Windows users I recommend free AVG
(they allow one instance free of charge per household). ClamAV and its
internet based Windows virus scanner Immunet. I would strongly warn
against Kaspersky (and any Russian based company for that matter).
Kaspersky himself is KGB man, I doubt you will want to take that chance
with your precious data.

>
> There seems to be no good reason for the probing message to
> name only these two systems. The available printer status
> shows no indication of network traffic associated with this
> probing activity.  The CentOS 6 system also does not indicate
> any related network activity from the system that is running
> the protection software.  We have tried unsuccessfully to
> capture the network probing activity using Wireshark.
>
> Any ideas regarding how to track down what is happening here
> would be greatly appreciated.

Someone probably already recommended wireshark to capture packets. Note,
that removing machine you investigating from network may prompt malware to
stop acting. Internally on Windows you may start with

netstat -nao

and see what is listening to which ports, and attempt to identify which
process belongs to which piece of software. Alas, one can never trust any
tools on compromised machine, so be it UNIX or Linux, I would just
establish that system is compromised, collect what I can on running system
the yank it off network and power (one may argue in favor of clean
shutdown, but that may delete some tracks on its way), and do forensics on
the system drive on clean machines with good forensic tools. I newer
considered it productive to do thorough investigation of compromised
Windows. As opposed to UNIX I already have learned all I need from
forensics of MS Windows: do not use Windows. Most Windows Admins just wipe
the drive and "re-image" the machine.

I hope, this helps.

Valeri


>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel 4.12 and nVidia Driver

[Alexander Dalloz]

Am 05.09.2017 um 06:16 schrieb Eugene Poole:
I tried to move to the latest stable kernel (4.12) so I could take 


"latest stable kernel (4.12) - that's not a CentOS project kernel. Can 
we guess that you are using the ELrepo kernel-ml?


advantage of my newest custom system (Intel Core I7 6-core; 64 GB RAM; 
MSI nVidia graphics card; 2 - 120 GB SSD; 2 - 4TB WD Black) on a UEFI 
Asrock mother board.


I've had the machine for 3-months but I couldn't get it to work until I 
found out that the Nouveau driver was causing me all the 'hardware' 
issues. I moved to the nVidia driver along with DKMS and all of my 
issues went away until I attempted to upgrade kernel 4.12 ...


It seems that DKMS doesn't automatically upgrade when the kernel is 
upgraded.  Will this issue go away if I change my graphics card to a AMD?


A bit dated, but it holds basic info about DKMS

https://wiki.centos.org/HowTos/BuildingKernelModules#head-d313bd351f90d4f25a2143b7bbcff73f927731f0

Instead of using DKMS, the kmod-nvidia driver from ELrepo does not fit 
for your graphics card? Or any of the other kmod-nvidia* kernel module 
packages from there?


https://elrepo.org/tiki/kmod-nvidia

Alexander



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Simple OCSP server ??

[Robert Moskowitz]

Alice,

Have you found an OCSP responder?

I am writing an Internet Draft for using openssl to set up a simple 
ECDSA pki:


https://datatracker.ietf.org/doc/draft-moskowitz-ecdsa-pki/

It is PAST time that the default for certs is RSA, and rather move on to 
ECDSA.  EdDSA is almost ready to ship! (Dan Bernstein's ECC rather than 
NIST/NSA, plus they ARE better curves)


Version 01 is in the works that adds CRL (done) and OCSP (almost done).  
I should have this version posted by middle of next week.


Right now I use self-signed certs for all my servers, but I plan on 
creating my own small PKI and running my own OCSP responder.  I also 
would like to find something 'simple'.


ECDSA will have better response for DANE.  EdDSA will be even better!  
But it will take the NEXT version of openssl to provide support.


Bob

On 04/16/2017 12:43 PM, Robert Moskowitz wrote:

What about the pki package that comes with Centos?

pki-server and pki-ca?

On 04/16/2017 11:54 AM, Alice Wonder wrote:

Oh I don't know, their github works.

However it seems that it isn't able to deal with more than one ocsp 
signing key.


On 04/16/2017 08:40 AM, Robert Moskowitz wrote:



On 04/14/2017 10:41 PM, Alice Wonder wrote:

https://www.openca.org/ might fit my needs.


their Centos repo does not exist, it seems?



On 04/14/2017 06:29 PM, Alice Wonder wrote:

Hello list,

I'm contemplating running my own CA to implement the new proposed ISP
for validation of S/MIME certificates via DANE.

I already use self-signed for my MX servers (with 3 1 1 dane 
records on

TCP port 25) but I don't want to use self-signed for S/MIME for user
specific x.509 certs because

A) That's potentially a lot of DNS records
B) That requires a hash of the e-mail addresses in DNS

Instead, I will be using a wildcard in DNS with an intermediary that
signs the user x.509 certificates.

Using an intermediary to sign their certificates though means I can't
just revoke their certificates by removing the DNS certificate, I'll
need to provide an OCSP server for when one of their private keys 
gets

compromised.

I found
https://access.redhat.com/documentation/en-US/Red_Hat_Certificate_System/8.1/html/Deploy_and_Install_Guide/install-oscp.html 



but it looks like that is intended for enterprise, more complex 
than I

need.

Anyone know of a good simple script for providing OCSP ??

-=-

Not relevant to question but just important for me to note, I will 
*not*
be asking people to install my root certificate in their e-mail 
clients.

I think it is a bad practice to get users in the habit of installing
root certificates.

I think the PKI system has way way way to many root certificates 
as it

is. I want a world where DANE validates most certificates, and only a
few root certificates are needed for things like banks where EV
certificates are a must.

DANE as a way to validate S/MIME I think will be a godsend to e-mail
security, I hope clients implement it.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Network Interrogation

[mad.scientist.at.large]

if you are using vlans i'd suspect the ethernet card in the machines that are 
misbehaving.  for wireshark you probably need to tee the network, or use a 
spare machine to run the ethernet through (bridged)  and run wireshark on the 
inserted machine (there are of course taps).  might also monitor the line that 
comes into the small subnet, assuming you can get the background noise reduced. 
 might also separate (physically) from the lan when probing it internally.

--
The Power Of the People Is Stronger Than The People In Charge.


5. Sep 2017 06:33 by chris_e_ol...@yahoo.com:


> --
> A recent update to this protection product has caused it
> to start probing the network for other systems.  There is
> sometimes a message following scans indicating that there
> are other systems on our network that are unprotected. It
> appears that the two systems it is naming are a CentOS 6
> system and the HP printer.
>
> This network probing does not happen with every scan that
> is run by the protection software and we have not been able
> to determine what causes that probing to be initiated. We
> also do not know exactly what is happening over the network
> during the probing activity.  The protection software support
> folks have been no help in figuring out what is going on.
>
> There seems to be no good reason for the probing message to
> name only these two systems. The available printer status
> shows no indication of network traffic associated with this
> probing activity.  The CentOS 6 system also does not indicate
> any related network activity from the system that is running
> the protection software.  We have tried unsuccessfully to
> capture the network probing activity using Wireshark.
>
> Any ideas regarding how to track down what is happening here
> would be greatly appreciated.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Network Interrogation

[Chris Olson]

Small private networks are a necessary part of our business.
We also run some small networks with Internet connectivity
through firewall routers.  The smallest of these networks
has only a printer and a mix of five CentOS and Windows 7
machines.

We use a commercial protection product on the W7 system.
This product has worked well guarding against unwanted
software on the system for about three and a half years.
Scans are scheduled and performed routinely once a week
or on demand at various times.

A recent update to this protection product has caused it
to start probing the network for other systems.  There is
sometimes a message following scans indicating that there
are other systems on our network that are unprotected. It
appears that the two systems it is naming are a CentOS 6
system and the HP printer.

This network probing does not happen with every scan that
is run by the protection software and we have not been able
to determine what causes that probing to be initiated. We
also do not know exactly what is happening over the network
during the probing activity.  The protection software support
folks have been no help in figuring out what is going on.

There seems to be no good reason for the probing message to
name only these two systems. The available printer status
shows no indication of network traffic associated with this
probing activity.  The CentOS 6 system also does not indicate
any related network activity from the system that is running
the protection software.  We have tried unsuccessfully to
capture the network probing activity using Wireshark.

Any ideas regarding how to track down what is happening here
would be greatly appreciated.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel 4.12 and nVidia Driver

[mad.scientist.at.large]

generally, no it won't update the kernel.  you can get security fixes for it if 
your' system is looking for updates regularly (you should set it to check at 
least daily).  it will usually update a version ( i.e. 2.16 would upgrade to 
2.X.) and if you let it.  you generally don't want auto kernel  updates to a 
different main version numbers as it can break things, and in critical apps 
mostly security patches get loaded, may use the same kernel for many years,  
just applying security updates.

--
The Power Of the People Is Stronger Than The People In Charge.


4. Sep 2017 22:16 by etpool...@comcast.net:


> I tried to move to the latest stable kernel (4.12) so I could take advantage 
> of my newest custom system (Intel Core I7 6-core; 64 GB RAM; MSI nVidia 
> graphics card; 2 - 120 GB SSD; 2 - 4TB WD Black) on a UEFI Asrock mother 
> board.
>
> I've had the machine for 3-months but I couldn't get it to work until I found 
> out that the Nouveau driver was causing me all the 'hardware' issues. I moved 
> to the nVidia driver along with DKMS and all of my issues went away until I 
> attempted to upgrade kernel 4.12 ...
>
> It seems that DKMS doesn't automatically upgrade when the kernel is upgraded. 
>  Will this issue go away if I change my graphics card to a AMD?
>
> -- 
> Eugene Poole
> Woodstock, Georgia
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] lightdm dependency

[Philippe BOURDEU d'AGUERRE]

Le 05/09/2017 à 07:01, Jon LaBadie a écrit :

On a CentOS 7 system I'm trying to install lightdm.
Yum says it requires "glib2(x86-64) >= 2.50.3".
glib2 2.46 is installed but I have not found a
2.50 version.  Have I overlooked it in some repo?


Same problem here. You can find glib2 2.50.3 in cr repository.
--
Philippe BOURDEU d'AGUERRE
AIME - Campus de l'INSA http://aime-toulouse.fr/
135 av. de Rangueil Tél +33 561 559 885
31077 TOULOUSE Cedex 4 - FRANCE Fax +33 561 559 870
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos