Inara API

More about Inara API is on the API page, general dev guidelines are here and more detailed documentation about the events and data format here.

Just a note for tool authors using Inara API - please ensure your apps are doing  TWO requests per minute AT MAXIMUM. As I have discovered, many users are using multiple apps at once (nothing wrong with that), but are also updating their profiles from all of the applications at once, which is causing quite serious overhead. For such reason, I have needed to make API requests limits much tighter. For bots and other similar non-demanding apps are requests rates set same as before. If do you need another requests rate limit, please send me a PM.

Inara API update for Odyssey:
  • The header property isDeveloped was renamed to less confusing isBeingDeveloped. You don't need to change anything on your end though, the old property will still work.
  • A new event addCommanderTravelLand for commanders landing on the celestial body was added (should be triggered at journal's Touchdown, DropShipDeploy and similar).
  • The events addCommanderTravelCarrierJump, addCommanderTravelDock, addCommanderTravelFSDJump and setCommanderTravelLocation now contain optional properties for the star system coordinates, celestial body and celestial body coordinates. It's not required to set, it may however help to further precise commander's location when the star system is not in the database, etc.
  • The events addCommanderTravelDock, addCommanderTravelFSDJump and addCommanderTravelLand are now having boolean properties isTaxiShuttle and isTaxiDropship for travelling with Apex or Frontline Solutions ships.
  • New events setCommanderInventory, resetCommanderInventory, setCommanderInventoryItem, addCommanderInventoryItem and delCommanderInventoryItem added. Those are supposed for handling the new Odyssey events like ShipLockerMaterials and similar, you can however use it also for the existing engineering materials or ship cargo instead of the existing dedicated events (but you do not need to, they are not going anywhere).
  • New events setCommanderSuitLoadout, updateCommanderSuitLoadout and delCommanderSuitLoadout for the suit loadouts added.
[Dax]
09 May 2020, 5:28pm
Well, no joy
But you guided me to the right direction where to look. I dug deeper with Wireshark and it seems that in current setup Inara does not support any ciphers of TLS1.2 protocol implemented in Windows 7. Server drops the connection on the handshake stage with "Fatal handshake failure" response, just after receiving "Client Hello" message.
Is there any chance to enable support for any of these?

Win7 TLS1.2 Cipher Suites (26 suites):
   Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
   Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
   Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
   Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
   Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
   Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
   Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
   Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
   Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
   Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
   Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
   Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
   Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
   Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
   Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
   Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
   Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
   Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
   Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
   Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
   Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)
   Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
   Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
   Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
   Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
   Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)

In Win10 I see two additional suites:

   Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
   Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)

And Inara server negotiate to connect with EDDiscovery on Win10 with one of these, 0xc030 in particular.

It is possible though, that the issue is not with cipher suites support but with some another incompatible option, so just in case here is the full quote of the TLS part of the "Client Hello" message.
Thanks!

Win7 "Client Hello":

Transport Layer Security
   TLSv1.2 Record Layer: Handshake Protocol: Client Hello
       Content Type: Handshake (22)
       Version: TLS 1.2 (0x0303)
       Length: 163
       Handshake Protocol: Client Hello
           Handshake Type: Client Hello (1)
           Length: 159
           Version: TLS 1.2 (0x0303)
           Random: 5eb6d8cf343c6309f0c102c145f5a4070d648d773b19e8bb…
               GMT Unix Time: May  9, 2020 19:22:39.000000000 FLE Daylight Time
               Random Bytes: 343c6309f0c102c145f5a4070d648d773b19e8bb09f78743…
           Session ID Length: 0
           Cipher Suites Length: 52
           Cipher Suites (26 suites)
               Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)
               Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027)
               Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
               Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
               Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f)
               Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e)
               Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
               Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
               Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
               Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
               Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d)
               Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c)
               Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
               Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
               Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
               Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
               Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)
               Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)
               Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
               Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
               Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 (0x006a)
               Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 (0x0040)
               Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
               Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
               Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
               Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)
           Compression Methods Length: 1
           Compression Methods (1 method)
               Compression Method: null (0)
           Extensions Length: 66
           Extension: server_name (len=13)
               Type: server_name (0)
               Length: 13
               Server Name Indication extension
                   Server Name list length: 11
                   Server Name Type: host_name (0)
                   Server Name length: 8
                   Server Name: inara.cz
           Extension: supported_groups (len=6)
               Type: supported_groups (10)
               Length: 6
               Supported Groups List Length: 4
               Supported Groups (2 groups)
                   Supported Group: secp256r1 (0x0017)
                   Supported Group: secp384r1 (0x0018)
           Extension: ec_point_formats (len=2)
               Type: ec_point_formats (11)
               Length: 2
               EC point formats Length: 1
               Elliptic curves point formats (1)
                   EC point format: uncompressed (0)
           Extension: signature_algorithms (len=20)
               Type: signature_algorithms (13)
               Length: 20
               Signature Hash Algorithms Length: 18
               Signature Hash Algorithms (9 algorithms)
                   Signature Algorithm: rsa_pkcs1_sha512 (0x0601)
                   Signature Algorithm: ecdsa_secp521r1_sha512 (0x0603)
                   Signature Algorithm: rsa_pkcs1_sha256 (0x0401)
                   Signature Algorithm: rsa_pkcs1_sha384 (0x0501)
                   Signature Algorithm: rsa_pkcs1_sha1 (0x0201)
                   Signature Algorithm: ecdsa_secp256r1_sha256 (0x0403)
                   Signature Algorithm: ecdsa_secp384r1_sha384 (0x0503)
                   Signature Algorithm: ecdsa_sha1 (0x0203)
                   Signature Algorithm: SHA1 DSA (0x0202)
           Extension: extended_master_secret (len=0)
               Type: extended_master_secret (23)
               Length: 0
           Extension: renegotiation_info (len=1)
               Type: renegotiation_info (65281)
               Length: 1
               Renegotiation Info extension
