Jump to content

CKAN (The Comprehensive Kerbal Archive Network); v1.28.0 - Dyson


politas

Recommended Posts

But:

  On 2/23/2018 at 6:38 AM, HebaruSan said:

You're WebClient, you figure it out!!

Expand  

It makes no sense for 1.2 to be disabled by default if you can autonegiotiate what the server supports...

#122 added to list: "why not using .NET, ever".

Edited by steve_v
Link to comment
Share on other sites

  On 2/23/2018 at 6:40 AM, steve_v said:

But:

It makes no sense for 1.2 to be disabled by default if you can autonegiotiate what the server supports...

Expand  

Autonegotiation is one thing, your client's pool of acceptable negotiation outcomes is another. If your default pool of acceptable protocols is { Ssl3, Tls1 } (as .NET 4.5's is), then a server that only allows Tls12 will fail your negotiations.

Edited by HebaruSan
Link to comment
Share on other sites

  On 2/23/2018 at 6:43 AM, HebaruSan said:

If your default pool of acceptable protocols is { Ssl3, Tls1 } (as .NET 4.5's is), then a server that only allows Tls12 will fail your negotiations.

Expand  

Indeed. But .NET 4.5.x does support TLS 1.2, it's just not enabled. It's the "not enabled by default" bit that is stupid.

Link to comment
Share on other sites

  On 2/23/2018 at 6:48 AM, steve_v said:

It's the "not enabled by default" bit that is stupid.

Expand  

Oh, very strongly agreed. :)

For what it's worth, they did fix it in .NET 4.6.

  On 2/23/2018 at 6:40 AM, steve_v said:

#122 added to list: "why not using .NET, ever".

Expand  

Is "32-bit only WinForms on OSX, OSX about to drop support for 32-bit" on that list yet? :wink:

Edited by HebaruSan
Link to comment
Share on other sites

@HebaruSanIs the build you posted to the github issue (ckan-tls12.zip) the current solution? Not working here:

  Reveal hidden contents

 

Link to comment
Share on other sites

  On 2/23/2018 at 8:02 AM, steve_v said:

@HebaruSanIs the build you posted to the github issue (ckan-tls12.zip) the current solution? Not working here:

  Reveal hidden contents

 

Expand  

Try running 'ckan update' from command prompt as recommended by HebaruSan from the Github issue thread https://github.com/KSP-CKAN/CKAN/issues/2293

Link to comment
Share on other sites

I'm trying to run the latest release of Ckan Guiana) on a fresh install of KSP but I'm getting this error on launch...  "Error in autoupdate:     The request was aborted: Could not create SSL/TLS secure channel."

Edited by Vichard
Link to comment
Share on other sites

Ok, it  looks like this TLS issue is pushing us to do a couple of things we'd rather not do:

 

  • Drop testing under Mono versions prior to 5.0. - Sorry Debian users, you may have to switch to the Mono Project for an updated Mono runtime.
  • Push our current Pre-release 2 branch to a release now - My pet project will have to wait for another release, but otherwise, I believe our working branch is looking pretty stable so we should be good.
Link to comment
Share on other sites

