Return-Path: X-Original-To: apmail-axis-java-user-archive@www.apache.org Delivered-To: apmail-axis-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 99F7D4B3E for ; Wed, 29 Jun 2011 12:18:06 +0000 (UTC) Received: (qmail 88405 invoked by uid 500); 29 Jun 2011 12:18:04 -0000 Delivered-To: apmail-axis-java-user-archive@axis.apache.org Received: (qmail 88203 invoked by uid 500); 29 Jun 2011 12:18:03 -0000 Mailing-List: contact java-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@axis.apache.org Delivered-To: mailing list java-user@axis.apache.org Received: (qmail 88188 invoked by uid 99); 29 Jun 2011 12:18:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 12:18:03 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pierre.muller@gfi.fr designates 216.32.180.11 as permitted sender) Received: from [216.32.180.11] (HELO VA3EHSOBE001.bigfish.com) (216.32.180.11) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2011 12:17:58 +0000 Received: from mail157-va3-R.bigfish.com (10.7.14.242) by VA3EHSOBE001.bigfish.com (10.7.40.21) with Microsoft SMTP Server id 14.1.225.22; Wed, 29 Jun 2011 12:17:37 +0000 Received: from mail157-va3 (localhost.localdomain [127.0.0.1]) by mail157-va3-R.bigfish.com (Postfix) with ESMTP id 569B152819A for ; Wed, 29 Jun 2011 12:17:37 +0000 (UTC) X-SpamScore: -26 X-BigFish: VS-26(zzbb2dK617R1447R1102Kzz1202hzz8275ch8275bh8275dhz2fh87h2a8h668h839h8aah61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: CIP:213.199.187.153;KIP:(null);UIP:(null);IPVD:NLI;SRV:BULK;H:IE2RD2HUB013.red002.local;RD:none;EFVD:NLI Received-SPF: pass (mail157-va3: domain of gfi.fr designates 213.199.187.153 as permitted sender) client-ip=213.199.187.153; envelope-from=pierre.muller@gfi.fr; helo=IE2RD2HUB013.red002.local ;red002.local ; X-FB-DOMAIN-IP-MATCH: fail Received: from mail157-va3 (localhost.localdomain [127.0.0.1]) by mail157-va3 (MessageSwitch) id 1309349789132101_7325; Wed, 29 Jun 2011 12:16:29 +0000 (UTC) Received: from VA3EHSMHS010.bigfish.com (unknown [10.7.14.241]) by mail157-va3.bigfish.com (Postfix) with ESMTP id 149C81AA004E for ; Wed, 29 Jun 2011 12:16:29 +0000 (UTC) Received: from IE2RD2HUB013.red002.local (213.199.187.153) by VA3EHSMHS010.bigfish.com (10.7.99.20) with Microsoft SMTP Server (TLS) id 14.1.225.22; Wed, 29 Jun 2011 12:16:23 +0000 Received: from IE2RD2XVS231.red002.local ([10.43.202.73]) by IE2RD2HUB013.red002.local ([10.43.198.11]) with mapi; Wed, 29 Jun 2011 05:16:03 -0700 From: Muller Pierre To: "java-user@axis.apache.org" Date: Wed, 29 Jun 2011 05:17:39 -0700 Subject: Re: AW: NTLM authentication failed (password with non-latin characters) Thread-Topic: AW: NTLM authentication failed (password with non-latin characters) Thread-Index: Acw2VlCDqst5SalHS+O5oKoAQbGdJQ== Message-ID: <4E0B17E3.5070800@gfi.fr> References: <4E087F75.6020609@gfi.fr>,,<4E09D564.1070405@gfi.fr> In-Reply-To: Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 acceptlanguage: fr-FR, en-US x-msol: FooterAdded Content-Type: multipart/alternative; boundary="_000_4E0B17E35070800gfifr_" MIME-Version: 1.0 --_000_4E0B17E35070800gfifr_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks Martin. Actually I had a look at the HTTPClient trace : there was this warning "Cre= dential charset not configured, using HTTP element charset". Thus I tried your conf directive and other directives too : stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHAR_SET_EN= CODING, new String("utf-16")); stub._getServiceClient().getOptions().setProperty("CHARACTER_SET_ENCODING",= new String("utf-16")); DefaultHttpParams.getDefaultParams().setParameter("http.protocol.credential= -charset", new String("utf-16")); Only the last one makes the warning disappear, which is good. But I tried several charsets (utf-16,utf-8,iso-8859-1,cp1252), with and wit= hout U+00E9 ("myPasswordWithLetter_=E9" or "myPasswordWithLetter_\u00e9") := no success, I always get the same 401.1 error !! Cordialement, Pierre Muller Le 28/06/2011 17:15, Martin Gainty a =E9crit : options.setProperty("CHARACTER_SET_ENCODING",new String("UTF-16"); when configuring the text part instead of typing displayable ASCII characte= r =E9 try U+00E9 http://en.wikipedia.org/wiki/ASCII#Unicode Martin Gainty ______________________________________________ Jogi =E9s Bizalmass=E1gi kinyilatkoztat=E1s/Verzicht und Vertraulichkeitanm= erkung/Note de d=E9ni et de confidentialit=E9 Ez az =FCzenet bizalmas. Ha nem =F6n az akinek sz=E1nva volt, akkor k=E9rj= =FCk, hogy jelentse azt nek=FCnk vissza. Semmif=E9le tov=E1bb=EDt=E1sa vagy= m=E1solat=E1nak k=E9sz=EDt=E9se nem megengedett. Ez az =FCzenet csak isme= ret cser=E9t szolg=E1l =E9s semmif=E9le jogi alkalmazhat=F3s=E1ga sincs. M= ivel az electronikus =FCzenetek k=F6nnyen megv=E1ltoztathat=F3ak, ez=E9rt m= inket semmi felel=F6s=E9g nem terhelhet ezen =FCzenet tartalma miatt. Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaeng= er sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterle= itung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient led= iglich dem Austausch von Informationen und entfaltet keine rechtliche Bindu= ngswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir= keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut =EAtre privil=E9gi=E9. Si vous n'=EAtes= pas le destinataire pr=E9vu, nous te demandons avec bont=E9 que pour satis= faire informez l'exp=E9diteur. N'importe quelle diffusion non autoris=E9e o= u la copie de ceci est interdite. Ce message sert =E0 l'information seuleme= nt et n'aura pas n'importe quel effet l=E9galement obligatoire. =C9tant don= n=E9 que les email peuvent facilement =EAtre sujets =E0 la manipulation, no= us ne pouvons accepter aucune responsabilit=E9 pour le contenu fourni. ________________________________ From: pierre.muller@gfi.fr To: java-user@axis.apache.org Date: Tue, 28 Jun 2011 06:21:40 -0700 Subject: Re: AW: NTLM authentication failed (password with non-latin charac= ters) Thanks for the answer. Actually I don't know how axis2 manages its stored-hashed. I can't say what= happens to the "=E9" because I pass the password to HttpTransportPropertie= s.Authenticator and I see it again in TCPMonitor as a NTLM hashed string, i= n which I can't say how "=E9" has been used. What is the tool used to generate and store the passwords? What does it in fact pass to the hashing algorithm? 1. A UTF-8-encoded stri= ngs or 2. A ISO-LATIN-encode-strings or 3. A double-byte-encoded -Unicode-s= tring? I pass the password-string to HttpTransportProperties.Authenticator , I don= 't use any other tool. The password-string is a standard Java String object= , which means (in my understanding of the javadoc ) represented in UTF-16 and = which libraries like axis2 should probably handle to take care of encoding = issues. Authenticating in a browser with the "=E9" works correctly (while accessing= the WSDL). Authenticating in Outlook also works correctly with this passwo= rd. The 401 error only occurs with the axis2 client application... Any idea ? Cordialement, Pierre Muller Le 27/06/2011 17:36, Stadelmann Josef a =E9crit : Somewhere there is a password data base which has stored password-hashes or= the like. Lets refer to it as stored-hashes. If the way hashes are generated from passwords, then transferred, then stor= ed by some tool differs from the way hashes are generated, transferred and= used toward the hasher by axis2 e all, in example by passing in one or the other direction a Iso-Latin-to-UTF-8 co= nverter in the later case, then the chance is real great that we will never reach a match on the hashe= s. So what happens to the "=E9" in sequence? How is it sent from client to ser= ver, as UTF-8 or as ISO-LATIN-1? TCP Monitor on a non-hashed transfer can t= ell you that. What is the tool used to generate and store the passwords? What does it in fact pass to the hashing algorithm? 1. A UTF-8-encoded stri= ngs or 2. A ISO-LATIN-encode-strings or 3. A double-byte-encoded -Unicode-s= tring? As the password generator is potentially a Microsoft one, I would suggest t= he "hasher" receives a double-byte-encoded-UNICODE-strings for an "=E9" BUT The axis2-web-service receives potentially a "double-byte-encoded-UTF-8-str= ing" for a single "=E9" and without converting this 2 bytes to UNICODE prio= r to passing it to the hasher the hasher will generate something different = then what is stored in the password-database and the match fails and result= s in UNAUTHENTICATED. Josef Von: Muller Pierre [mailto:pierre.muller@gfi.fr] Gesendet: Montag, 27. Juni 2011 15:03 An: java-user@axis.apache.org Betreff: NTLM authentication failed (password with non-latin characters) Hello, I'm working on a web application consuming web services with Axis2. Client = classes are generated from a WSDL file with the XMLBeans method. The web services require NTLM authentication, which I set up in my applicat= ion. Everything's fine, the application works as expected (able to authenticate,= able to use services). Except in one case : when the NTLM password contain= s accents, e.g. "myPasswordWithLetter_=E9". Does someone know about this, i= s this a filed bug for Axis2 (I couldn't find anythind on it so far) ? Are = there any solutions to bypass it ? Thanks Pierre More detailed information : 1. The services requested are Exchange Web Service ones. Again, it's workin= g fine for passwords without accents. 2. My authentication code is : URL endpoint =3D new URL(...); HttpTransportProperties.Authenticator authenticator =3D new HttpTransportPr= operties.Authenticator(); authenticator.setAuthSchemes(Arrays.asList(HttpTransportProperties.Authenti= cator.NTLM)); authenticator.setUsername("user"); authenticator.setPassword("myPasswordWithLetter_=E9"); authenticator.setHost(endpoint.getHost()); authenticator.setPort(endpoint.getPort()!=3D-1? endpoint.getPort() : endpoint.getProtocol().equalsIgnoreCase("https")? 443= : 80); authenticator.setDomain(conf.getAgendaHttpAuthDomain()); stub._getServiceClient().getOptions().setProperty(HTTPConstants.AUTHENTICAT= E, authenticator); 3. The password is showing healthy in Java, no encoding problem. 4. TCPMonitor shows similar behaviours with or without accents in the passw= ord : 3 POST requests, only the last differing between the expected SOAP re= sponse or the "HTTP 401.1 Unauthorized" seen below : Application request Server response POST /EWS/Exchange.asmx HTTP/1.1 Content-Type: text/xml; charset=3DUTF-8 SOAPAction: "http://schemas.microsoft.com/exchange/services/2006/messages/F= indItem" User-Agent: Axis2 Host: vm-iodasxch:8989 Transfer-Encoding: chunked 322 User-Agent: Axis2 Transfer-Encoding: chunked Authorization: NTLM TlRMTVNTUAABAAAABlIAAAgACAApAAAACQAJACAAABMT0NBTE hPU1R= JT0RBU1hDSA=3D=3D Host: localhost:8989 322 User-Agent: Axis2 Transfer-Encoding: chunked Authorization: NTLM TlRMTVNTUAADAAAAGAAYAFYAAAAAAAAAbgAAAAgACABAAAAA BQAFAE= gAAAAJAAkATQAAAAAAAAuAAAABlIAAElPREFTWENIVEVTVDFMT0NBTEhPU 1QbF84penGv2i5dP= WJzY1FKXnOm/wIvn0I=3D Host: localhost:8989 322 Thanks Martin.
Actually I had a look at the HTTPClient trace : there was this warning &quo= t;Credential charset not configured, using HTTP element charset&qu= ot;.
Thus I tried your conf directive and other directives too :
stub._getServiceClient().getOptions().setProperty(HTTPConstants.CHAR_SE= T_ENCODING, new String("utf-16"));
stub._getServiceClient().getOptions().setProperty("CHARACTER_SET_ENCOD= ING", new String("utf-16"));
DefaultHttpParams.getDefaultParams().setParameter("http.protocol.cr= edential-charset", new String("utf-16"));

Only the last one makes the warning disappear, which is good.
But I tried several charsets (utf-16,utf-8,iso-8859-1,cp1252), with and wit= hout U+00E9 ("myPasswordWithLetter_=E9" or "myPasswordWithLetter_\u00e9") : no success, I a= lways get the same 401.1 error !!


Cordialement,
Pierre Muller

Le 28/06/2011 17:15, Martin Gainty a =E9crit :
options.setProperty("CHARACTER_SET_ENCODING",new= String("UTF-16");
when configuring the text part instead of typing displayable ASCII characte= r =E9 try
U+00E9

http://en.wikipedia.org/wiki/ASCII#Unicode
Martin Gainty
______________________________________________
Jogi =E9s Bizalmass=E1gi kinyilatkoztat=E1s/Verzicht und Vertraulichkeitanm= erkung/Note de d=E9ni et de confidentialit=E9
 
Ez az =FCzenet bizalmas.  Ha nem =F6n az akinek sz=E1nva volt, ak= kor k=E9rj=FCk, hogy jelentse azt nek=FCnk vissza. Semmif=E9le tov=E1bb=EDt= =E1sa vagy m=E1solat=E1nak k=E9sz=EDt=E9se nem megengedett.  Ez az =FC= zenet csak ismeret cser=E9t szolg=E1l =E9s semmif=E9le jogi alkalmazhat=F3s= =E1ga sincs.  Mivel az electronikus =FCzenetek k=F6nnyen megv=E1ltoztathat=F3ak, e= z=E9rt minket semmi felel=F6s=E9g nem terhelhet ezen =FCzenet tartalma miat= t.

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaeng= er sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterle= itung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient led= iglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Mani= pulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt ueberne= hmen.
Ce message est confidentiel et peut =EAtre privil=E9gi=E9. Si vous n'=
=EAtes pas le destinataire pr=E9vu, nous te demandons avec bont=E9 que pour=
 satisfaire informez l'exp=E9diteur. N'importe quelle diffusion non autoris=
=E9e ou la copie de ceci est interdite. Ce message sert =E0 l'information s=
eulement et n'aura pas n'importe quel effet l=E9galement obligatoire. =C9ta=
nt donn=E9 que les email peuvent facilement =EAtre sujets =E0 la manipulati=
on, nous ne pouvons accepter aucune responsabilit=E9 pour le contenu fourni=
.



From: pierre.muller@gfi.fr
To: java-user@axis.apache.org
Date: Tue, 28 Jun 2011 06:21:40 -0700
Subject: Re: AW: NTLM authentication failed (password with non-latin charac= ters)

Thanks for the answer.
Actually I don't know how axis2 manages its stored-hashed. I can't say what= happens to the "=E9" because I pass the password to HttpTranspor= tProperties.Authenticator and I see it again in TCPMonitor as a NTLM hashed= string, in which I can't say how "=E9" has been used.

What is the tool used to generate and= store the passwords?

What does it in fact pass to the hashing algorithm? 1. A UTF-8-encoded = strings or 2. A ISO-LATIN-encode-strings or 3. A double-byte-encoded -Unicode-string?
I pass the password-string to HttpTransportProperties.Authenticator , I don= 't use any other tool. The password-string is a standard Java String object= , which means (in my understanding of the javadoc ) represented in UTF-16 and which libraries like axis2 shou= ld probably handle to take care of encoding issues.

Authenticating in a browser with the "=E9" works correctly (while= accessing the WSDL). Authenticating in Outlook also works correctly with t= his password. The 401 error only occurs with the axis2 client application..= .


Any idea ?


Cordialement,
Pierre Muller

Le 27/06/2011 17:36, Stadelmann Josef a =E9crit :

Somewhere there is a password d= ata base which has stored password-hashes or the like.

 

Lets refer to it as stored-hash= es.

 

If the way hashes are generated= from passwords, then transferred, then stored  by some tool differs from the way hashes are generated, transferred and used toward the= hasher  by axis2 e all,

in example by passing in one or= the other direction a Iso-Latin-to-UTF-8 converter in the later case,

then the chance is real great t= hat we will never reach a match on the hashes.

 

So what happens to the "= =E9" in sequence? How is it sent from client to server, as UTF-8 or as ISO-LATIN-1? TCP Monitor on a non-hashed transfer can tell you that.

 

What is the tool used to genera= te and store the passwords?

What does it in fact pass to th= e hashing algorithm? 1. A UTF-8-encoded strings or 2. A ISO-LATIN-encode-st= rings or 3. A double-byte-encoded -Unicode-string?

 

As the password generator is po= tentially a Microsoft one, I would suggest the "hasher" receives a double-byte-encoded-UNICODE-strings  for an "=E9" =

 

BUT

 

The axis2-web-service receives = potentially a "double-byte-encoded-UTF-8-string" for a single "=E9" and without converting this 2 bytes to UNICODE prior to pa= ssing it to the hasher the hasher will generate something different then wh= at is stored in the password-database and the match fails and results in UN= AUTHENTICATED.

 

Josef

 

 

Von: Muller Pierre [mailto:pierre.muller@gfi.fr]
Gesendet: Montag, 27. Juni 2011 15:03
An: java-user@axis.apache.org
Betreff: NTLM authentication failed (password with non-latin charact= ers)

 

Hello,

I'm working on a web application consuming web services with Axis2. Client = classes are generated from a WSDL file with the XMLBeans method.
The web services require NTLM authentication, which I set up in my applicat= ion.

Everything's fine, the application works as expected (able to authenticate,= able to use services). Except in one case : when the NTLM password contain= s accents, e.g. "myPasswordWithLetter_=E9". Does someone know abo= ut this, is this a filed bug for Axis2 (I couldn't find anythind on it so far) ? Are there any solutions to bypass it ?

Thanks
Pierre



More detailed information :
1. The services requested are Exchange Web Service ones. Again, it's= working fine for passwords without accents.

2. My authentication code is :
URL endpoint =3D new URL(...);<= /tt>
HttpTransportProperties.Authenticator = authenticator =3D new HttpTransportProperties.Authenticator();<= span style=3D"font-size: 10pt;">
authenticator.setAuthSchemes(Arrays.asList(HttpTransportProperties.Auth= enticator.NTLM));
authenticator.setUsername("user");
authenticator.setPassword("myPasswordWithLetter_=E9"); authenticator.setHost(endpoint.getHost());
authenticator.setPort(endpoint.getPort()!=3D-1? endpoint.getPort()=
              &n= bsp;     : endpoint.getProtocol().equalsIgnoreCase("htt= ps")? 443 : 80);
authenticator.setDomain(conf.getAgendaHttpAuthDomain());
stub._getServiceClient().getOptions().setProperty(HTTPConstants.AUTHENT= ICATE, authenticator);

3. The password is showing healthy in Java, no encoding problem.

4. TCPMonitor shows similar behaviours with or without accents in th= e password : 3 POST requests, only the last differing between the expected = SOAP response  or the  "HTTP 401.1 Unauthorized" seen b= elow :

Application request

Server response

POST /EWS/Ex= change.asmx HTTP/1.1
Content-Type: text/xml; charset=3DUTF-8
SOAPAction: "http://schemas.microsoft.com/exchange/services/2006/messages/FindItem= "
User-Agent: Axis2
Host: vm-iodasxch:8989
Transfer-Encoding: chunked

322
<?xml version=3D'1.0' encoding=3D'UTF-8'?><soapenv:Envelope .<= /tt>

HTTP/1.= 1 401 Unauthorized
Content-Length: 1897
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
Date: Mon, 27 Jun 2011 10:05:06 GMT

POST /EWS/Ex= change.asmx HTTP/1.1
Content-Type: text/xml; charset=3DUTF-8
SOAPAction: "http://schemas.microsoft.com/exchange/services/2006/messages/FindItem= "
User-Agent: Axis2
Transfer-Encoding: chunked
Authorization: NTLM TlRMTVNTUAABAAAABlIAAAgACAApAAAACQAJACAAABMT0NBTE h= PU1RJT0RBU1hDSA=3D=3D
Host: localhost:8989

322
<?xml version=3D'1.0' encoding=3D'UTF-8'?><soapenv:Envelope&nb= sp; ..

HTTP/1.= 1 401 Unauthorized
Content-Length: 1776
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: NTLM TlRMTVNTUAACAAAACAAIADgAAAAGAoECgB4YkR3A1OQAAAAA= AAA AAM4AzgBAAAAABQLODgAAAA9JT0RBU1hDSAIAEABJAE8ARABBAFMAWABDAEgAAQAWAFY AT= QAtAEkATwBEAEEAUwBYAEMASAAEACgAaQBvAGQAYQBzAHgAYwBoAC4AZwBmAGkALgBw AHIAaQB= 2AGEAdABlAAMAQAB2AG0ALQBpAG8AZABhAHMAeABjAGgALgBpAG8AZABhAHMAeAB jAGgALgBnAGYAaQAuAHAAcgBpAHYAYQB0AGUABQAoAGkAbwBkAGEAcwB4AGMAaAAuAGcAZg Bp= AC4AcAByAGkAdgBhAHQAZQAAAAAA
X-Powered-By: ASP.NET
Date: Mon, 27 Jun 2011 10:05:06 GMT

POST /EWS/Ex= change.asmx HTTP/1.1
Content-Type: text/xml; charset=3DUTF-8
SOAPAction: "http://schemas.microsoft.com/exchange/services/2006/messages/FindItem= "
User-Agent: Axis2
Transfer-Encoding: chunked
Authorization: NTLM TlRMTVNTUAADAAAAGAAYAFYAAAAAAAAAbgAAAAgACABAAAAA BQ= AFAEgAAAAJAAkATQAAAAAAAAuAAAABlIAAElPREFTWENIVEVTVDFMT0NBTEhPU 1QbF84penGv2= i5dPWJzY1FKXnOm/wIvn0I=3D
Host: localhost:8989

322
<?xml version=3D'1.0' encoding=3D'UTF-8'?><soapenv:Envelope .<= /tt>

HTTP/1.= 1 401 Unauthorized
Content-Length: 1776
Content-Type: text/html
Server: Microsoft-IIS/6.0
WWW-Authenticate: Negotiate
WWW-Authenticate: NTLM
X-Powered-By: ASP.NET
Date: Mon, 27 Jun 2011 10:05:06 GMT

 



-- 
Cordialement,
Pierre Muller


Ce message et toutes = les pi=E8ces jointes (ci-apr=E8s le =AB message =BB) sont confidentiels et = =E9tablis =E0 l'intention exclusive de ses destinataires. Toute utilisation de ce message non conforme =E0 sa destination, toute diffusion ou toute pu= blication, totale ou partielle, est interdite, sauf autorisation expresse d= es parties. Si vous recevez ce message par erreur, merci de le d=E9truire s= ans en conserver de copie et d'en avertir imm=E9diatement l'exp=E9diteur. Internet ne permettant pas de garantir l'i= nt=E9grit=E9 de ce message, le groupe GFI Informatique d=E9cline toute resp= onsabilit=E9 au titre de ce message s'il a =E9t=E9 modifi=E9, alt=E9r=E9, d= =E9form=E9 ou falsifi=E9. Par ailleurs et malgr=E9 toutes les pr=E9cautions prises pour =E9viter la pr=E9sence de virus dans nos envois,= nous vous recommandons de prendre, de votre c=F4t=E9, les mesures permetta= nt d'assurer la non-introduction de virus dans votre syst=E8me informatique= .
This email message and any attachments ("the email") are confiden= tial and intended only for the recipient(s) indicated. If you are not an in= tended recipient, please be advised that any use, dissemination, forwarding= or copying of this email whatsoever is prohibited without prior written consent. If you have received this email in error, p= lease delete it without saving a copy and notify the sender immediately. In= ternet emails are not necessarily secured, and GFI Informatique Group decli= nes responsibility for any changes that may have been made to this email after it was sent. While we take all= reasonable precautions to ensure that viruses are not transmitted via emai= ls, we recommend that you take your own measures to prevent viruses from en= tering your computer system.


Ce message et toutes les pi= =E8ces jointes (ci-apr=E8s le =AB message =BB) sont confidentiels et =E9tab= lis =E0 l'intention exclusive de ses destinataires. Toute utilisation de ce= message non conforme =E0 sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisatio= n expresse des parties. Si vous recevez ce message par erreur, merci de le = d=E9truire sans en conserver de copie et d'en avertir imm=E9diatement l'exp= =E9diteur. Internet ne permettant pas de garantir l'int=E9grit=E9 de ce message, le groupe GFI Informatique d=E9= cline toute responsabilit=E9 au titre de ce message s'il a =E9t=E9 modifi= =E9, alt=E9r=E9, d=E9form=E9 ou falsifi=E9. Par ailleurs et malgr=E9 toutes= les pr=E9cautions prises pour =E9viter la pr=E9sence de virus dans nos envois, nous vous recommandons de prendre, de votre c=F4t=E9, les mesu= res permettant d'assurer la non-introduction de virus dans votre syst=E8me = informatique.
This email message and any attachments ("the email") are confiden= tial and intended only for the recipient(s) indicated. If you are not an in= tended recipient, please be advised that any use, dissemination, forwarding= or copying of this email whatsoever is prohibited without prior written consent. If you have received this email in error, p= lease delete it without saving a copy and notify the sender immediately. In= ternet emails are not necessarily secured, and GFI Informatique Group decli= nes responsibility for any changes that may have been made to this email after it was sent. While we take all= reasonable precautions to ensure that viruses are not transmitted via emai= ls, we recommend that you take your own measures to prevent viruses from en= tering your computer system.

Ce message et toutes les pi= =E8ces jointes (ci-apr=E8s le =AB message =BB) sont confidentiels et =E9tab= lis =E0 l'intention exclusive de ses destinataires. Toute utilisation de ce= message non conforme =E0 sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisatio= n expresse des parties. Si vous recevez ce message par erreur, merci de le = d=E9truire sans en conserver de copie et d'en avertir imm=E9diatement l'exp= =E9diteur. Internet ne permettant pas de garantir l'int=E9grit=E9 de ce message, le groupe GFI Informatique d=E9= cline toute responsabilit=E9 au titre de ce message s'il a =E9t=E9 modifi= =E9, alt=E9r=E9, d=E9form=E9 ou falsifi=E9. Par ailleurs et malgr=E9 toutes= les pr=E9cautions prises pour =E9viter la pr=E9sence de virus dans nos envois, nous vous recommandons de prendre, de votre c=F4t=E9, les mesu= res permettant d'assurer la non-introduction de virus dans votre syst=E8me = informatique.
This email message and any attachments ("the email") are confiden= tial and intended only for the recipient(s) indicated. If you are not an in= tended recipient, please be advised that any use, dissemination, forwarding= or copying of this email whatsoever is prohibited without prior written consent. If you have received this email in error, p= lease delete it without saving a copy and notify the sender immediately. In= ternet emails are not necessarily secured, and GFI Informatique Group decli= nes responsibility for any changes that may have been made to this email after it was sent. While we take all= reasonable precautions to ensure that viruses are not transmitted via emai= ls, we recommend that you take your own measures to prevent viruses from en= tering your computer system.
 --_000_4E0B17E35070800gfifr_--