Discuss

discuss@lists.centos.org

34753 discussions

[PKI concepts] Why Jboss need (signed cert and) root-cert in PEM format?
by Sven Aluoor 21 Jan '10

21 Jan '10

Hi folks [ Please add me CC. Thanks ] We have here a Jboss app and web server. We signed the SSL-certificate that end-user don't have ugly error messages. I don't understand why we need to import the Root-Cert in PEM format? $ keytool -import -trustcacerts -file rootcert.pem -keystore myserver.keystore -alias root The Root-Cert is in web browser, why there is a must to import in keystore? Did I misunderstood PKI basics? cheers Sven

2 1

update of openssh-server i386 4.3p2-36.el5, dependencies
by zagiatakrapovic＠gmx.ch 21 Jan '10

21 Jan '10

thx for your help Filipe, I see the point! unfortunately I got the same for ecryptfs-utils until now no GTK stuff was needed... now even if I try your hint > yum update ecryptfs-utils I think the trousers rpm is pulling the whole stuff. Until now I didn't had to install trousers. output: --------------- Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Updating: ecryptfs-utils i386 75-5.el5 updates 157 k Installing for dependencies: atk i386 1.12.2-1.fc6 base 222 k cairo i386 1.2.4-5.el5 base 394 k cups-libs i386 1:1.3.7-8.el5_3.6 updates 193 k fontconfig i386 2.4.1-7.el5 base 174 k freetype i386 2.2.1-21.el5_3 updates 310 k gnutls i386 1.4.1-3.el5_3.5 updates 348 k gtk2 i386 2.10.4-20.el5 base 6.5 M hicolor-icon-theme noarch 0.9-2.1 base 25 k keyutils i386 1.2-1.el5 base 36 k libX11 i386 1.0.3-9.el5 base 795 k libXau i386 1.0.1-3.1 base 18 k libXcursor i386 1.1.7-1.1 base 32 k libXdmcp i386 1.0.1-2.1 base 19 k libXext i386 1.0.1-2.1 base 35 k libXfixes i386 4.0.1-2.1 base 14 k libXft i386 2.1.10-1.1 base 44 k libXi i386 1.0.1-3.1 base 25 k libXinerama i386 1.0.1-2.1 base 9.7 k libXrandr i386 1.1.1-3.1 base 15 k libXrender i386 0.9.1-3.1 base 27 k libjpeg i386 6b-37 base 139 k libpng i386 2:1.2.10-7.1.el5_3.2 updates 241 k libtiff i386 3.8.2-7.el5_3.4 updates 306 k pango i386 1.14.9-5.el5.centos updates 335 k trousers i386 0.3.1-4.el5 base 308 k xorg-x11-filesystem noarch 7.1-2.fc6 base 5.4 k Transaction Summary ============================================================================= Install 26 Package(s) Update 1 Package(s) Remove 0 Package(s) -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

6 5

PAM and GNOME keyring
by Giulio Troccoli 21 Jan '10

21 Jan '10

Hi everybody, I have a CentOS 5.4 server I need to se-up as Subversion server. On the server GNOME keyring has been installed and the integration with Subversion works fine: I'm asked for the keyring password the first time and that's it. I am now trying to set it up so that after login the default keyring is unlocked. This way I won't be asked for the keyring password ever. I have followed the instructions found at http://fedoraproject.org/wiki/Tools/NetworkManager#Gnome-specific_informati… but it doesn't work. I have rebooted the server few times with no avail. I have checked that my password and the keyring password are the same. Every time I run a Subversion command I'm prompted for the keyring password. Can anyone help me? Please reply to me too as I am not subscribed to the list. Thanks Giulio Linedata Services (UK) Ltd Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB Registered in England and Wales No 3027851 VAT Reg No 778499447

1 0

Xorg without xorg.conf (a bit OT)
by Ron Blizzard 21 Jan '10

21 Jan '10

I like to try out other distributions of Linux. Today I took a look at Mint Linux 8 and Fedora 12. I installed and updated each on a small partition -- actual physical install, not virtual machines. Both worked great at 1280x1024 (their defaults) but neither would let me use 1024x768 resolution. Both came with newer versions of Xorg, neither of which build an xorg.conf file. Mint gave me three settings, 1280x1024, 640x480 and something like 700x400(?). Fedora gave me the choice of 1024x768, but when I tried to use it, it just went black until timing out. When I downloaded and ran system-config-display, it built an xorg.conf file, which I modified to 1024x768 (by removing the 1280x1024 selection). When I tried rebooting, it locked up. (I have an Intel 865G video chip, BTW.) So, what is it about the newer versions of Xorg that doesn't like 1024x758 resolution? At least not on an Intel Graphics chip? Just weird. And I'm curious as to how Xorg determines its monitor resolution choices when there is no xorg.conf file. Is there a good tutorial on this subject available? Frustrating situation -- and I'm still nervous that Red Hat 6 is going to end up with the same issue -- if this is an Xorg problem with Intel it seems reasonable to assume that they will inherit it. -- RonB -- Using CentOS 5.4