Will ckan be able to auto update itself once this is resolved? Or is the tls issue affecting the auto updater too? (only asking so I know whether I need to keep watching, or if it will just tell me when it's ready)

Edit: never mind. I should read the release notes first

Edited by severedsolo
Link to comment
Share on other sites

CKAN release 1.24.0 "Bruce" has been released!

68747470733a2f2f75706c6f61642e77696b696d


Changes since 1.22.6

  Reveal hidden contents

 

Notes

  • The auto-update function in previous releases will fail trying to upgrade to this version. You will need to download it manually and replace your previous copy.
  • You don't need to download AutoUpdate.exe. This is used internally by CKAN when a new version is released.
  • Windows users must have .NET 4.5 installed. SImply download the ckan.exe file and either store it in your game directory or somewhere in your filesystem that you have non-admin write access. Never run the CKAN client as Administrator!
  • libcurl is no longer used by CKAN for Linux or Mac. If you experience problems downloading, please contact us
  • Mac/Linux/Mono users: please use the new cert-sync tool, to update mono's certificate store.
  • Mac Users: You should only need to download and install the CKAN.dmg
  • The .deb file is for automated installation on Debian-based Linux distributions - Use dpkg-install/apt-get/apt to install the .deb file and you will then be able to run CKAN with just ckan instead of mono ckan.exe. All required libraries should be pulled in as dependencies.
  • This release of the CKAN has not been tested on Mono releases prior to 5.0.1. We highly recommend upgrading to the latest stable release of Mono from mono-project.com You will need the equivalent of the mono-complete package for your OS.

Release image public domain, courtesy NASA

Some fabulous new changes in this release:

  • A new consoleui command thanks to @HebaruSan, which is a thing of beauty:
    image
  • We now have a Right-Click menu on the modlist, which doesn't do much yet, but we'll be adding to it.
  • You can now import files you downloaded outside of CKAN into the CKAN cache
  • Failed downloads now give you an option to retry, and the download information you get before confirming also tells you which host the download is being sourced from.
  • We are now testing zip file validity when we process new mod versions, so badly formatted zip files will not make it into your CKAN list.
  • There is a new "History" folder under the CKAN folder, which stores a time-stamped modset after each action, so you can roll-back to previous working sets easily.
  • The client will now attempt to download FOSS mods from the Internet Archive if the primary download location fails (great for when Spacedock goes down)
  • Our longstanding issue of mods not appearing in any filter if they are "compatible", but have "incompatible" dependencies has been fixed, such mods are now correctly labelled as "incompatible" and will appear in that filter.
  • For simplification of CLI usage, we now have a prompt command that runs a Read-Execute-Print-Loop so you don't have to add all the same options every single time
  • We now check downloaded files against our stored checksum hash before adding to the cache, so a corrupted download will not be stored.
  • We've changed the way we handle downloads from GitHub to be compliant with their rules for downloads, which should help to avoid 403 Forbidden errors. You can now add your own Authentication token for sites that implement such a scheme (currently only GitHub)
  • Loads of other changes, mostly thanks to @HebaruSan, to whom I am extremely grateful

As always, many thanks to the rest of the CKAN team, especially @techman83 who keeps all the infrastructure running, @pjf who may be quiet, but is still working in the background to keep the lights on, and the CKAN Wranglers for tireless efforts to keep out metadata up to date.

As an aside, any YouTubers out there that have done videos on CKAN in the past - I would hugely appreciate if you could do a revisit to check all the recent changes.

Edited by politas
Link to comment
Share on other sites

  On 2/23/2018 at 3:32 PM, politas said:
  • You can now import files you downloaded outside of CKAN into the CKAN cache
  • Failed downloads now give you an option to retry, and the download information you get before confirming also tells you which host the download is being sourced from.
  • There is a new "History" folder under the CKAN folder, which stores a time-stamped modset after each action, so you can roll-back to previous working sets easily.
Expand  

Unexpected bonuses!

Link to comment
Share on other sites

@politas and @HebaruSan (and everyone else working on CKAN), I know there are a lot of very relieved and grateful people out there. A website and service not in your control made a mod-breaking change, and in approximately 1 day you had not only addressed the problem, but released new features as well. Thank you and well done!

Edited by eightiesboi
Removed "without warning", to avoid disparging GitHub :)
Link to comment
Share on other sites

  On 2/23/2018 at 4:07 PM, eightiesboi said:

@politas and @HebaruSan (and everyone else working on CKAN), I know there are a lot of very relieved and grateful people out there. A website and service not in your control made a mod-breaking change without warning, and in approximately 1 day you had not only addressed the problem, but released new features as well. Thank you and well done!

Expand  

To be fair...  Github announced this change back in July, I think, and they even did a one hour "brown out" earlier this month where they turned off TLS 1.1 to try to get the attention of people who hadn't already read the appropriate notices.

