Missing legacy client

[Joseph Hales]

Ubuntu 12.04 SVN 3410 when I go to the web page for the client on my server and select the legacy client I receive a 0k zip file without anything in it.

[Wayne Workman]

Because it’s you, I assume you’ve already ran the installer again?

[Tom Elliott]

I’m going to guess, try upgrading to 3414?

[Joseph Hales]

Will do I was just checking in case legacy clients had been dropped in SVN in favor of the new one I will update today.

[Wayne Workman]

For the record - I do not want the legacy client dropped.

The new client has yet to work for me.

[Joseph Hales]

You recommended SVN 3414 should I avoid the latest then which is at 3451?

[Joe Schmitt]

@Wayne-Workman For the record, the legacy client will not be dropped in v1.3.*. However, what will happen is that we will create a checkbox for disabling it. Why? Security. The legacy client opens up many security holes, which the new client does not have.

[Tom Elliott]

@Joseph-Hales said:

You recommended SVN 3414 should I avoid the latest then which is at 3451?

My recommendation is an assumption that you’re using new client, and anything past 3414 will break the new client, especially if you’re using FOG_AES_ENCRYPTED.

[Wayne Workman]

@Tom-Elliott said:

@Joseph-Hales said:

You recommended SVN 3414 should I avoid the latest then which is at 3451?

My recommendation is an assumption that you’re using new client, and anything past 3414 will break the new client, especially if you’re using FOG_AES_ENCRYPTED.

That explains a lot…

So… What should I do? Just not worry about the hosts that have the Legacy Client? Just let it go, and go full speed ahead with the new? That’s sorta terrifying…

[Joe Schmitt]

it breaks the new client because we have been implementing our entire security system for the new client. v0.8.0 of the client will be a million times more secure then the current beta.

[Joseph Hales]

We’re not using the new client yet I upgraded to SVN 3463 this morning which fixed the missing client issue.