Re: rdesktop seg fault possibly related to MS13-029

Brian D <[email protected]> Mon, 22 Apr 2013 11:17:35 -0400
Newsgroups gmane.network.rdesktop.devel
Message-ID <CAEWMk_Rap9CtzjuJJ2TGeeTrtr+SGJJw6BctDgRCpnyYYEQ8AQ@mail.gmail.com>
--===============4704743181870700754==
Content-Type: multipart/alternative; boundary=089e0118304a8eceac04daf4917b

--089e0118304a8eceac04daf4917b
Content-Type: text/plain; charset=UTF-8

Hi Henrik,

The r1710 fix has fixed this situation for me.

Interestingly enough I was testing the old version just to make certain the
issue still existed.  What I found is that if I was already logged into the
remote system, TLS was being attempted and my connection crashed.  If
however I was not logged in, the old released version,
rdesktop-1.7.1-2.1.2, was working for the initial login.

In either case, this latest fix solved it.  Thank you for your diligence.

Thanks for the pointer on TLS Authentication, I will take a look at that
option as well.

Regarding the "new NLA code" you mention, are you saying a server side
change did indeed come with the patch I mentioned that appeared to be
client only?  Just trying to confirm that's how this issue started, as I've
been using it for over a year without any problems.

Thanks,
Brian

On Thu, Apr 18, 2013 at 3:30 AM, Henrik Andersson <
[email protected]> wrote:

>  Hi Brian,
>
> I was pretty sure that rdesktop would fallback to plain RDP connection but
> that was not the case. I have pushed a fix to upstream for that. Could you
> update and recompile rdesktop to verify the functionlity.
>
>
> Regards,
>
> Henrik Andersson
>
>
> On 04/18/2013 07:37 AM, Henrik Andersson wrote:
>
> Hi Brian,
>
> This is due to the new NLA code of rdesktop, your server presents it can
> do TLS but you do not have a certificate assigned to the RDP-tcp connection
> which will make rdesktop fallback to use non TLS eg. plain RDP protocol.
>
> See following article how to configure a certificate for your server,
> http://support.microsoft.com/kb/895433, which applies on both 2003 and
> 2008.
>
>
> Regards,
>
> Henrik Andersson
>
>

--089e0118304a8eceac04daf4917b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Henrik,<div><br></div><div>The r1710 fix has fixed this=
 situation for me.</div><div><br></div><div>Interestingly enough I was test=
ing the old version just to make certain the issue still existed. =C2=A0Wha=
t I found is that if I was already logged into the remote system, TLS was b=
eing attempted and my connection crashed. =C2=A0If however I was not logged=
 in, the old released version, rdesktop-1.7.1-2.1.2, was working for the in=
itial login.</div>
<div><br></div><div>In either case, this latest fix solved it. =C2=A0Thank =
you for your=C2=A0diligence.</div><div><br><div class=3D"gmail_extra">Thank=
s for the pointer on TLS Authentication, I will take a look at that option =
as well.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra" style>Regar=
ding the &quot;new NLA code&quot; you mention, are you saying a server side=
 change did indeed come with the patch I mentioned that appeared to be clie=
nt only? =C2=A0Just trying to confirm that&#39;s how this issue started, as=
 I&#39;ve been using it for over a year without any problems.</div>
<div class=3D"gmail_extra" style><br></div><div class=3D"gmail_extra">Thank=
s,</div><div class=3D"gmail_extra">Brian</div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Thu, Apr 18, 2013 at 3:30 AM, Henrik Anders=
son <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" ta=
rget=3D"_blank">[email protected]</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>Hi Brian,<br>
      <br>
      I was pretty sure that rdesktop would fallback to plain RDP
      connection but that was not the case. I have pushed a fix to
      upstream for that. Could you update and recompile rdesktop to
      verify the functionlity.<br>
      <br>
      <br>
      Regards,<br>
      <br>
      Henrik Andersson<div><div class=3D"h5"><br>
      <br>
      On 04/18/2013 07:37 AM, Henrik Andersson wrote:<br>
    </div></div></div>
    <blockquote type=3D"cite"><div><div class=3D"h5">Hi
      Brian,
      <br>
      <br>
      This is due to the new NLA code of rdesktop, your server presents
      it can do TLS but you do not have a certificate assigned to the
      RDP-tcp connection which will make rdesktop fallback to use non
      TLS eg. plain RDP protocol.
      <br>
      <br>
      See following article how to configure a certificate for your
      server, <a href=3D"http://support.microsoft.com/kb/895433" target=3D"=
_blank">http://support.microsoft.com/kb/895433</a>, which applies on
      both 2003 and 2008.
      <br>
      <br>
      <br>
      Regards,
      <br>
      <br>
      Henrik Andersson
      <br></div></div></blockquote></div></blockquote></div><br></div></div=
></div>

--089e0118304a8eceac04daf4917b--


--===============4704743181870700754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
--===============4704743181870700754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rdesktop-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rdesktop-devel

--===============4704743181870700754==--