Discuss

discuss@lists.centos.org

34758 discussions

upcoming mailman version change?
by Dave Stevens 23 Nov '10

23 Nov '10

Hi, I'm using CentOS on a box that, among other things, offers mailman mailing lists, currently mailman 2.1.9. Version 2.1.14 is avilable from the developers but integrating it into the system promises to be tedious. I looked at RHEL 6 and don't know where to look to find the version there, which I assume will be the version in CentOS 6. Can anyone either confirm what version will be in C6 or where to find the full feature list in RHEL 6? Dave -- "It is no measure of health to be well adjusted to a profoundly sick society." Krishnamurti

2 2

where to download tzdata-java-20101-1.e15 RPM fro CENTOS 5.5 X86?
by mcclnx mcc 22 Nov '10

22 Nov '10

I am installed CENTOS 5.5 on X86. After finish, I tried to apply latest patches. Rpm patch manager say need "dependency" "tzdata-java-20101-1.e15". I search CENTOS 5.5 CD and can NOT find this file. I also search Internet and no result. Can anyone tell me where to download "tzdata-java-20101-1.e15" RPM? Thanks.

3 2

firefox. java. 64 bit. bleah!
by m.roth＠5-cent.us 22 Nov '10

22 Nov '10

Found this <http://plugindoc.mozdev.org/linux-amd64.html#java-sun>, and I remember the plugins directory... except firefox 3.6.11, I can't find any, not in ~/.mozilla, not in /usr/lib64/mozilla. Anyone have a clue for the poor? mark

4 6

Re: [CentOS] Router for SOHO network - hardware considerations
by Bob Puff＠NLE 22 Nov '10

22 Nov '10

I am looking for something similar to this thread.. Is there a way to make a small CentOS distro that is bootable and runnable from only a USB memory stick? It would need to be able to have files modified, but I wouldn't want the USB stick to die prematurely due to a ton of writes... Bob

2 1

Strange ntp behaviour?
by Robert Moskowitz 22 Nov '10

22 Nov '10

The following is from my logwatch email: --------------------- XNTPD Begin ------------------------ XNTPD Killed: 7 Time(s) XNTPD Started: 8 Time(s) Total interfaces 8 (non-local: 4) Total synchronizations 6 (hosts: 1) Errors getaddrinfo: "0.centos.pool.ntp.org" invalid host address, ignored: 2 time(s) getaddrinfo: "1.centos.pool.ntp.org" invalid host address, ignored: 2 time(s) getaddrinfo: "2.centos.pool.ntp.org" invalid host address, ignored: 2 time(s) ---------------------- XNTPD End ------------------------- Yet from this host I get: # host 0.centos.pool.ntp.org 0.centos.pool.ntp.org has address 208.53.158.34 0.centos.pool.ntp.org has address 69.50.219.51 0.centos.pool.ntp.org has address 108.76.168.145 So what is NTP doing here; why the errors for getaddrinfo? Or is this nothing more than 2 out of some many times getaddrinfo failed, but worked just fine enough to count?

2 2

TC Filter Flows & ESFQ - Traffic Shaping
by Frederick Abrams 22 Nov '10

22 Nov '10

Hi, We currently have ESFQ running on an old Fedora machine and i'm trying to build a new router with something similar using CentOS 5.5 The problem is that it seems by default the CentOS is not compiled with TC ESFQ or TC filter hash flows I get the following error: Unknown filter "flow", hence option "hash" is unparsable How can i add support for the hash flow option or ESFQ or perhaps someone can suggest a better option where I can get the same functionality of even sharing based on src / dst tc filter add dev eth0 parent 10: protocol ip handle 10 flow hash keys dst divisor 1024 -- Fred -- This message has been scanned for viruses and dangerous content by Intelvision MailScanner, and is believed to be clean.

1 0

"Cracking Passwords In The Cloud: Amazon’s New EC2 GPU Instances" -- using CentOS
by Timo Schoeler 22 Nov '10

