June 2008 - openSUSE Users - openSUSE Mailing Lists

[opensuse] VNC remote control in 10.3
by Ian 17 Jun '08

17 Jun '08

Hi, I'm looking for some help or advice getting VNC configured on 10.3 (running Gnome) in "remote control" mode - ie to make it connect to the physical X session rather than the more "normal" mode where you login to a separate vnc session. I can get VNC running in the "normal" mode using YAST, Remote Administration (VNC) and choosing "Allow Remote Administration", then running vncviewer <ipaddress>:5901 on the other machine or pointing a browser at <ipaddress>:5801. From what I've read, I thought the way to do this was to go to the Remote Access section in SAX and enable it, but it doesn't seem to do anything - if I enable it's Remote Access and disable Remote Admin in YAST, I can't connect at all. If I enable both,I get the same result as only enabling Remote Admin in YAST (ie connect to a new session on port 5901 or 5801 in a browser). So SAX doesn't appear to do anything! Is there a "preferred" way to do this in opensuse? Cheers, -- Ian gpg key: http://home.swiftdsl.com.au/~imoore/no-spam.asc

3 4

[opensuse] in KDE can you stop the [shift] key from affecting the numpad?
by David C. Rankin 17 Jun '08

17 Jun '08

Listmates, The new laptop I have comes with a full 104 key keyboard, including the separate numeric keypad. Somewhat awkwardly, the key 6-pack of: [INS] [HOME] [PGUP] [DEL] [END] [PGDN] is placed at the far top-right corner of the keyboard. With this layout the use of the numpad [home] [end] [pgup] [pgdn] is the most convenient. The difficulty with this comes when you need to select ranges of text with [shift]+ any of the keys on the keypad because of the alternate binding of 7, 1, 9 and 3 for those keys. Hitting the 'num lock' and then going back to the keypad to shift+select works, but it isn't workable from a hand-motion, efficiency standpoint. The burning question is "is there a way to modify the manner that the keypad responds to the shift key so that I can make range selection possible without turning numlock on? Some keyboard binding editor or something like it? The ultimate goal would be to prevent the keypad from recognizing that shift had been pressed unless numlock is turned on. Weird question, I know, but I have confident that Linux is flexible enough to do it, I just have to find out how and where to look. Thanks. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] wireless doesn't work in suse 11 RC1
by Joe Zien 17 Jun '08

17 Jun '08

I installed SuSE 11 RC1 and everything except wireless works. I have a ThinkPad T60 laptop with 11abg wireless card which works with my default distro mepis 7.01 and wireless works "right out of the box". This is what I tried: yast 2 -- Network services: No wireless shown Network Devices: No wireless shown Network Settings: AR5212 802.11 abg -- NIC not configured KnetworkManager shows: eth0 (ethernet) (no carrier) I don't have it connected ath0 shown on mepis, atheros wireless # iwconfig -- Listed below from mepis, a working wireless: "ath0 IEEE 802.11g ESSID:"linksys" Nickname:"default" Mode:Managed Frequency:2.437 GHz Access Point: 00:1A:70:6E:4C:4E Bit Rate:48 Mb/s Tx-Power:8 dBm Sensitivity=1/1 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=36/70 Signal level=-62 dBm Noise level=-98 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0" 1 - How do I config my NIC in yast 2 network settings? 2 - How do I add "ath0" using iwconfig? I am impressed with 11 RC1, it will be great if I can get wireless to work. jozien -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

14 34

[opensuse] missing log entries of imapd or master in openSUSE
by Uwe Galle 16 Jun '08

16 Jun '08

Hi, I get an error when I try to download the IMAP folders after the first connection to cyrus when an account in Outlook Express is created. The message is: "Bei der Verbindung zum Server ist ein Fehler aufgetreten" ("The connection to the server has failed"). Code: 800ccc0e The main point here is not the actual reason of this error, although advice is very appreciated. The main point is that I cannot see any record in the syslog-ng log for this error, although I can see records when I make a local login with imtest. Logins with imtest work without errors and problems and are logged by syslog-ng. The firewall was disabled during the test so there cannot be problems at that point. Wireshark shows me three request/response tcp packet pairs so that the request really reaches the server. Wireshark shows me that the connection is correctly established on port 143 of the server. netstat -antp shows me that master has opened that port so that master must have received the requests and must have send the responses. When looking for the reason for the missing log records I found the webpage http://wiki.rowi.net/pmwiki.php/Linux/Cyrus-imapd what states that the cyrus log should be configured. According to that page the option CYRUS_VERBOSE should be changed, apparently in the file cyrus21 in /etc/default. But in openSUSE 10.3 there is no cyrus file in /etc/default. According to man there is also no such option in cyrus.conf. My question is: Do I have to configure here something in openSUSE? The strange thing is that almost every program would log errors or warnings if it already logs successful operations. The successful login is logged as notice by syslog-ng, so any error or warning should have a higher priority and appear in the syslog. On the other hand other connections from the Outlook Express Client ARE logged. Outlook Express is configured to poll the server every 30 minutes. I created a directory in /var/lib/imap/log with the name of the user account of Outlook Express and see that every 30 minutes a log is written with the content ---------- galle Mon Jun 16 23:33:38 2008 >1213652018>+OK Mailbox locked and ready <1213652018<STAT >1213652018>+OK 0 0 <1213652018<QUIT >1213652018>+OK The configured polling seems to be OK. But when Outlook Express tries to download the folders of the IMAP account and ends up with an error nothing is logged. I am desperately looking for the reason of that. Note that I configured a second account in Outlook Express as POP3 account for testing purposes so that the same mailbox is polled by a POP3 account (this is obviously the 30 minutes polling) as well as by an IMAP4 account. I don't know of an option on cyrus that a mailbox has to be configured either as POP3 mailbox or IMAP4 mailbox. Even if there is a mistake here it should be logged. Note: I want at first to know why there are no log entries. But if you know that I have to configure a protocol for a cyrus mailbox, please tell me that. I think that a cyrus mailbox does not require a protocol setting. Regards, Uwe -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Rootkit Hunter for openssue 10.3
by Jim Flanagan 16 Jun '08

