Discuss November 2013

discuss@lists.centos.org

160 participants
173 discussions

X11 connection rejected because of wrong authentication
by Timothy Murphy 26 Nov '13

26 Nov '13

I'd like to run SELinux on my CentOS server in enforcing mode, but I get the above message when I run sealert. I assume this is because I am accessing the server from my laptop? In any case, I googled for the message, and this threw up dozens of similar queries over many years. Most of the ones I read offered methods of avoiding the problem rather than solving it. Am I right in thinking the message arises from my remote connection? And if so, is there a simple solution? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 4

CentOS 6 : Network Interface Naming
by SilverTip257 25 Nov '13

25 Nov '13

Hello All, I have one CentOS 6 KVM virtualization server that I built around a year ago (best I can tell it was in October 2012) at which time I would have been installing 6.3 [0]. That particular install used the Consistent Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2). I started to build out a new KVM virt server (kickstarting a 6.4 install now as compared to 6.3 back then) and the interface names are back to the old ethX convention for the PCIe NICs. See below for my snippets from udev persistent rules on the two hosts. I'm working off of [older] Dell PowerEdge 2950 hardware that has dual onboard Broadcom NICs and an additional Intel Dual GigE PCIe NIC. ** Did anyone but me notice this change/regression in network interface naming? ** Does anyone know if or why a change was made from what 6.3 or earlier apparently defaulted to? This is by no means a major problem, but it did make me wonder what caused or why there was a change. [Of course I can change interface names in the udev rules if I chose to.] Thanks for your feedback! ================== Snippets: # was 6.3 when initially installed, but has been updated to 6.4 since then ~]# cat /etc/*ele* CentOS release 6.4 (Final) CentOS release 6.4 (Final) CentOS release 6.4 (Final) cpe:/o:centos:linux:6:GA ~]# egrep -v '^$|^#' /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="p1p1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="p1p2" ~]# lspci | grep Ether 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 0c:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 0c:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) # freshly installed 6.4 ~]# cat /etc/*ele* CentOS release 6.4 (Final) CentOS release 6.4 (Final) CentOS release 6.4 (Final) cpe:/o:centos:linux:6:GA ~]# egrep -v '^$|^#' /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" ~]# lspci | grep Ether 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) [0] https://access.redhat.com/site/articles/3078 [1] https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux… -- ---~~.~~--- Mike // SilverTip257 //

5 6

intel
by madunix＠gmail.com 25 Nov '13

25 Nov '13

I am in the process of getting multiple Desktops to run linuxfor Research and Development, at the moment am comparing the following intel chipset H81, Q87, Q77, H61...What is the difference?What would be best performance issue?

3 4

Wrap around to first/last work space
by Wes James 25 Nov '13

25 Nov '13

Is there a way to get CentOS 6.4 to wrap from last to first or first to last workspace when moving with ctl-alt left/right arrow? I right clicked on the workspace view at the bottom right and selected Preferences, but there are now options for that. Thanks, -wes

3 10

ltsp & Selinux
by Johan Vermeulen 25 Nov '13

25 Nov '13

Hello All, I set up ltsp regulary, on Centos6 machines. This morning I have a Selinux problem that usualy does not occur: after setting everything up, the thinclients boot, but nobody can login. It only works after the command : # echo 0 > /selinux/enforce I tried this semanage command: # semanage fcontext -a -t bin_t /usr/bin/xauth but it makes no difference. The message I'm now seeing in /var/log/audit/audit.log : type=AVC msg=audit(1385112688.399:67769): avc: denied { write } for pid=8218 comm="xauth" name="caw" dev=md1 ino=262145 scontext=unconfined_u:unconfined_r:xauth_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:home_root_t:s0 tclass=dir type=SYSCALL msg=audit(1385112688.399:67769): arch=c000003e syscall=2 success=no exit=-13 a0=7fffdecf5c60 a1=c1 a2=180 a3=8 items=0 ppid=8217 pid=8218 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=9 comm="xauth" exe="/usr/bin/xauth" subj=unconfined_u:unconfined_r:xauth_t:s0-s0:c0.c1023 key=(null) Can anybody help me overcome this without disabling Selinux? Many thanks. Greetings, J. -- Johan Vermeulen IT-medewerker Opensource Software is the future.

3 5

Google Chrome
by Michael B Allen 25 Nov '13

25 Nov '13