As a publisher of information, it's very difficult to make sure you reach all the people who need to have the information, and as a consumer of information, it's very hard to stay on top of everything when there's so much out there.  It's nobody's fault.  Everyone is trying to do their best.

And, yes, a superb job was done by everyone for diagnosing and fixing CKAN in less than a day. 

Link to comment
Share on other sites

  On 2/23/2018 at 4:20 PM, AG5BPilot said:

To be fair...  Github announced this change back in July, I think, and they even did a one hour "brown out" earlier this month where they turned off TLS 1.1 to try to get the attention of people who hadn't already read the appropriate notices.

Expand  

The very first announcement was about a year ago, but either no one on CKAN at the time saw it, or no one on CKAN realized the impact it would have.

  1 minute ago, AG5BPilot said:

As a publisher of information, it's very difficult to make sure you reach all the people who need to have the information, and as a consumer of information, it's very hard to stay on top of everything when there's so much out there.  It's nobody's fault.  Everyone is trying to do their best.

Expand  

Well, .NET could "just work." I would apportion a small amount of blame there.

  1 minute ago, AG5BPilot said:

And, yes, a superb job was done by everyone for diagnosing and fixing CKAN in less than a day. 

Expand  

Credit for that goes to @TruePikachu, who pointed out the GitHub announcements and suggested the code fix. I had no idea what I was looking at up till then, and frankly little hope of guessing it.

Link to comment
Share on other sites

  On 2/23/2018 at 4:20 PM, AG5BPilot said:

To be fair...  Github announced this change back in July, I think, and they even did a one hour "brown out" earlier this month where they turned off TLS 1.1 to try to get the attention of people who hadn't already read the appropriate notices.

As a publisher of information, it's very difficult to make sure you reach all the people who need to have the information, and as a consumer of information, it's very hard to stay on top of everything when there's so much out there.  It's nobody's fault.  Everyone is trying to do their best.

And, yes, a superb job was done by everyone for diagnosing and fixing CKAN in less than a day. 

Expand  

Sorry--I wasn't trying to blame anyone, just indicating my appreciation to the CKAN devs because I recognize the work they do that I (and many others) get to enjoy for free (or relatively little cost). I edited my post to clarify. Thanks for the heads-up.

Link to comment
Share on other sites

  On 2/22/2018 at 9:32 PM, MikeO89 said:

Been using ckan for awhile. Today I tried to start it and got this.

 

Error in autoupdate. The request was aborted: Could not create SSL/TLS secure channel.

Expand  

same. I opened ckan just fine earlier too. Then this happens suddenly.

  On 2/16/2018 at 1:57 AM, Loren Pechtel said:

I've seen that sort of behavior when the update couldn't be loaded--doesn't match your KSP version or a dependency doesn't match.  Note that by default CKAN is sensitive to even the smallest of version changes, even when the mods are still compatible.  In the menus there's an option for what KSP versions to accept as compatible.

Expand  

Ive usually noticed this when conflicts arise between mods. (eve configs+sve as example) unhighlight the mod and look for any mod in RED. It will tell you whats conflicting. Even if its a false flag(havnt seen too many tbh)

Link to comment
Share on other sites

First off, thank you for making the most essential KSP tool.