16 Jun '08

Does anyone know where I can get the newest version of rkhunter in an RPM for opensuse 10.3? I have an older version installed, and run it with the --update tag, but it still shows to be the older version. Thanks, Jim -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

8 14

[opensuse] 'openSUSE-10.3-Updates': SQL logic error or missing database
by Michael Mientus 16 Jun '08

16 Jun '08

FYI. I got the error below from YaST just a moment ago. I also got the same error when trying to install scite 1.76 from a 1-click installer except it was for scite's repo. There was an error in the repository initialization. 'openSUSE-10.3-Updates': SQL logic error or missing database Mike -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 2

RE: [opensuse] su password problem {solved}
by James D. Parra 16 Jun '08

16 Jun '08

... although I see that the permissions are > incorrect; >> >> -rwxr-xr-x 1 root root 23296 Jan 31 2006 /bin/su >> >> How do I change it back to; >> >> -rwsr-xr-x 1 root root 23296 Jan 31 2006 /bin/su >> > > Off the top of my head, I'd say: > > chmod 4755 /bin/su > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` > > That sorted out that little problem. > > Thank you, Till next time. Q: How did it get that way in the first place? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I want to limit the users who can use su when logging in via ssh. After changing the group ownership to group 'wheel' and adding the appropriate users to the wheel group, I noticed the rw permissions changed on /bin/su. Unfortunately, my tests show that even with certain users in the wheel group, anyone can su to root. (Please, I know all about who should and should not get the root password. In a small company exec's don't always follow best practices. This is my way to fix that.) I do want to restrict who can su to root. Using the 'wheel' group, how can this be accomplished? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The answer to my own question is to change the permissions as such; # chmod 4750 /bin/su #-rwsr-x--- 1 root wheel 33400 Sep 9 2005 /bin/su Thank you for your help and direction. Best, ~James -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

RE: [opensuse] su password problem {solved}
by James D. Parra 16 Jun '08

16 Jun '08

-----Original Message----- From: Sloan [mailto:joe@tmsusa.com] Sent: Monday, June 16, 2008 12:04 PM To: opensuse(a)opensuse.org Subject: Re: [opensuse] su password problem James D. Parra wrote: > On Mon, Jun 16, 2008 at 11:49 AM, James D. Parra > <Jamesp(a)musicreports.com> wrote: > >> Hello, >> >> Trying to use su from my account to get to root and I get the following >> error; >> >> me@example.server:/home> su >> Password: >> Permissions on the password database may be too restrictive. >> su: incorrect password >> <snip> >> >> I can log in directly as root with the password, but I cannot su to it. >> > Any > >> ideas how to correct this? >> >> Thank you, >> >> James >> > > Your Clue: > > Permissions on the password database may be too restrictive. > > Log in as root and set security options to SECURE, not Paranoid. > Yase Security Local. > ~~~~~~~~~~ > > Hello, > > Its not set to Paranoid, although I see that the permissions are incorrect; > > -rwxr-xr-x 1 root root 23296 Jan 31 2006 /bin/su > > How do I change it back to; > > -rwsr-xr-x 1 root root 23296 Jan 31 2006 /bin/su > Off the top of my head, I'd say: chmod 4755 /bin/su ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~` That sorted out that little problem. Thank you, ~James -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Multiserielle Karten
by Detlev Runge 16 Jun '08

16 Jun '08

Hallo Leute, hat schon jemand Erfahrung mit einer AXXON MP8-PCI Karte ? bzw, wie stellt man die seriellen Ports ein. -- Detlev Runge Email: detlev.runge(a)necnet.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

RE: [opensuse] su password problem
by James D. Parra 16 Jun '08

16 Jun '08

On Mon, Jun 16, 2008 at 11:49 AM, James D. Parra <Jamesp(a)musicreports.com> wrote: > Hello, > > Trying to use su from my account to get to root and I get the following > error; > > me@example.server:/home> su > Password: > Permissions on the password database may be too restrictive. > su: incorrect password > <snip> > > I can log in directly as root with the password, but I cannot su to it. Any > ideas how to correct this? > > Thank you, > > James Your Clue: Permissions on the password database may be too restrictive. Log in as root and set security options to SECURE, not Paranoid. Yase Security Local. ~~~~~~~~~~ Hello, Its not set to Paranoid, although I see that the permissions are incorrect; -rwxr-xr-x 1 root root 23296 Jan 31 2006 /bin/su How do I change it back to; -rwsr-xr-x 1 root root 23296 Jan 31 2006 /bin/su Thank you, James -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1