I have been using CentOS on my laptop for a few days now and it works great! Great work-around for the Fedora GNOME 3 debacle. But I'm starting to miss Google Chrome pretty seriously. Firefox is just not what it once was. It's slow. Spell check is weak. Sometimes it straight up fails to display pages after going "back". There are numerous details like this that just make FF almost intolerable. And based on current browser usage statistics I don't think I'm the only one who sees the difference which means the problem is only going to get worse. Unfortunately Chrome is not available for CentOS 6.4: Error: Package: google-chrome-stable-31.0.1650.57-1.x86_64 (google-chrome) Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) This page [http://www.muktware.com/2013/02/google-says-red-hat-enterprise-linux-6-is-o…] claims: "Chrome, the browser in question here, is based on the open source project Chromium. Chromium developers seems to prefer the new C++11 for the obvious security reasons and ease of maintenance but it also means adopting a new toolchain and upgrading to GCC 4.6. This makes it hard to support those operating systems that ship with older C++ standard libraries. RHEL 6, among many others, is one such operating system." What is the safest path out of this problem? I am not particularly excited about running a package from a small third party. Particularly a browser. Is this situation really that bad? Mike

11 14

Re: [CentOS] X11 connection rejected because of wrong authentication
by James B. Byrne 25 Nov '13

25 Nov '13

On Sun, November 24, 2013 20:08, Timothy Murphy wrote: > I'd like to run SELinux on my CentOS server in enforcing mode, > but I get the above message when I run sealert. > I assume this is because I am accessing the server from my laptop? > > In any case, I googled for the message, > and this threw up dozens of similar queries over many years. > Most of the ones I read offered methods of avoiding the problem > rather than solving it. > > Am I right in thinking the message arises from my remote connection? Yes. It arises from your ssh connection. You are probably using the -Y or -X option with xauth. > And if so, is there a simple solution? Perhaps. The error you have is caused by one of two things: 1. incorrect SELinux settings on the ~/.Xauthority file or your home directory. Run restorcon -vR ~ to fix those. 2. incorrect ownership or permissions on ~/.Xauthority. The second condition can also be triggered by logging in via ssh as one user and su -l to another on the remote host. In my case I find that the second circumstance is the most frequent cause of the exact error you report. HTH -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Re: [CentOS] Any experience with lanner appliances?
by John Doe 25 Nov '13

25 Nov '13

From: Steve Clark <sclark(a)netwolves.com> > We have about 1000 FW-7535s (replaced by FW-7541) deployed using > CentOS 6.x. I finally chose to go with the microserver... I have a hard time finding a simple price for the lanner appliance (without having to fill some huge forms to get a quotation...) And last time, when I did find one price, it was more than $800 which feels too much for some "above average soho router like hardware". Thank you both for the info,JD

1 0

MultiTech MT5634ZBA usb modems
by Gregory P. Ennis 24 Nov '13

24 Nov '13

Everyone, I have a centos 5.10 machine set up to be a fax server using hylafax+ with three multitech MT5634ZBA modems. I am still in the testing phase of using this system for production, and during my tests I have detected a problem I have not been able to solve except for unplugging the modem from the usb port and plugging it back into the usb port. In the middle of a fax production of around 1,000 faxes the ttyACM0 device becomes disabled and disappears. I have only had this happen twice so I have not collected sufficient data to figure out what is happening. When I remotely reboot the os, the system comes up and ignores the modem that has become faulty, and of course ttyACM0 is assigned to a different modem. Has anyone had problems with the MT5634SBA modems, and if so what modems would you recommend by way of replacements. Is there a way to turn off a usb port so that I could power down the modem remotely, and then bring it back up. I think if I could do this, remotely, I may be able to save the use of these modems. Otherwise, I am going to be required to have someone unplug the modem and plug it back in to reset it in order to make it work. hylafax+ seems to be working fine, it just reports that the modem has become inaccessible. Any ideas? Thanks much, Greg Ennis

1 0

Postfix relay on Comcast
by Lists 24 Nov '13

24 Nov '13

How to get postfix working on CentOS 6 and Comcast. Recently, they've changed their policies regards email relay and require authentication even to send email. (they no longer use IP address ranges, presumably in an attempt to curb outgoing SPAM) I didn't see an updated howto anywhere on the Interwebs, thought I'd point out what I had to do. The part that had me stumped for longer than I care to admit was having to install cyrus-sasl-plain rpm - EL5 apparently had that installed as part of the cyrus-sasl package. 1) yum install postfix cyrus-sasl-plain; # note that cyrus-sasl-plain is NOT installed by default but is needed by this config. 2) Create file /etc/postfix/passwords. Replace "USERNAME" with your user name, and "password" with your password. Note: your username is typically your email address without the domain name. #---------------------------- smtp.comcast.net:587 USERNAME:password smtp.comcast.net USERNAME@comcast.net:password #---------------------------- 3) makemap passwords; 4) Edit /etc/postfix/main.cf #---------------------------- relayhost = [smtp.comcast.net]:587 smtpd_sasl_auth_enable = yes smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/passwords # note that with no security options on, we're using sasl-plain installed above. smtp_sasl_security_options = # You might need this, you may not. #sender_canonical_maps = regexp:/etc/postfix/sender_rewrite #---------------------------- 5) Create file /etc/postfix/sender_rewrite. Note that not all Comcast customers need this, I didn't when I authenticated as above. Obviously, replace "USERNAME" with your user name. #---------------------------- /^([^@]*)@.*$/ USERNAME(a)comcast.net #---------------------------- 6) service postfix stop; sleep 5; service postfix start

3 2

← Newer
1
2
3
4
5
6
7
8
...
18
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 November 2013