2 1

Re: [CentOS] cryptoloop
by Morten Sundstrøm 21 Jan '10

21 Jan '10

I know about that. Is that the reason it wont work in ubuntu? If I switch to a new encryption i must copy all the data to a new raid wich is not possible at the moment. I need to get this mounted. /MS ----- Original Message ----- Fra: "Pasi Kärkkäinen" <pasik(a)iki.fi> Til: "CentOS mailing list" <centos(a)centos.org> Sendt: 21. januar 2010 09:57:24 Emne: Re: [CentOS] cryptoloop On Thu, Jan 21, 2010 at 09:41:37AM +0100, Morten Sundstrøm wrote: > Hi. > > Have a problem that i need som help with: > 1. Have multipple raids working in a encrypted filesystem in CentOS 5.4 (i386): script file, crypt.sh > > modprobe cryptoloop > cryptoloop is depracated, and should not be used. Use dm-crypt instead, or if you have to, loop-aes. -- Pasi > losetup -e aes /dev/loop0 /dev/md0 > (inserting password here) > then run > mount -t ext3 /dev/loop0 /mnt/raid5 > Have been using this in CentOS for a long time and works like a charm. > > 2. Raids is now moved to another server with ubuntu server 9.10 (64bit) > Raid is detected fine and working. > > Do the same thing again and get: > sudo modprobe cryptoloop (ok) > sudo losetup -e aes /dev/loop0 /dev/md0 (ok) > sudo mount -t ext3 /dev/loop0 /mnt/raid5 (failes with the following msg) > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > ubuntu: cat /proc/crypto |grep aes > name : ecb(aes) > driver : ecb(aes-asm) > name : cbc(aes) > driver : cbc(aes-asm) > name : cbc(aes) > driver : cbc(aes-asm) > name : aes > driver : aes-asm > module : aes_x86_64 > name : aes > driver : aes-generic > module : aes_generic > > Is there compatible issues here? > Can it be that the old server was using i386 arch and the new is 64bit? > losetup version differs? > > Any insight is appreciated. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

mysql Workbench
by Rajagopal Swaminathan 21 Jan '10

21 Jan '10

Greetings, Is there a centos repo with mysql workbench anywhere. In the same vein, is there a publicly available build system for centos where people can submit the source tar.gz and get hotly baked rpm and the icing would be with some way to resolve dependencies?? It would be great to have one.. Regards and thanks, Rajagopal

6 16

cryptoloop
by Morten Sundstrøm 21 Jan '10

21 Jan '10

Hi. Have a problem that i need som help with: 1. Have multipple raids working in a encrypted filesystem in CentOS 5.4 (i386): script file, crypt.sh modprobe cryptoloop losetup -e aes /dev/loop0 /dev/md0 (inserting password here) then run mount -t ext3 /dev/loop0 /mnt/raid5 Have been using this in CentOS for a long time and works like a charm. 2. Raids is now moved to another server with ubuntu server 9.10 (64bit) Raid is detected fine and working. Do the same thing again and get: sudo modprobe cryptoloop (ok) sudo losetup -e aes /dev/loop0 /dev/md0 (ok) sudo mount -t ext3 /dev/loop0 /mnt/raid5 (failes with the following msg) mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so ubuntu: cat /proc/crypto |grep aes name : ecb(aes) driver : ecb(aes-asm) name : cbc(aes) driver : cbc(aes-asm) name : cbc(aes) driver : cbc(aes-asm) name : aes driver : aes-asm module : aes_x86_64 name : aes driver : aes-generic module : aes_generic Is there compatible issues here? Can it be that the old server was using i386 arch and the new is 64bit? losetup version differs? Any insight is appreciated.

2 1

perl updates always break perl programs, how to fix?
by James Chase 21 Jan '10

21 Jan '10