22 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, in case someone missed it: CentOS was used in a EC2 setup to demonstrate GPU-based brute force cracking of passwords. "Cracking Passwords In The Cloud: Amazon’s New EC2 GPU Instances" http://stacksmashing.net/2010/11/15/cracking-in-the-cloud-amazons-new-ec2-g… See also: http://it.slashdot.org/story/10/11/16/1549245/Cracking-Passwords-With-Amazo… Cheers, Timo :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFM6i59fg746kcGBOwRAoioAKC6oCVuh0meM5ynVUe7L+a3JlLFHgCeMivH nwFIhD4rcm6pP66uE9/M3Uo= =ZWeW -----END PGP SIGNATURE-----

1 0

Routing of outgoing packets
by Mitja Mihelič 22 Nov '10

22 Nov '10

Hi! I am trying to use hping to chek the latency of our network. Somehow things are not going to plan and I thought someone might be able to shed some light on the subject. Here is the setup: (the IP addresses gvien here are fake, but they do represent the correct state of the networking setup) vlan interface IP mask V2 eth0 192.168.20.20 32 V4 eth1 172.16.4.40 32 V6 eth2 172.16.6.60 32 The default route is set to eth1. The idea is to use eth2 for pinging only, the other two interfaces are used by another service and management access. If I do: ping -c 2 -I eth2 74.125.39.147 or fping -c 2 -I eth2 74.125.39.147 It binds to eth2 and sends its ICMP probes via that interface with the IP on that interface. If I do: hping3 -1 -c 2 -I eth2 74.125.39.147 -VD or [root@server ~]# hping3 -c 2 -I eth2 74.125.39.147 -VD DEBUG: if lo: Don't Match (but seems to be UP) DEBUG: if eth0: Don't Match (but seems to be UP) DEBUG: if eth1: Don't Match (but seems to be UP) DEBUG: if eth2: OK using eth2, addr: 172.16.6.60, MTU: 1500 It supposedly binds to eth2. But tcpdump tells another story. Packets get sent out via the default route (eth1) with the IP from eth2 set as the source address. The same happens with tcptraceroute (tcptraceroute-1.5-0.beta7.el5.rf.i386.rpm). I have tried various routing policies, but I have yet to find a solution that works. I have used iptables to log the packets in the OUTPUT chain, but they arrive there with the interface already set to eth1. Can anyone help ? Regards, Mitja Mihelic

3 3

Centos 4 and cgiemail
by Todd Cary 22 Nov '10

22 Nov '10

I am running Centos 4 and want to run cgiemail in a directory under the web application. The setting of the "value" property in the <form> is tricky, but I have the web application running on other servers without a problem. On my server I get the error that it cannot find the file pointed to by the value in the <form>. My question is whether or not I need to do something special like install an application on the server or do something special with permissions (the cgiemail is owned by apache and has 775 for permissions). The web app is in the "interact" folder with the cgiemail in cgi-bin under it. Works on other servers. Many thanks... Todd -- Ariste Software Petaluma, CA 94952 http://www.aristesoftware.com

2 5

LDAP clients fail to connect with SSL enabled
by bluethundr 21 Nov '10

21 Nov '10

