> preferred publickey,keyboard-interactive,password
It also appears that the bad password is actually what's getting you in, which is really strange. I'm out of ideas at the moment.
Neil- any guesses?
Jeremy
At 11:15 AM 2/20/2004, Benjamin Simmons wrote:
open to any thoughts on how to proceed.
I thought of something and tried it myself. I have another server setup in another part of campus that is running OSCAR 3 and RH9. I copied the sshd_config file from this machine before I performed the things below.
Ben
Ok, i started /usr/sbin/sshd -d and here is the output [EMAIL PROTECTED] sbin]# ./sshd -d debug1: sshd version OpenSSH_3.5p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #2 type 2 DSA socket: Address family not supported by protocol debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. Generating 768 bit RSA key. RSA key generation complete.
I then opened another window and logged in as a user and here is the output. ( i entered a bad password to get it in)
Last login: Fri Feb 20 08:20:50 2004 from 141.225.161.39
debug1: PAM establishing creds
debug1: permanently_set_uid: 0/0
Environment:
USER=root
LOGNAME=root
HOME=/root
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
MAIL=/var/mail/root
SHELL=/bin/bash
SSH_CLIENT=141.225.161.39 1383 22
SSH_CONNECTION=141.225.161.39 1383 141.225.164.31 22
SSH_TTY=/dev/pts/2
TERM=vt100
SSH_AUTH_SOCK=/tmp/ssh-XXXmAViD/agent.6482
[EMAIL PROTECTED] root]# su - bdsimmns
[EMAIL PROTECTED] bdsimmns]$ ssh -vvv engrcluster
OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to engrcluster [10.0.0.250] port 22.
debug1: Connection established.
debug1: identity file /home/bdsimmns/.ssh/identity type 0
debug3: Not a RSA1 key file /home/bdsimmns/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found
debug1: identity file /home/bdsimmns/.ssh/id_rsa type 1
debug3: Not a RSA1 key file /home/bdsimmns/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: no key found
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug3: key_read: no space
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: no key found
debug1: identity file /home/bdsimmns/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.1p1
debug1: match: OpenSSH_3.1p1 pat OpenSSH_2.*,OpenSSH_3.0*,OpenSSH_3.1*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED]
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,[EMAIL PROTECTED]
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 127/256
debug1: bits set: 1632/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /home/bdsimmns/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug3: check_host_in_hostfile: filename /home/bdsimmns/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug1: Host 'engrcluster' is known and matches the RSA host key.
debug1: Found key in /home/bdsimmns/.ssh/known_hosts:1
debug1: bits set: 1596/3191
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug3: start over, passed a different list publickey,password,keyboard-interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: next auth method to try is publickey
debug1: try pubkey: /home/bdsimmns/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: try pubkey: /home/bdsimmns/.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: next auth method to try is keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug3: userauth_kbdint: disable: no info_req_seen
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred:
debug3: authmethod_is_enabled password
debug1: next auth method to try is password
[EMAIL PROTECTED]'s password:
debug3: packet_send2: adding 64 (len 54 padlen 10 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: ssh-userauth2 successful: method password
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug1: send channel open 0
debug1: Entering interactive session.
debug2: callback start
debug1: ssh_session2_setup: id 0
debug1: channel request 0: pty-req
debug3: tty_make_modes: ospeed 38400
debug3: tty_make_modes: ispeed 38400
debug3: tty_make_modes: 1 3
debug3: tty_make_modes: 2 28
debug3: tty_make_modes: 3 8
debug3: tty_make_modes: 4 21
debug3: tty_make_modes: 5 4
debug3: tty_make_modes: 6 0
debug3: tty_make_modes: 7 0
debug3: tty_make_modes: 8 17
debug3: tty_make_modes: 9 19
debug3: tty_make_modes: 10 26
debug3: tty_make_modes: 12 18
debug3: tty_make_modes: 13 23
debug3: tty_make_modes: 14 22
debug3: tty_make_modes: 18 15
debug3: tty_make_modes: 30 0
debug3: tty_make_modes: 31 0
debug3: tty_make_modes: 32 0
debug3: tty_make_modes: 33 0
debug3: tty_make_modes: 34 0
debug3: tty_make_modes: 35 0
debug3: tty_make_modes: 36 1
debug3: tty_make_modes: 37 0
debug3: tty_make_modes: 38 1
debug3: tty_make_modes: 39 0
debug3: tty_make_modes: 40 0
debug3: tty_make_modes: 41 0
debug3: tty_make_modes: 50 1
debug3: tty_make_modes: 51 1
debug3: tty_make_modes: 52 0
debug3: tty_make_modes: 53 1
debug3: tty_make_modes: 54 1
debug3: tty_make_modes: 55 1
debug3: tty_make_modes: 56 0
debug3: tty_make_modes: 57 0
debug3: tty_make_modes: 58 0
debug3: tty_make_modes: 59 1
debug3: tty_make_modes: 60 1
debug3: tty_make_modes: 61 1
debug3: tty_make_modes: 62 0
debug3: tty_make_modes: 70 1
debug3: tty_make_modes: 71 0
debug3: tty_make_modes: 72 1
debug3: tty_make_modes: 73 0
debug3: tty_make_modes: 74 0
debug3: tty_make_modes: 75 0
debug3: tty_make_modes: 90 1
debug3: tty_make_modes: 91 1
debug3: tty_make_modes: 92 0
debug3: tty_make_modes: 93 0
debug1: channel request 0: shell
debug1: fd 3 setting TCP_NODELAY
debug2: callback done
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
Last login: Fri Feb 20 10:56:23 2004 from viper.engr.memphis.edu
Jeremy Enos wrote:
At 10:21 AM 2/20/2004, Benjamin Simmons wrote:
Ok. I was able to try it this morning, and it still does not work, but it will take anything for a password still. Do i need to turn off password authentication on both sides of this?
Either side alone should do. If that's not working, perhaps the "ordering problem" conclusion is not accurate. We might want to try running the sshd in debug mode (-d on the cmd line). Maybe that will tell us more. I don't know any ssh support areas better than the man pages or google. And either one of those is vulnerable to having information not pertinent to a particular ssh build or version.
Jeremy
I am not sure what you mean by the last set of ideas you sent me,
can you give me a pointer to a place to read about this other than the man pages,
Thanks,
Ben
Jeremy Enos wrote:
I don't know what your needs are, but you can also specify
PasswordAuthentication no
on the client side instead of the server. You can do this in a user's local config file or the system's global ssh_config. You can also specify a host list or mask that a particular setting applies to within the a config file too. This solution is a hack at best, but maybe it will help you get unstuck for the moment.
Jeremy
At 05:57 PM 2/19/2004, Benjamin Simmons wrote:
Ok, I think I found a problem neither one of us saw coming from setting that to a no. When I use my remote ssh connection tool on my windows environment to try to connect, I cannot get authenticated anymore. So, I might be able to login if I was physically in the room, but I can't be until around 8am CST tomorrow. I will test it then and let you know what has happened at that point.
Any other thoughts on a way to re-order the authentication methods ?
Thanks, Ben
Jeremy Enos wrote:
That's a good data point. Don't be troubled- that means it's working! It's just got the auth methods out of order for some reason; I'm not quite sure why. Password attempt fails, and it continues on to the next auth method, which is likely pub key which will work.
So the only mystery now is why is it in the wrong order, and how to change it. The only thing that comes to mind quickly is setting:
PasswordAuthentication no
in the sshd_config on the target hosts. However, this can really be a pain in the event that root's keys ever get messed up. But if you trust that won't happen, give it a try. The worst case scenario is that it will require console access to reverse it.
Jeremy
At 04:41 PM 2/19/2004, Benjamin Simmons wrote:
I am troubled by the fact that when it prompts a user for a password, I can type anything and it is a successful authentication. Does this help in any way?
I have made the update from a file off a node. Here are the relevant files you had asked for.
Ben
RH 9 machine (from machine)
[EMAIL PROTECTED] ssh]# tail /var/log/messages
Feb 19 15:47:58 viper sshd(pam_unix)[5432]: session opened for user apwinter by (uid=502)
Feb 19 15:48:47 viper sshd(pam_unix)[5486]: session opened for user apwinter by (uid=502)
Feb 19 15:49:23 viper sshd(pam_unix)[5486]: session closed for user apwinter
Feb 19 15:49:25 viper sshd(pam_unix)[5432]: session closed for user apwinter
Feb 19 16:05:33 viper su(pam_unix)[5565]: session opened for user bdsimmns by root(uid=0)
Feb 19 16:06:02 viper su(pam_unix)[5565]: session closed for user bdsimmns
Feb 19 16:17:57 viper sshd(pam_unix)[5645]: session opened for user root by (uid=0)
Feb 19 16:21:43 viper su(pam_unix)[5707]: session opened for user bdsimmns by root(uid=0)
Feb 19 16:23:33 viper su(pam_unix)[5707]: session closed for user bdsimmns
RH 7.3 machine (to machine) ( I supplied a bad password and got in)
[EMAIL PROTECTED] root]# tail /var/log/messages
Feb 19 16:27:24 goddard31 kernel: EXT2-fs error (device ide0(3,6)): ext2_write_inode: unable to read inode block - inode=32396, block=65540
Feb 19 16:27:56 goddard31 kernel: end_request: I/O error, dev 03:06 (hda), sector 0
Feb 19 16:27:56 goddard31 kernel: end_request: I/O error, dev 03:06 (hda), sector 8
Feb 19 16:27:56 goddard31 kernel: end_request: I/O error, dev 03:06 (hda), sector 524296
Feb 19 16:34:57 engrcluster rpc.mountd: authenticated unmount request from viper.engr.memphis.edu:633 for /root (/root)
Feb 19 16:34:57 engrcluster rpc.mountd: authenticated unmount request from viper.engr.memphis.edu:635 for /home (/home)
Feb 19 16:37:02 engrcluster rpc.mountd: authenticated mount request from viper.engr.memphis.edu:904 for /home (/home)
Feb 19 16:37:02 engrcluster rpc.mountd: authenticated mount request from viper.engr.memphis.edu:908 for /root (/root)
Feb 19 16:38:24 engrcluster sshd(pam_unix)[19884]: session opened for user root by (uid=0)
Feb 19 16:38:54 engrcluster sshd(pam_unix)[19966]: session opened for user bdsimmns by (uid=0)
[EMAIL PROTECTED] root]#
File from server(now replaced by a file from a node)
# $OpenBSD: sshd_config,v 1.59 2002/09/25 11:17:16 markus Exp $
# This is the sshd server system-wide configuration file. See # sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin
# The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value.
#Port 22 #Protocol 2,1 #ListenAddress 0.0.0.0 #ListenAddress ::
# HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key
# Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 3600 #ServerKeyBits 768
# Logging #obsoletes QuietMode and FascistLogging #SyslogFacility AUTH SyslogFacility AUTHPRIV #LogLevel INFO
# Authentication:
#LoginGraceTime 120 #PermitRootLogin yes #StrictModes yes
RSAAuthentication yes PubkeyAuthentication yes #AuthorizedKeysFile .ssh/authorized_keys
# rhosts authentication should not be used
#RhostsAuthentication no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
RhostsRSAAuthentication yes
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts noi
#RSAAAuthentication yes
# To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no
# Change to no to disable s/key passwords #ChallengeResponseAuthentication yes
# Kerberos options #KerberosAuthentication no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes
#AFSTokenPassing no
# Kerberos TGT Passing only works with the AFS kaserver #KerberosTgtPassing no
# Set this to 'yes' to enable PAM keyboard-interactive authentication
# Warning: enabling this may bypass the setting of 'PasswordAuthentication'
#PAMAuthenticationViaKbdInt no
#X11Forwarding no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PrintMotd yes #PrintLastLog yes #KeepAlive yes #UseLogin no #UsePrivilegeSeparation yes #PermitUserEnvironment no #Compression yes
#MaxStartups 10 # no default banner path #Banner /some/path #VerifyReverseMapping no
# override default of no subsystems Subsystem sftp /usr/libexec/openssh/sftp-server
File from a node [EMAIL PROTECTED] ssh]# vi sshd_config
# $OpenBSD: sshd_config,v 1.48 2002/02/19 02:50:59 deraadt Exp $
# This is the sshd server system-wide configuration file. See sshd(8) # for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with # OpenSSH is to specify options with their default value where # possible, but leave them commented. Uncommented options change a # default value.
#Port 22 #Protocol 2,1 #ListenAddress 0.0.0.0 #ListenAddress ::
# HostKey for protocol version 1 #HostKey /etc/ssh/ssh_host_key # HostKeys for protocol version 2 #HostKey /etc/ssh/ssh_host_rsa_key #HostKey /etc/ssh/ssh_host_dsa_key
# Lifetime and size of ephemeral version 1 server key #KeyRegenerationInterval 3600 #ServerKeyBits 768
# Logging #obsoletes QuietMode and FascistLogging #SyslogFacility AUTH SyslogFacility AUTHPRIV #LogLevel INFO
# Authentication:
#LoginGraceTime 600 #PermitRootLogin yes #StrictModes yes
#RSAAuthentication yes #PubkeyAuthentication yes #AuthorizedKeysFile .ssh/authorized_keys
# rhosts authentication should not be used
#RhostsAuthentication no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no
# Change to no to disable s/key passwords #ChallengeResponseAuthentication yes
# Kerberos options # KerberosAuthentication automatically enabled if keyfile exists #KerberosAuthentication yes #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes
# AFSTokenPassing automatically enabled if k_hasafs() is true #AFSTokenPassing yes
# Kerberos TGT Passing only works with the AFS kaserver #KerberosTgtPassing no
# Set this to 'yes' to enable PAM keyboard-interactive authentication
# Warning: enabling this may bypass the setting of 'PasswordAuthentication'
#PAMAuthenticationViaKbdInt yes
#X11Forwarding no X11Forwarding yes #X11DisplayOffset 10 #X11UseLocalhost yes #PrintMotd yes #PrintLastLog yes #KeepAlive yes #UseLogin no
#MaxStartups 10 # no default banner path #Banner /some/path #VerifyReverseMapping no
# override default of no subsystems Subsystem sftp /usr/libexec/openssh/sftp-server IgnoreRhosts yes RhostsRSAAuthentication yes RSAAuthentication yes RhostsAuthentication no
Jeremy Enos wrote:
Could you send your sshd file as well? You may want to try backing it up and copying the config from a compute node too...
also watch /var/log/messages on the target host during the attempt/failure.
(tail -f /var/log/messages)
Jeremy
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