Artie
09 May 2020, 6:25pm
To be honest, I am not very willing to fiddle with that and/or add older/weaker cipher suites there. If there is an option to add additional cipher suites to Win 7 (for example browsers like Chrome or Firefox are having no problem there), use that way. Otherwise, consider an upgrade as Win 7 is no longer supported by MS since January and it will get just worse.
[Dax]
09 May 2020, 6:43pm
ArtieTo be honest, I am not very willing to fiddle with that and/or add older/weaker cipher suites there. If there is an option to add additional cipher suites to Win 7 (for example browsers like Chrome or Firefox are having no problem there), use that way. Otherwise, consider an upgrade as Win 7 is no longer supported by MS since January and it will get just worse.

I see, so be it.
Unfortunately, I have not found any options yet to add these missing two suites to Win 7. And it seems this is the only difference in "Client Hello" between two OS. Upgrade to Win10 is not an option for me, unfortunately. I wonder if I am only user of Win7 here...

Anyway, thank you for your help and swift responses and sorry for wasting your time.
Take care and be safe in these turbulent times!
Thanks!
Bravada Cadelanne
12 May 2020, 10:48am
It looks like the cipherlist is something like "ECDHE+AESGCM:ECDHE+CHACHA20", with the RSA certificate limiting it to RSA ciphers.


$ openssl ciphers -v -stdname 'ECDHE+AESGCM:ECDHE+CHACHA20:!ECDSA'
TLS_AES_256_GCM_SHA384 - TLS_AES_256_GCM_SHA384  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(256) Mac=AEAD
TLS_CHACHA20_POLY1305_SHA256 - TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any      Au=any  Enc=CHACHA20/POLY1305(256) Mac=AEAD
TLS_AES_128_GCM_SHA256 - TLS_AES_128_GCM_SHA256  TLSv1.3 Kx=any      Au=any  Enc=AESGCM(128) Mac=AEAD
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 - ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AESGCM(256) Mac=AEAD
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AESGCM(128) Mac=AEAD
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 - ECDHE-RSA-CHACHA20-POLY1305 TLSv1.2 Kx=ECDH     Au=RSA  Enc=CHACHA20/POLY1305(256) Mac=AEAD


Running SSL Server Test gives the following cipher suites:


# TLS 1.3 (suites in server-preferred order)
TLS_AES_256_GCM_SHA384 (0x1302)                        ECDH x25519 (eq. 3072 bits RSA)
TLS_CHACHA20_POLY1305_SHA256 (0x1303)                  ECDH x25519 (eq. 3072 bits RSA)
TLS_AES_128_GCM_SHA256 (0x1301)                        ECDH x25519 (eq. 3072 bits RSA)

# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)         ECDH x25519 (eq. 3072 bits RSA)
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8)   ECDH x25519 (eq. 3072 bits RSA)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)         ECDH x25519 (eq. 3072 bits RSA)


Its browser emulation also shows Windows 8.1 and macOS 10.10 not being supported, and looking at Microsoft's Windows 8.1 Cipher List, none of the ECDHE-RSA-AESGCM ciphers are supported.

