14 days ago - CCP_Cemetery - Direct link

Howdo, todays launcher update improved the security and fundamental mechanics of how we handle and store tokens locally on Windows & macOS.

This change does not work on Linux, and we have no current plans to support it due to Linux not being a supported operating system by CCP at this time.

13 days ago - CCP_Bartender - Direct link

Hey all, CCP Bartender here!

There’s been a little bit of confusion about what’s happening with EVE and Linux. Let me do a little information dump and clarify some things.

Before we get to that, I want to reiterate that CCP discontinued official support for Linux in early 2009. A combination of some convenient early technical decisions and extra time by Linux-using devs has allowed Linux to remain surprisingly viable for the last decade, but it is not a supported operating system.

A forum post mentioned that the change yesterday would break how the launcher works on Linux. Our current business focus is on Windows and macOS. The change implemented is based on moving from storing tokens in our own home-rolled token storage mechanism to using secure credential storage on the OS itself. This is a significant boon to account security, and the safety of the accounts of our Windows and macOS users is simply a much higher priority than the ability to run on unsupported operating systems.

With that in mind, let’s talk about whether the EVE launcher works on Linux right this second. Because it is not a supported OS, we do not do QA on Linux machines. Occasionally, some ad-hoc testing on personal Linux machines, including my own, takes place, and the last time we did it, both the native and proton environments failed to launch clients.

Since that testing occurred, some fallbacks for credential handling have been implemented to allow for a more robust transition to OS credential storage while reducing the risk of mass-logout problems. By a happy chance, this means logins are still working under proton, which can run the Windows version of the launcher and has an up-to-date QT application binary. However, it is not working under the native launcher, which has not been updated for around a year, due to certain new dependencies that do not support Linux preventing compilation and thus has an outdated QT binary running the latest webUI.

Those using the native launcher should consider this the end of the road for that avenue of playing EVE under Linux. With the upcoming native port of the macOS client to Metal, once our Mac client does not require wine, that infrastructure will inevitably be torn down.

Fortunately for all Linux gamers, Valve has been doing a fantastic job with proton over the last few years, and at this time, you can use proton to play EVE (I certainly will be!). Key details of my currently functional setup are as follows:

  • Ubuntu 18.04
  • Proton 5.0-10
  • i7-4770-k
  • Nvidia RTX 1060
  • Kernel 4.15.0-147-generic

I hope this can act as a guide to help others who might be having issues get up and running again for now.

Let’s talk about the future, though. At some point, the transitionary code for the credential storage will be removed. When that happens, it is expected (but untested) that the same issue seen in the native launcher will express in the proton launcher too. There is some internal discussion about this, but at this time, Linux users should be aware that unless wine or proton adds support for the syscalls involved in the windows credential store, proton will eventually stop working too. The exact timeline for this is amorphous, and it is impossible to say whether that’s one month or twelve months. We might see support for the credential store land in upstream wine before that happens, but the matter is very much outside our scope for day-to-day work.

I hope it brings clarity to the discussion. Stay awesome, my fellow Linux nerds! o7

Removed some off topic posts.

10 days ago - CCP_Cemetery - Direct link

Howdo, I’m CCP Cemetery (Davy), and I’m the producer for our launcher team. If you’re unhappy with the recent update, or our messaging surrounding it then please accept my apologies.

To shed a little light on how our lack of advanced communication came to pass. While we knew that our latest update was not going to be compatible with Linux, with our available data we didn’t expect to inconvenience that many people at the time due to the majority of the Linux community making use of older launcher builds or Proton. This coupled with the fact that our Linux community are quite resilient and are often capable of adapting and solving issues when they arise, along with the fact that Linux is an unsupported platform, lead us to believe that messaging wouldn’t be required for this update. While this statement doesn’t necessarily excuse our lack of communication on this front, it should give some insight into how we came to the conclusion that advanced notification would not be required in this instance.

I do want to remind those still reading that at this time our development teams don’t officially develop for, test on or otherwise support Linux given that it’s an unsupported platform. As such teams may often not know that Linux users would be adversely affected by their work, and may not have a communication plan in place. However CCP does undergo public beta testing, such as our past and future Native Mac Client play tests, and everyone has the ability to try our beta launchers via the launcher settings menu under tools. As such I would encourage Linux users try out our beta releases since this is the only way to ensure some degree of testing on Linux, and may help the community to prepare in advance for upcoming changes.

In regards to this particular launcher security update, we have included backwards compatibility in our web UI for older launcher applications, such as the ones most Linux users are active on. However at some point we will need to deprecate this functionality in order to move forwards with planned improvements, harden security and to reduce our technical debt.

For those expressing security concerns, or those who feel the need to get in contact directly, simply file a support ticket and title it for the attention of CCP Cemetery, and I’ll be sure to read and respond where appropriate.

In closing, should our launcher team be aware of changes that may have serious repercussions to the greater Linux community, we will endeavour to communicate them in advance, and once again my apologies to those caught out by the lack of communication for our last release.

Have a good weekend and fly safe o7

CCP Cemetery (Davy)