Eric is correct. For completeness, please print out the line starting
with your username in /etc/passwd to us.
Kinson
Eric Hyche wrote:
EHYCHED620"
type="cite">
Well, as you can see:
debug1: Next authentication method: publickey
debug1: Trying private key: /cygdrive/c/source/.ssh/identity
debug1: Trying private key: /cygdrive/c/source/.ssh/id_rsa
debug1: Trying private key: /cygdrive/c/source/.ssh/id_dsa
It never tried your generated key (helixid_dsa). Have you
verified that it is in c:source.ssh?
Also, what is your HOME environment variable set to? Usually
ssh.exe will try to look for keys in $HOME/.ssh.
Eric
=============================================
Eric Hyche (real.com">ehyche real.com)
Technical Lead
RealNetworks, Inc.
-----Original Message-----
From: aricent.com">Jinu.Thomasaricent.com [aricent.com">mailto:Jinu.Thomasaricent.com]
Sent: Friday, March 23, 2007 9:34 AM
To: real.com">ehychereal.com
Cc: helixcommunity.org">helix-client-devhelixcommunity.org
Subject: RE: [Helix-client-dev] Authentication failure
The key pair generated are helixid_dsa.pub(public key) and
helixid_dsa(private key). I have updated the keys field in my
account with the public key generated. I have tried even
after 3-4 hours after the key updating. But still the problem
persists. What could be the reason? My helix account is
helixcommunity.org">jinuthomashelixcommunity.org.
Regards,
Jinu
"Eric Hyche" real.com"><ehychereal.com>
Sent by: helixcommunity.org">helix-client-dev-bounceshelixcommunity.org
03/23/2007 06:30 PM
Please respond to
real.com">ehychereal.com
To
Jinu Thomas/BLR/HSSHSS, helixcommunity.org">helix-client-devhelixcommunity.org
cc
Subject
RE: [Helix-client-dev] Authentication failure
debug1: Next authentication method: publickey
debug1: Trying private key: /cygdrive/c/source/.ssh/identity
debug1: Trying private key: /cygdrive/c/source/.ssh/id_rsa
debug1: Trying private key: /cygdrive/c/source/.ssh/id_dsa
Which one of these is the correct one?
Usually when we see this, it's one of the following problems:
1) Public key has been properly loaded into helix account,
but it just hasn't been long enough (sometimes up to 4 hours)
until it's active.
2) Public key has been copied incorrectly into the helix
account. Sometimes people copy the *private* key into it,
sometimes they copy the wrong format key (like they copy
a PGP key or something like that).
Do any of these apply?
Eric
=============================================
Eric Hyche (real.com">ehychereal.com)
Technical Lead
RealNetworks, Inc.
-----Original Message-----
From: helixcommunity.org">helix-client-dev-bounceshelixcommunity.org
[helixcommunity.org">mailto:helix-client-dev-bounceshelixcommunity.org] On
Behalf Of aricent.com">Jinu.Thomasaricent.com
Sent: Friday, March 23, 2007 5:04 AM
To: helixcommunity.org">helix-client-devhelixcommunity.org
Subject: [Helix-client-dev] Authentication failure
Hi all,
I have followed the qiuck start guide to setup
the build system. But ssh is not working properly. It is
prompting for the password. I tried the installation process
many times but getting the same result always. If anybody
know the problem , please advise.
bash-2.05b$ ssh -v -v -l jinuthomas 207.188.25.137 port 22
OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004
debug1: Reading configuration data /cygdrive/c/source/.ssh/config
debug2: ssh_connect: needpriv 0
debug1: Connecting to 207.188.25.137 [207.188.25.137] port 22.
debug1: Connection established.
debug1: identity file /cygdrive/c/source/.ssh/identity type -1
debug1: identity file /cygdrive/c/source/.ssh/id_rsa type -1
debug1: identity file /cygdrive/c/source/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-gro
up14-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,lysator.liu.se,aes128-ctr,a">rijndael-cbclysator.liu.se,aes128-ctr,a
es192-ctr,aes256-c
tr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
aes192-cbc,aes256-cbc,lysator.liu.se,aes128-ctr,a">rijndael-cbclysator.liu.se,aes128-ctr,a
es192-ctr,aes256-c
tr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160open
ssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160open
ssh.com,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-gro
up14-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,lysator.liu.se,aes128-ctr,a">rijndael-cbclysator.liu.se,aes128-ctr,a
es192-ctr,aes256-c
tr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
aes192-cbc,aes256-cbc,lysator.liu.se,aes128-ctr,a">rijndael-cbclysator.liu.se,aes128-ctr,a
es192-ctr,aes256-c
tr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160open
ssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160open
ssh.com,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(1024<1024<;8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 121/256
debug2: bits set: 527/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '207.188.25.137' is known and matches the RSA
host key.
debug1: Found key in /cygdrive/c/source/.ssh/known_hosts:1
debug2: bits set: 556/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /cygdrive/c/source/.ssh/identity (0x0)
debug2: key: /cygdrive/c/source/.ssh/id_rsa (0x0)
debug2: key: /cygdrive/c/source/.ssh/id_dsa (0x0)
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Trying private key: /cygdrive/c/source/.ssh/identity
debug1: Trying private key: /cygdrive/c/source/.ssh/id_rsa
debug1: Trying private key: /cygdrive/c/source/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
207.188.25.137">jinuthomas207.188.25.137's password:
Rishi Mathew real.com"><rmathewreal.com>
03/23/2007 12:12 AM
To
Jinu Thomas/BLR/HSSHSS
cc
Sunil Bhide/BLR/HSSHSS, Scott Nelson real.com"><snelsonreal.com>
Subject
Re: Access license for Emuzed
This is because your ssh key is not correctly set up. Follow
steps 7-15 of the Quickstart guide again.
https://helixcommunity.org/developers/get_connected_to_cvs/qui
ckstart
<https://helixcommunity.org/developers/get_connected_to_cvs/qu
ickstart>
Please use the helix-client-dev mailing list for follow up
questions from now on.
Thanks,
Rishi.
At 06:53 AM 3/22/2007, aricent.com">Jinu.Thomasaricent.com wrote:
Hi Rishi,
Thank you very much. But I am unable to proceed with
the code building process since it keep on asking password
when I run the build.py file.
bash-2.05b$ python "../build/bin/build.py"
[#-00000001][2007-03-22 18:49:18][3356][INFO ] : Ribosome v2.4.5
[#-00000002][2007-03-22 18:49:18][3356][INFO ] : Using
Python v2.4.3
[#-00000003][2007-03-22 18:49:18][3356][INFO ] : Log dir:
c:sourcehelixriboso
me_logs
[#-00000005][2007-03-22 18:49:18][3356][INFO ] : Running
tool: build
[#-00000028][2007-03-22 18:49:19][3356][INFO ] : Submitting
all jobs to chaingan
g.
[#-00000029][2007-03-22 18:49:19][3356][INFO ] : Enabling
threading, 3 threads r
equested.
[#-00000031][2007-03-22 18:49:19][3356][INFO ] : Starting
thread scheduler to pr
ocess jobs.
cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org's password:
cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org'
s password: cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org's password:
cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org's password:
cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org's password:
cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org's password:
cvs.helixcommunity.org">jinuthomascvs.helixcommunity.org's password:
The .buildrc file I am using is attached . Please advise.
Thanks & Regards,
Jinu
Rishi Mathew real.com"><rmathewreal.com>
03/22/2007 04:49 AM
To
Jinu Thomas/BLR/HSSHSS
cc
Scott Nelson real.com"><snelsonreal.com>, Sunil Bhide/BLR/HSSHSS
Subject
Re: Access license for Emuzed
Done. Please continue to use your emuzed email address while
sending your CR emails to the community mailing lists.
Thanks,
Rishi.
At 05:30 AM 3/21/2007, aricent.com">Jinu.Thomasaricent.com wrote:
Hi Rishi,
The email address on my helix community
account ( helixcommunity.org">jinuthomashelixcommunity.org ) has been changed to
my emuzed email address( emuzed.com">jinuemuzed.com). Please provide me
the read and write access to all public and restricted projects.
Thanks& Regards,
Jinu
Rishi Mathew real.com"><rmathewreal.com>
03/10/2007 02:39 AM
To
Jinu Thomas/BLR/HSSHSS
cc
Sunil Bhide/BLR/HSSHSS, Scott Nelson real.com"><snelsonreal.com>
Subject
Re: Access license for Emuzed
Yes, other Emuzed employees have write access. Here are the
steps that I recommend to you Jinu:
1. Change your email address on the Helix Community account
to your emuzed email address. Let us know after you have done that.
2. We will provide read and write access for your username to
all public and restricted projects.
3. Resend your CR to the datatype-dev and realformat-sdk-dev
mailing list as mentioned in the Patch Submission process.
Use your emuzed.com email address at all times.
4. You can NOT have your "Disclaimer" in the email footer.
5. You ALSO need to use the following CR header (this is from
the code-review form (
https://common.helixcommunity.org/2005/patch/change-form
<https://common.helixcommunity.org/2005/patch/change-form> ):
In
consideration for RealNetworks' hosting and maintenance
of my
modification, I agree to assign to RealNetworks full
copyright
ownership of the code included in the attached
patch, and
agree that RealNetworks has no duty of accounting
to me for
it. I warrant that this code is entirely original
to and owned
by me, that I can legally grant the copyright
assignment,
and that my contribution does not violate any other
person's
rights, and laws or breach any contract. I understand
that
RealNetworks may license this code under RPSL, RCSL,
and/or any
other license at RealNetworks' discretion, and use
the code in
any way.
6. Once the code review is approved in the public/restricted
mailing list, you can commit the changes to CVS.
Thanks,
Rishi.
At 10:37 PM 3/8/2007, aricent.com">Jinu.Thomasaricent.com wrote:
Hi Rishi,
Please confirm the same.
Thanks&Regards,
jinu
Scott Nelson real.com"><snelsonreal.com>
03/08/2007 04:20 AM
To
Sunil Bhide/BLR/HSSHSS
cc
Rishi Mathew real.com"><rmathewreal.com>, real.com">snelsonreal.com, Jinu
Thomas/BLR/HSSHSS
Subject
Re: Access license for Emuzed
Sunil,
Rishi will have to send you the answer about the write
access. Here is my understanding as of now.
* Emuzed is licensed for our codec source code
* Aricent does not have access to our codec
source code
* Emuzed still exists as a legal company
separate from Aricent
* All the people that you want to have read
or write
access to our codec source code under the Emuzed codec source
license are current employees of Emuzed, are aware of and
bound by that license, and will use only their emuzed.com
email addresses to communicate with us.
Please send back your agreement.
Thank you
Scott Nelson
Real
At 02:21 AM 3/7/2007, aricent.com">Sunil.Bhidearicent.com wrote:
Dear Rishi,
I understand Emuzed had WRITE access ?
Scott, pl. correct me if that is not the case.
regards,
Sunil
Rishi Mathew real.com"><rmathewreal.com>
03/07/2007 10:40 AM
To
Sunil Bhide/BLR/HSSHSS, real.com">snelsonreal.com
cc
Jinu Thomas/BLR/HSSHSS, "Scott Nelson" real.com"><snelsonreal.com>
Subject
Re: Access license for Emuzed
Here is the list of things that need to be addressed, sent in
a previous email. I believe we have covered point (1). Scott-
Please send an email to admin asking for Jinu to be given
read access.
Thanks,
Rishi
Here are a number of points that we need to solve before you
can check in ANY code:
1. You need to have READ access to the restricted part of our
code-base. This is the reason you were having those checkout
errors that you mentioned earlier. This will also allow you
to take cvs diffs of all the files. To get READ access,
either Flextronics' license agreement with us needs to be
assigned to Aricent, or, Aricent needs to sign a new license.
2. You need WRITE access to our codebase (both restricted and
non-restricted) to be able to checkin any changes that have
been reviewed. Aricent needs to agree to a 1-page PDF, so
that copyright is appropriately handed over to us.
https://helixcommunity.org/2002/intro/contributor-agreement.pd
f
<https://helixcommunity.org/2002/intro/contributor-agreement.pdf>
3. All Code-reviews need to happen in the community mailing
lists, not in private emails.
4. You need to remove following text from the footer of the email:
*********************** Aricent- Confidential
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is
intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
5. The header in the CR email is invalid because there is no
current commercial agreement between us.
"Aricent submits this code under the terms of a commercial
contribution
agreement with Real Networks, and I am authorized to
contribute this
code under said agreement."
You actually need to have the following header:
I have signed and delivered a Joint Copyright Assignment
to
RealNetworks, and received acknowledgment that the
agreement
was received.
At 08:49 PM 3/6/2007, aricent.com">Sunil.Bhidearicent.com wrote:
Hi Scott,
Now that this is clarified, I feel we need to focus on
sorting out the compilation problems that we are facing.
I assume Rishi can help us with this ?
regards,
Sunil
real.com">snelsonreal.com
03/06/2007 10:15 PM
To
Sunil Bhide/BLR/HSSHSS
cc
"Scott Nelson" real.com"><snelsonreal.com>, "Rishi Mathew"
real.com"><rmathewreal.com>, Jinu Thomas/BLR/HSSHSS
Subject
Re: Access license for Emuzed
Hi Sunil,
Please tell folks with access to the codec source that work
for Emuzed to
use their "emuzed.com" email accounts for all communications
with Helix
Community and Real and all should be OK. It is the fact that
you have a
aricent.com email address that is the problem. We assume you
work for that
legal entity.
Thank you,
Scott Nelson
Dir Lic
Real
Dear Scott,
As Rishi mentions, Emuzed has valid licenses for this access.
Note that Emuzed is a separate legal entity and we are
employees of the
same.
Therefore, I suppose the license should still be usable.
Please advise if anything on the contrary.
Regards,
Sunil Bhide
Engineering Project Manager
Emuzed India Pvt. Ltd.,
9th Floor, Sigma Softech Park, Whitefield Main Road,
Varthur Post, Bangalore- 560 066, India
Office: +91.80.41069000 Extn: 9701
: +91.80.41069701 (Direct)
----- Forwarded by Jinu Thomas/BLR/HSS on 03/02/2007
11:18 AM -----
Scott Nelson real.com"><snelsonreal.com>
03/01/2007 02:29 PM
To
Jinu Thomas/BLR/HSSHSS
cc
"Rishi Mathew" real.com"><rmathewreal.com>, Scott Nelson real.com"><snelsonreal.com>
Subject
Re: Fw: CR: MDF Wrapper for the RV89 Combo Decoder
Jinu,
We license companies to use our technology. Flextronix has
a license,
Aricent does not. No employee of Aricent should have access
to the source
code or check things in right now because you do not have a
license via
your employer to do so. A Flextronix employee could do a
check in if they
have been granted access to the restricted project.
Please get me in touch with the legal person at Aricent
that can process
the new license (attached) or the person at Flextronix that
can request an
assignment of their license to Aricent and the problem is solved.
Scott Nelson
Dir Tech Lic
Real
At 11:02 PM 2/27/2007, Orient.com">Jinu.ThomasOrient.com wrote:
Hi Rishi,
Does helixcommunity.org">ramukchelixcommunity.org or
helixcommunity.org">pcnbosehelixcommunity.org has got the access to restricted code ?
Actually helixcommunity.org">pcnbosehelixcommunity.org has done the check-in
earlier. If any
of them has the access , then they can help us doing tjhe
checking-in.
Please clariffy.
Thanks&Regards,
Jinu
Scott Nelson real.com"><snelsonreal.com>
02/27/2007 11:08 PM
To
Jinu Thomas/BLR/HSSHSS
cc
Scott Nelson real.com"><snelsonreal.com>, "Rishi Mathew" real.com"><rmathewreal.com>
Subject
Re: Fw: CR: MDF Wrapper for the RV89 Combo Decoder
No
Scott
At 11:14 PM 2/26/2007, aricent.com">Jinu.Thomasaricent.com wrote:
Hi Scott,
Thanks for the information. I have
escalated the same to
the higher management. We will get back to you early next week.
I need a quick clarification. Will I be able to check-in
the code now if
the CR is agreed by Nokia?
Thanks & Regards,
Jinu
Scott Nelson real.com"><snelsonreal.com>
02/27/2007 06:43 AM
To
Jinu Thomas/BLR/HSSHSS
cc
Scott Nelson real.com"><snelsonreal.com>, "Rishi Mathew" real.com"><rmathewreal.com>
Subject
Re: Fw: CR: MDF Wrapper for the RV89 Combo Decoder
Hi Jinu,
None of the Real Format source code licenses that Emuzed of
Flextronics
have with us have been assigned and they are going to
expire in 6 months.
We can agree to assign the old one if you send us a written
request in the
form of a letter to sign, or you can submit new ones which
are good for 2
years and downloadable here: Real Format Source Code Porting and
Optimization License
If anyone has any questions please contact me.
Scott Nelson
Dir Tech Lic
Real
At 04:34 PM 2/26/2007, Rishi Mathew wrote:
Jinu,
This should be reviewed by one of the Nokia folks. I have
sent them a note
asking them to reply to your mail.
As for the error, the reason it is happening is because you
do not have
acesss to restricted code. Emuzed had a license with us and so did
Flextronics, but I am not sure if it got assigned to Aricent.
I have cc'ed Scott Nelson who is our business dev contact.
He can help you
further on this if you put your bus dev person in touch with him.
Thanks,
Rishi.
At 03:16 AM 2/23/2007, aricent.com">Jinu.Thomasaricent.com wrote:
Hi Rishi,
Thank you very much for your help. Kindly go
through the CR
request I have already sent. Is it proper? Nobody has
responded until now.
What shall I do now? I could not take the diff file since I
was getting
some error while using the command cvs diff -uw on the folder
datatype-restricted . The error is
/CVSROOTccess /cvsroot/rarvcode-video
No such file or directory
Please give me ur feedback.
Regards,
Jinu
----- Forwarded by Jinu Thomas/BLR/HSS on 02/23/2007
04:42 PM -----
Jinu Thomas/BLR/HSS
02/22/2007 08:49 PM
Aricent- Confidential
To
helixcommunity.org">datatype-devhelixcommunity.org
cc
Subject
CR: MDF Wrapper for the RV89 Combo Decoder
"Aricent submits this code under the terms of a commercial
contribution
agreement with Real Networks, and I am authorized to
contribute this
code under said agreement."
Modified by:
Aricent.com">Jinu.ThomasAricent.com
Date:
February-22-2007
Project:
RV89 MDF Wrapper for Symbian
Synopsis:
This is to build the modules independently and to fix
the multiple
definition compilation error.
Overview:
The cdecarm file modification is to define
independent macros
for building the code in different platforms. Both the BIF file
modifications are to build the modules independently.
Files Modified:
buildbif-cvshelixclient-restrictedbuildBIFhxclient_2_1_0
_cayennes_restricted.bif
buildbif-cvshelixrealformat-sdkbuildBIFrealformat-sdk.bif
helixdatatype-restrictedrmvideocodecrv89comboplatformem
uzedcdecarm
Files Added:
None
Image Size and Heap Use impact:
Minimal
Platforms and Profiles Build Verified:
BIF branch -> realformat-sdk as well as
hxclient_2_1_0_cayennes_restricted
Target(s) ->src/common as well as
datatype-restricted_rm_video_codec_rv89combo_emuzed
Profile -> helix-client-s60-32-mmf-mdf-arm
SYSTEM_ID= symbian-91-armv5
Platforms and Profiles Functionality verified:
armv5
Branch: HEAD
Files Attached:
cdecarm
hxclient_2_1_0_cayennes_restricted.bif
realformat-sdk.bif
*********************** Aricent- Confidential
***********************
*********************** Aricent-Private ***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain
privileged or
confidential information and should not be
circulated or used for any purpose other than for what it
is intended.
If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Rishi Mathew
Sr. Software Development Engineer
Helix Community
Real Networks, Inc.
real.com">rmathewreal.com
http://www.helixcommunity.org <http://www.helixcommunity.org/>
http://www.realnetworks.com/products/support/devsupport.html
<http://www.realnetworks.com/products/support/devsupport.html>
Scott Nelson
Dir. Bus. Dev. IP Licensing
Real
www.helixcommunity.org <http://www.helixcommunity.org/>
Office 925 838-5536 Mobile 925 890-5306
"The overall best codec was RealNetworks RealVideo."
StreamingMedia.com article by Jan Ozer 3/22/06
*********************** Aricent- Confidential
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain
privileged or
confidential information and should not be
circulated or used for any purpose other than for what it
is intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Scott Nelson
Dir. Bus. Dev. IP Licensing
Real
www.helixcommunity.org <http://www.helixcommunity.org/>
Office 925 838-5536 Mobile 925 890-5306
"The overall best codec was RealNetworks RealVideo."
StreamingMedia.com article by Jan Ozer 3/22/06
*********************** Aricent- Confidential
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain
privileged or
confidential information and should not be
circulated or used for any purpose other than for what it
is intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Scott Nelson
Dir. Bus. Dev. IP Licensing
Real
www.helixcommunity.org <http://www.helixcommunity.org/>
Office 925 838-5536 Mobile 925 890-5306
"The overall best codec was RealNetworks RealVideo."
StreamingMedia.com article by Jan Ozer 3/22/06
*********************** Aricent- Confidential
***********************
*********************** Aricent-Restricted
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely
for the use of
the individual to whom it is addressed. It may contain
privileged or
confidential information and should not be
circulated or used for any purpose other than for what it
is intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by this
email including damage from virus."
*********************** Aricent-Private ***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is
intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Rishi Mathew
Sr. Software Development Engineer
Helix Community
Real Networks, Inc.
real.com">rmathewreal.com
http://www.helixcommunity.org <http://www.helixcommunity.org/>
http://www.realnetworks.com/products/support/devsupport.html
<http://www.realnetworks.com/products/support/devsupport.html>
*********************** Aricent-Restricted
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is
intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Scott Nelson
Dir. Bus. Dev. IP Licensing
Real
www.helixcommunity.org <http://www.helixcommunity.org/>
Office 925 838-5536 Mobile 925 890-5306
"The overall best codec was RealNetworks RealVideo."
<http://www.streamingmedia.com/article.asp?id=9259>
StreamingMedia.com article by Jan Ozer
<http://www.streamingmedia.com/bio.asp?id=34657> 3/22/06
*********************** Aricent- Confidential
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is
intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Rishi Mathew
Sr. Software Development Engineer
Helix Community
Real Networks, Inc.
real.com">rmathewreal.com
http://www.helixcommunity.org <http://www.helixcommunity.org/>
http://www.realnetworks.com/products/support/devsupport.html
<http://www.realnetworks.com/products/support/devsupport.html>
*********************** Aricent- Confidential
***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is
intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Rishi Mathew
Sr. Software Development Engineer
Helix Community
Real Networks, Inc.
real.com">rmathewreal.com
http://www.helixcommunity.org <http://www.helixcommunity.org/>
http://www.realnetworks.com/products/support/devsupport.html
<http://www.realnetworks.com/products/support/devsupport.html>
*********************** Aricent-Private ***********************
"DISCLAIMER: This message is proprietary to Aricent and is
intended solely for the use of
the individual to whom it is addressed. It may contain privileged or
confidential information and should not be
circulated or used for any purpose other than for what it is
intended. If
you have received this message in error,
please notify the originator immediately. If you are not
the intended
recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the
contents of
this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information
transmitted by
this email including damage from virus."
Rishi Mathew
Sr. Software Development Engineer
Helix Community
Real Networks, Inc.
real.com">rmathewreal.com
http://www.helixcommunity.org <http://www.helixcommunity.org/>
http://www.realnetworks.com/products/support/devsupport.html
<http://www.realnetworks.com/products/support/devsupport.html>
*********************** Aricent-Unclassified
***********************
_______________________________________________
Helix-client-dev mailing list
helixcommunity.org">Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
*********************** Aricent-Unclassified
***********************
_______________________________________________
Helix-client-dev mailing list
helixcommunity.org">Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
|