I realize this is my fault because once upon a time I installed a package using CPAN and probably other admins on the system have as well but now whenever I update perl I have to jump through hoops to get perl applications to work again (usually updating Scalar::Util and another package with CPAN). I would love to figure out how to fix this so it's not such a headache to keep up to date with perl, but I can't figure out how. I tried moving my /usr/lib/perl5/site_perl directory out of the way and installing perl-Scar-Util using yum but it doesn't let me because the perl-5.8.8 rpm owns the man file for that. I'm not sure why the default Scalar-Util (isn't it built in to the base install of perl on CentOS) doesn't work in the first place? Also I do add perl packages via the dag/rpmforge repo, not sure if that messes up the perl updates too. Sorry I realize this could also be classified as a perl question -- but I'm hopeful other centos admins found a way to get their centos back into compliance with the yum updates. Thanks, James -- "Beware of all enterprises that require new clothes." -- Henry David Thoreau

3 2

Re: [CentOS] followup to request for centos C/W
by fabien faye 21 Jan '10

21 Jan '10

Like i have understood, xen could be also present and support on RHEL6 and in this case, it could be supported until the cycle of RHEL 6. But is it preferable to migrate all your xen to kvm in a near furtur. Kvm is a REDHAT project and REDHAT want to put all ressources to improve and develop KVM instead of xen. Fabien FAYE RHCE www.generationip.com On 1/20/10 7:14 PM, fabien faye wrote: > I can confirm, after my last discussion with Redhat, is it better to learn KVM. > Xen is going to die on redhat and centos in some years. In some years? It is supported until support cycle is over. So, in RHEL 5.4 due date is: 31 Mar 2014 Anyway, the same gui tools works for xen and kvm also.. -- Eero, RHCE _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

routing multiple network cards on a single subnet
by Frank Cox 20 Jan '10

20 Jan '10

I have dealt with machines that have multiple network cards in them before, but never when they were on the same subnet so this issue has never come up before. My problem is that I can only access one IP address at a time. I started out using dhcp and found that if I went through the dhcp song-and-dance then that address became active and the other one was disabled, and vice versa. On our local tech mailing list, a couple of the guys advised me that this is due to a routing issue and, after a bit of googling around I now understand why that is. However, I have so far been unable to fix it. I got rid of dhcp and set up static addresses using system-config-network. This machine has three network cards in it, eth0 is 192.168.1.5 and I use that one to ssh into the box from this computer. (I really don't want to lose my ability to connect to eth0; this machine runs headless on a shelf about 7 feet above the floor and it would be quite an undertaking to dismantle it and bring it down to hook a monitor and keyboard to it again.) The solution to this problem appears to be easier to describe than to implement, at least for me. I need to have each network card reply back on the same interface that it received a request from. eth1 is 24.89.92.178 eth2 is 24.89.92.180 The gateway for both of these is 24.89.92.1 The suggestion that I got was to add two entries to the end of /etc/iproute2/rt_tables (which I did with a text editor) and run a series of ip route commands which set up a custom routing table but I'm missing something because while the custom routing tables appear to be getting set up, it's still not working. I have studied the suggested routing commands and I think I understand what they are doing and what is supposed to be happening. But something is still missing because it's not working. Here is what I did and what the results are. If I have missed anything let me know; this covers what I think is the relevant information as I currently understand it. I would sincerely appreciate any further advice regarding this situation. I really would like to know what I am doing wrong and also why (in the interest of learning something from this situation). It's new territory for me. [root@audio ~]# cat /etc/iproute2/rt_tables # # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep 50 access1 60 access2 [root@audio ~]# ip route add 24.89.92.0/24 dev eth1 table access1 [root@audio ~]# ip route add default via 24.89.92.1 table access1 [root@audio ~]# ip rule add from 24.89.92.178/32 lookup access1 [root@audio ~]# [root@audio ~]# ip route add 24.89.92.0/24 dev eth2 table access2 [root@audio ~]# ip route add default via 24.89.92.1 table access2 [root@audio ~]# ip rule add from 24.89.92.180/32 lookup access2 [root@audio ~]# ip route show table access2 24.89.92.0/24 dev eth2 scope link default via 24.89.92.1 dev eth1 [root@audio ~]# ip route show table access1 24.89.92.0/24 dev eth1 scope link default via 24.89.92.1 dev eth1 [root@audio ~]# ip route 24.89.92.0/24 dev eth1 proto kernel scope link src 24.89.92.178 24.89.92.0/24 dev eth2 proto kernel scope link src 24.89.92.180 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.5 169.254.0.0/16 dev eth2 scope link default via 24.89.92.1 dev eth1 [frankcox@mutt ~]$ ping 24.89.92.178 PING 24.89.92.178 (24.89.92.178) 56(84) bytes of data. 64 bytes from 24.89.92.178: icmp_seq=1 ttl=50 time=92.2 ms 64 bytes from 24.89.92.178: icmp_seq=2 ttl=50 time=96.2 ms 64 bytes from 24.89.92.178: icmp_seq=3 ttl=50 time=91.0 ms --- 24.89.92.178 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 91.023/93.193/96.263/2.245 ms [frankcox@mutt ~]$ ping 24.89.92.180 PING 24.89.92.180 (24.89.92.180) 56(84) bytes of data. --- 24.89.92.180 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 5000ms Incidentally, it is my current understanding that anything that I do with an "ip route" command will go away on a reboot, therefore if I somehow screw up the routing on this box completely all I have to do is reboot it and I'll be back to what I had before. Which is not a bad thing at the moment. Once I have this nailed down should I put the "ip route" commands into /etc/rc.local? Or is there a better place? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

10 25

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