1.5.4

[Christopher Forsythe]

On Tue, Oct 2, 2012 at 12:20 PM, Joe Hildebrand (jhildebr) <
jhildebr at cisco.com> wrote:

> On 10/2/12 10:55 AM, "Robert Vehse" <robertvehse at fastmail.fm> wrote:
>
> >
> >Am 01.10.2012 um 09:02 schrieb Joe Hildebrand (jhildebr):
> >
> >> The WebEx Connect XMPP servers were generating the issue, but we've
> >>since
> >> upgraded TLS stacks so it doesn't happen anymore.  If you can't find a
> >> server to repro on, let me know, and I'll have someone try an old build
> >>in
> >> the lab.
> >
> >So how should we proceed? Should the patch still be considered? Is this a
> >server-side issue and if so, should it be worked around?
>
> There are other versions of our server out in the wild that have the same
> issue, that we can't get upgraded as easily.  As such, yes, the patch
> would still be nice.
>
> I just talked to Jack Erwin, who owns this team at Cisco.  He said that if
> you sent us a build of Adium containing the fix, we could have our QA
> department run it against the old version of our server in our lab to
> prove that the fix works.  I'd expect them to write a couple of bullets
> about what they tested and how it worked.
>
> You'd have to trust them for their results, but we're the ones harmed if
> they mess it up.
>
>
My experience working with cisco to test like this has been really
positive, including code contributions on the cisco end. I'd highly
recommend this path.


> --
> Joe Hildebrand
>
>
>
>
>


-- 
Chris Forsythe
@The_Tick <http://twitter.com/The_Tick>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20121002/8931c891/attachment-0002.html>