I wonder if Inara has any control (or say) over the LetsEncrypt certificate renewal process, and whether their host can generate an ECDSA certificate?
Artie
12 May 2020, 11:08am
Yeah, there is possible to make the situation easier for such users, but honestly - I do not want to spend time with that. Chrome/Firefox works on Win7/8 without any issues, newest Safari browsers should have no problem too, doesn't matter the MacOS version, so the only problem are IE 11 (and lower) browsers and custom apps on Win7/8. A number of users using those problematic combinations is very marginal, so it doesn't worth the effort - they will need to upgrade their systems/browsers sooner or later anyway.
Harbogast
23 May 2020, 7:18pm
I'm a Windows 7 user, and am suffering the same issues described above.
User218737
08 Jun 2020, 1:44pm
I found myself updating the Star Type for a number of systems, mostly fixing null settings (--) out on the edge of the Bubble and fixing red dwarf systems to read Class M instead of Class M (giant). It'd be nice to have API access to this setting, so I could run some code to crosscheck with say EDSM's API.
Artie
08 Jun 2020, 10:52pm
MojoroI found myself updating the Star Type for a number of systems, mostly fixing null settings (--) out on the edge of the Bubble and fixing red dwarf systems to read Class M instead of Class M (giant). It'd be nice to have API access to this setting, so I could run some code to crosscheck with say EDSM's API.

Thanks for the updates! I will rather make some bulk pass on this one day. It doesn't worth an effort to add API support for such static assets as stars (and it will be simply faster to update it directly).
Epidage
09 Jun 2020, 1:31pm
I cannot find anything on how to disable the Inara "auto-updates." All I can do is update manually. I need to turn off updates. I don't want to loose proof of my loss of progress on my Xbox with the Fleet Carrier update. When I loaded into the game this morning, I discovered that Frontier has wiped 2 months of game play from my account.
Artie
09 Jun 2020, 1:33pm
When you open Import Frontier data window, there is a small button to disable auto-updates. But as the Frontier's servers are still down, no updates are performed at the moment.
Epidage
09 Jun 2020, 3:42pm
ArtieWhen you open Import Frontier data window, there is a small button to disable auto-updates. But as the Frontier's servers are still down, no updates are performed at the moment.


Thank you Artie, I was afraid if I clicked on that blue "import" link box it would execute an update.  I see now that by clicking on that box it opens a smaller window with the "disable update" option.  I wish this option could be found as a line item in the "Settings > Account Settings" menu tab.  I think it would be a little more straight forward.
Artie
10 Jun 2020, 12:16pm
Minor update to the API - added addCommanderTravelCarrierJump event (but you can also use the existing addCommanderTravelFSDJump event, no big deal).

Most importantly, there is now implemented linking back to Inara through star system, station and minor faction names.
The link formats are following, don't forget to properly URL encode the search strings:
  • https://inara.cz/galaxy-starsystem/?search=STARSYSTEMNAME
  • https://inara.cz/galaxy-station/?search=STARSYSTEMNAME [STATIONNAME]
  • https://inara.cz/galaxy-minorfaction/?search=MINORFACTIONNAME
There are some link examples:
  • https://inara.cz/galaxy-starsystem/?search=Shinrarta%20Dezhra
  • https://inara.cz/galaxy-station/?search=Sothis%20[Newholm%20Station]
  • https://inara.cz/galaxy-minorfaction/?search=Inara%20Nexus
Heavy Johnson
13 Jun 2020, 11:50am
Windows 7 user here, and Inara supporter via paypal. Inara API updates broken for me is a downer. Updating for me is not currently an option.
John Kozak
14 Jun 2020, 8:45am
ArtieMinor update to the API - added addCommanderTravelCarrierJump event (but you can also use the existing addCommanderTravelFSDJump event, no big deal).

Most importantly, there is now implemented linking back to Inara through star system, station and minor faction names.
The link formats are following, don't forget to properly URL encode the search strings:
  • https://inara.cz/galaxy-starsystem/?search=STARSYSTEMNAME
  • https://inara.cz/galaxy-station/?search=STARSYSTEMNAME [STATIONNAME]
  • https://inara.cz/galaxy-minorfaction/?search=MINORFACTIONNAME
There are some link examples:
  • https://inara.cz/galaxy-starsystem/?search=Shinrarta%20Dezhra
  • https://inara.cz/galaxy-station/?search=Sothis%20[Newholm%20Station]
  • https://inara.cz/galaxy-minorfaction/?search=Inara%20Nexus

This is splendid Artie, thank you
Aleks Zakharov
21 Jun 2020, 9:08pm
Got this problem with every sync

Post a reply

You must be signed in to post here.
Inara API is... well... see sticky post for the details.