Discovery Scanner - 03.10.2022

[Elyria]

Guess we'll see if U14 still contains that command line parameter. I can see Frontier removing it without ever addressing it.

We haven't been able to get a yes/no on the intentionality of the argument working at all, other than the publicly-stated intent not to have Horizons 4.0 be easily accessible to the overwhelming majority of users who are unaware of the existence of command-line or minilauncher tools.

They could still ban users for it, despite what users are telling each other. They also could remove it in any other updates since no policy has been stated.

Stonewalling is going to be on par for this particular course. It makes me doubtful of their fulfilling their equally publicly-stated promise of merging the playerbases.

 

[Winterwalker]

@sallymorganmoore

Just wanted to say that I hope we get to hear more from Joy Senne. Loving the conspiracy theorist podcast type vibe she's giving out.

 

[aRJay]

5.0? Remove space flight/ships as a key feature overhaul?

Remove the CQC Arena and Open.

 

[Ned Flandalorian]

It wouldn't be too complicated to update the official launcher to add a single use key provided by the login server that could be passed to the elitedangerous64 executable to send back to the servers (to make sure that the executable has been start by the official launcher).

A session "key" (for want of a better word) is already passed from the launcher as an argument for the executable. min-ed-launcher does exactly the same thing.
As long as the launcher is a standalone executable that only passes arguments (even if it delivers them some other way such as using a shared memory object), it can be mimicked by a different application.

 

[St0rmFury]

I like the autumn themed paintjobs more than spring & summer ones. At least they cover the entire ship now.

 

[[VR] Mad Mike]

I like them as well...... but for me the star was that asp explorer yellow limited edition Halloween one. that was really cool. (and congrats to the winners, there were some nice shots in there...... there can be no argument that ED can create some fantastic space pr0n

 

[aRJay]

I like them as well...... but for me the star was that asp explorer yellow limited edition Halloween one. that was really cool. (and congrats to the winners, there were some nice shots in there...... there can be no argument that ED can create some fantastic space pr0n

Darn I forgot to watch the stream again.

That was nasty of you wording your post to make it seem like the Halloween competition was over already when there is almost a month to go.

 

[[VR] Mad Mike]

Darn I forgot to watch the stream again.

That was nasty of you wording your post to make it seem like the Halloween competition was over already when there is almost a month to go.

sorry... not my intention.... plenty of time to go. i was just commenting on the 1st batch of winners

 

[VALIDATING]

A session "key" (for want of a better word) is already passed from the launcher as an argument for the executable. min-ed-launcher does exactly the same thing.
As long as the launcher is a standalone executable that only passes arguments (even if it delivers them some other way such as using a shared memory object), it can be mimicked by a different application.

Not the same thing, a "single use key" would be like a two factor authentication between the server and the client only (think SMS message with a 6 digit key from google or paypal or FDEV connection email validation when login to the game the first time, only limited to client-server use).

Edited: If you use a command line argument with the same "single use key", the server would reject the connection since this key has already been used. Simple, really...

 

[Ned Flandalorian]

Edited: Not a session key, the key has to be usable only once to connect to the servers, if you use a command line argument with the same key, the server would reject the connection since this key has already been used.

The key already changes when the session expires/gets renewed, it's not constant (especially in the case of epic accounts). Regardless there is no reason min-ed-launcher couldn't perform the same authentication, whatever the method used.

 

[VALIDATING]

The key already changes when the session expires/gets renewed, it's not constant (especially in the case of epic accounts). Regardless there is no reason min-ed-launcher couldn't perform the same authentication, whatever the method used.

Nonsense.
Since the this key is just communicated between the launcher and the servers when clicking on the PLAY button of the launcher (or with the /EDO argument?).

• The launcher then start the ED executable with this key in the command line,
• The executable use this key to be granted access to the servers,
• After this point, the key is not usable anymore.

It would require disassembling/hacking the launcher to reproduce the same process which is a clear breach of the TOS (contrary to the current SeasonTwo command line argument, which doesn't hack anything).

To be clear, I am seriously disappointed (to say the least) at FDEV for not letting EDO customers have access to EDH4 through the launcher,
But since (for now) my friends and I still have access to 3.8 to play ED, 3.8 it is.

 

[VALIDATING]

...

 

[Ned Flandalorian]

It would require disassembling/hacking the launcher to reproduce the same process which is a clear breach of the TOS (contrary to the current SeasonTwo command line argument, which doesn't hack anything).

Suggest you look at what min-ed-launcher actually does, because it already performs authentication (either via a frontier login, or by communication with steam or epic) to retrieve the key to pass to the executable (completely different from the "season" argument). And how do you think that was made possible...

 

[VALIDATING]

Suit yourself...

 

[VALIDATING]

Suggest you look at what min-ed-launcher actually does, because it already performs authentication (either via a frontier login, or by communication with steam or epic) to retrieve the key to pass to the executable (completely different from the "season" argument). And how do you think that was made possible...

This is not a single use key, this key is linked to the player profile (since using the command line parameter connects you to your game character).
you don't seem to understand the difference between player identifier and single use key (time limited and single use only) that grant access to the game if sent back to the server in a timely manner and only ONCE (because THIS key would be invalid if send a second time through the command line).

Anyway this is wayyyy off topic so this is my last post about this subject.

 

[Sylveria]

This is not a single use key, this key is linked to the player profile (since using the command line parameter connects you to your game character).
you don't seem to understand the difference between player identifier and single use key (time limited and single use only) that grant access to the game if sent back to the server in a timely manner and only ONCE (because THIS key would be invalid if send a second time through the command line).

Anyway this is wayyyy off topic so this is my last post about this subject.

I've confirmed this using two separate accounts and two separate client downloads.

It's connected to the player account. Authentication isn't based on the "client" software, but rather the "entitlement" each account has been granted by Frontier.

If you connect with an account that owns Odyssey, it forces you to use Horizons 3.8 or Odyssey 4.0- you won't even see Horizons 4.0 in the list. If you connect using a Horizons account, it will refresh the available client list and remove Odyssey and supply Horizons 4.0 instead.

What's perplexing here is that Horizons 4.0 doesn't grant anything "special" or outside of what a customer has already paid for with the purchase of Odyssey, so denying access to Horizons 4.0 is especially bizarre as a decision.