Just got the latest version, made sure .NET was updated for Windows (I'm on 4.7). Still having a failure.

NEVERMIND: Had to run "ckan update" on the command line

Edited by FleshJeb
Link to comment
Share on other sites

Thanks for the update but I have a problem.
I have two istances of KSP. In the test one CKAN work correctly (a little slow when add aviable mod update or import a ckan instal..). In the Main Installation, after opening , Appear this error:

  Quote

CKAN.ModuleNotFoundKraken: Generata eccezione di tipo 'CKAN.ModuleNotFoundKraken'.
   in CKAN.Registry.AllAvailable(String module)
   in CKAN.MainAllModVersions.set_SelectedModule(GUIMod value)
   in CKAN.Main.ModList_SelectedIndexChanged(Object sender, EventArgs e)
   in System.Windows.Forms.DataGridView.OnSelectionChanged(EventArgs e)
   in System.Windows.Forms.DataGridView.FlushSelectionChanged()
   in System.Windows.Forms.DataGridView.ClearSelection(Int32 columnIndexException, Int32 rowIndexException, Boolean selectExceptionElement)
   in System.Windows.Forms.DataGridView.SetAndSelectCurrentCellAddress(Int32 columnIndex, Int32 rowIndex, Boolean setAnchorCellAddress, Boolean validateCurrentCell, Boolean throughMouseClick, Boolean clearSelection, Boolean forceCurrentCellSelection)
   in System.Windows.Forms.DataGridView.MakeFirstDisplayedCellCurrentCell(Boolean includeNewRow)
   in System.Windows.Forms.DataGridView.OnRowCollectionChanged_PostNotification(Boolean recreateNewRow, Boolean allowSettingCurrentCell, CollectionChangeAction cca, DataGridViewRow dataGridViewRow, Int32 rowIndex)
   in System.Windows.Forms.DataGridViewRowCollection.OnCollectionChanged_PostNotification(CollectionChangeAction cca, Int32 rowIndex, Int32 rowCount, DataGridViewRow dataGridViewRow, Boolean changeIsDeletion, Boolean changeIsInsertion, Boolean recreateNewRow, Point newCurrentCell)
   in System.Windows.Forms.DataGridViewRowCollection.OnCollectionChanged(CollectionChangeEventArgs e, Int32 rowIndex, Int32 rowCount)
   in System.Windows.Forms.DataGridViewRowCollection.AddRange(DataGridViewRow[] dataGridViewRows)
   in CKAN.Main._UpdateFilters()
   in CKAN.Main._UpdateModsList(Boolean repo_updated, List`1 mc)
   in CKAN.Main.CurrentInstanceUpdated()
   in CKAN.Main.OnLoad(EventArgs e)
   in System.Windows.Forms.Form.OnCreateControl()
   in System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   in System.Windows.Forms.Control.CreateControl()
   in System.Windows.Forms.Control.WmShowWindow(Message& m)
   in System.Windows.Forms.Control.WndProc(Message& m)
   in System.Windows.Forms.Form.WmShowWindow(Message& m)
   in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Assembly caricati **************
mscorlib
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2633.0 built by: NET471REL1LAST_C
    Base di codice: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ckan
    Versione assembly: 1.24.0.0
    Versione Win32: 1.24.0
    Base di codice: file:///D:/Giochi/Kerbal%20Space%20Program/ckan.exe
----------------------------------------
System.Core
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2633.0 built by: NET471REL1LAST_C
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2612.0 built by: NET471REL1LAST_B
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Windows.Forms
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Transactions
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Windows.Forms.resources
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
mscorlib.resources
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_it_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
Microsoft.GeneratedCode
    Versione assembly: 1.0.0.0
    Versione Win32: 4.7.2612.0 built by: NET471REL1LAST_B
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Numerics
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0 built by: NET471REL1
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
System.Runtime.Serialization
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2612.0 built by: NET471REL1LAST_B
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll
----------------------------------------
System.Data
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2633.0 built by: NET471REL1LAST_C
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
    Versione assembly: 0.0.0.0
    Versione Win32: 4.7.2633.0 built by: NET471REL1LAST_C
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
Microsoft.CSharp
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll
----------------------------------------
System.Dynamic
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll
----------------------------------------
Microsoft.CSharp.resources
    Versione assembly: 4.0.0.0
    Versione Win32: 4.7.2556.0
    Base di codice: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp.resources/v4.0_4.0.0.0_it_b03f5f7f11d50a3a/Microsoft.CSharp.resources.dll
----------------------------------------

************** Debug JIT **************
Per abilitare il debug JIT, è necessario impostare il valore
jitDebugging nella sezione system.windows.forms del file di configurazione
dell'applicazione o del computer (machine.config).
L'applicazione inoltre deve essere compilata con il debug
abilitato.

Ad esempio:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Expand  

What can I do to fix it?
Thank you.

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...