I am attempting to setup SSL/TLS support on my openLDAP 2.4 server on FreeBSD. LBSD2# pkg_info | grep openldap openldap-sasl-client-2.4.23 Open source LDAP client implementation with SASL2 support openldap-sasl-server-2.4.23 Open source LDAP server implementation I put my cert file, key file and CA certfile in a directory called /usr/local/etc/openldap/cacerts Here's how it looks: [root@LBSD2:/usr/local/etc/openldap/cacerts]#ls -l total 48 dr--r----- 2 root ldap 512 Nov 21 17:12 bak -r--r----- 1 root ldap 1960 Nov 21 07:05 bsd2.summitnjhome.com.crt -r--r----- 1 root ldap 4604 Nov 21 17:16 gd_bundle.crt -r--r----- 1 root ldap 4689 Nov 21 18:59 sf_bundle.crt -r--r----- 1 root ldap 1537 Nov 21 17:16 sf_issuing.crt -r--r----- 1 root ldap 1090 Nov 21 12:29 slapd.csr -r--r----- 1 root ldap 1743 Nov 21 12:26 slapd.key -r--r----- 1 root ldap 1675 Nov 21 17:25 slapd.pem My cert flie is a GoDaddy turbo-ssl certfile named bsd2.summitnjhome.com.crt. slapd.key is the key file and slapd.pem is the same thing only with the password removed. I'm a little unsure of which CA file to use but I think that sf_issuing.crt _should_ work as this is the CA file that I used to setup a similar SSL enabled LDAP server for a client recently. Although I have tried all three CA files in this directory: (gd_bundle.crt, sf_bundle.crt, and sf_issuing.crt). I put the various cert/key files into my slapd.conf file like this: LBSD2# cat slapd.conf | grep -i tls ## TLS options for slapd TLSCipherSuite HIGH:MEDIUM:+SSLv2 TLSCertificateFile /usr/local/etc/openldap/cacerts/bsd2.summitnjhome.com.crt TLSCertificateKeyFile /usr/local/etc/openldap/cacerts/slapd.pem TLSCACertificateFile /usr/local/etc/openldap/cacerts/sf_issuing.crt Slapd restarts cleanly! LBSD2# /usr/local/etc/rc.d/slapd restart Stopping slapd. Waiting for PIDS: 81924. Starting slapd. Then I attempt to setup a virtual instance of CentOS 5.5 on the client side and that's where things fall apart...I attempt to ssh to localhost as an LDAP account: [root@VIRTCENT08:/etc/openldap/cacerts]#ssh bluethundr@localhost [...tectonic plates drift, careers begin and end, babies learn to walk, talk and grow to adulthood..] Connection closed by 127.0.0.1 [root@VIRTCENT08:/etc/openldap/cacerts]#getent passwd | grep ldapAccount [same interminable wait as above] This is what my /etc/ldap.conf file looks like on the client: [root@VIRTCENT08:/etc/openldap/cacerts]#cat /etc/ldap.conf # Your LDAP server. Must be resolvable without using LDAP. # Multiple hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). #host 127.0.0.1 # The distinguished name of the search base. base dc=summitnjhome,dc=com # stored in /etc/ldap.secret (mode 600) #rootbinddn cn=manager,dc=example,dc=com # The port. # Optional: default is 389. #port 389 # Search timelimit #timelimit 30 timelimit 120 # Bind/connect timelimit #bind_timelimit 30 bind_timelimit 120 # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 idle_timelimit 3600 # Netscape SDK LDAPS #ssl on # Netscape SDK SSL options #sslpath /etc/ssl/certs # OpenLDAP SSL mechanism # start_tls mechanism uses the normal LDAP port, LDAPS typically 636 #ssl start_tls #ssl on # OpenLDAP SSL options # Require and verify server certificate (yes/no) # Default is to use libldap's default behavior, which can be configured in # /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for # OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes". #tls_checkpeer yes # CA certificates for server certificate verification # At least one of these are required if tls_checkpeer is "yes" #tls_cacertfile /etc/ssl/ca.cert #tls_cacertdir /etc/ssl/certs # SSL cipher suite # See man ciphers for syntax #tls_ciphers TLSv1 # Client certificate and key # Use these, if your server requires client authentication. #tls_cert #tls_key # SASL mechanism for PAM authentication - use is experimental # at present and does not support password policy control uri ldap://ldap.summitnjhome.com/ ssl start_tls tls_cacertdir /etc/openldap/cacerts pam_password crypt This is how my nsswitch on the client side is setup: passwd: files ldap shadow: files ldap group: files ldap And here is the cert dir on my CentOS client: [root@VIRTCENT08:/etc/openldap/cacerts]#ls -l total 72 lrwxrwxrwx 1 root root 13 Nov 21 09:44 97552d04.0 -> gd_bundle.crt lrwxrwxrwx 1 root root 14 Nov 21 09:44 b737b221.0 -> sf_issuing.crt dr--r--r-- 2 root root 4096 Nov 21 2010 bak -r--r--r-- 1 root root 1960 Nov 21 07:05 bsd2.summitnjhome.com.crt lrwxrwxrwx 1 root root 25 Nov 21 09:44 c75be861.0 -> bsd2.summitnjhome.com.crt -r--r--r-- 1 root root 4604 Nov 21 2010 gd_bundle.crt -r--r--r-- 1 root root 1537 Nov 21 2010 sf_issuing.crt -r--r--r-- 1 root root 1090 Nov 21 12:29 slapd.csr -r--r--r-- 1 root root 1743 Nov 21 12:26 slapd.key -r--r--r-- 1 root root 1675 Nov 21 2010 slapd.pem Back on the server side there is a lot of activity in the ldap logs (here is an excerpt) Nov 21 20:21:38 LBSD2 slapd[81972]: daemon: read activity on 11 Nov 21 20:21:38 LBSD2 slapd[81972]: daemon: select: listen=6 active_threads=0 tvp=NULL Nov 21 20:21:38 LBSD2 slapd[81972]: daemon: select: listen=7 active_threads=0 tvp=NULL Nov 21 20:21:38 LBSD2 slapd[81972]: connection_read(11): input error=-2 id=1017, closing. Nov 21 20:21:38 LBSD2 slapd[81972]: connection_closing: readying conn=1017 sd=11 for close Nov 21 20:21:38 LBSD2 slapd[81972]: daemon: activity on 1 descriptor I've encloses a more complete log file as an attachment. I then try to show the CA files with an openssl command. First with sf_issuing.crt - slapd.conf: TLSCACertificateFile /usr/local/etc/openldap/cacerts/sf_issuing.crt On the client: [root@VIRTCENT08:/etc/openldap/cacerts]#openssl s_client -connect ldap.summitnjhome.com:389 -showcerts -CAfile sf_issuing.crt CONNECTED(00000003) 3143:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:188 Next with sf_bundle.crt - slapd.conf: TLSCACertificateFile /usr/local/etc/openldap/cacerts/sf_bundle.crt [root@VIRTCENT08:/etc/openldap/cacerts]#openssl s_client -connect ldap.summitnjhome.com:389 -showcerts -CAfile sf_bundle.crt 3149:error:02001002:system library:fopen:No such file or directory:bss_file.c:122:fopen('sf_bundle.crt','r') 3149:error:2006D080:BIO routines:BIO_new_file:no such file:bss_file.c:125: 3149:error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:by_file.c:279: CONNECTED(00000003) 3149:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:188: Next with gd_bundle.crt - TLSCACertificateFile /usr/local/etc/openldap/cacerts/gd_bundle.crt [root@VIRTCENT08:/etc/openldap/cacerts]#openssl s_client -connect ldap.summitnjhome.com:389 -showcerts -CAfile gd_bundle.crt CONNECTED(00000003) 3156:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:188: Disabling TLS on the client side authentication works again! [root@VIRTCENT08:/etc/openldap/cacerts]#ssh bluethundr@localhost bluethundr@localhost's password: Last login: Sun Nov 21 09:41:34 2010 from 192.168.1.50 ######################################################### # SUMMITNJHOME.COM # # TITLE: VIRTCENT08 BOX # # LOCATION: SUMMIT BASEMENT # # # ######################################################### Any thought on how to resolve the current situation would be most appreciated! ;) -- Here's my RSA Public key: gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9 Share and enjoy!!

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss