What changed
0 fixes2 additions4 changes0 removals
addedWhere's Arynnia?Long story short, my ability to release new versions of *Idle Space Navy* got compromised when my computer failed and I had to move to much different hardware. I was not able to get my signing certificate at the time to move onto the new computer, which left me unable to release new code-signed versions of Idle Space Navy - thereby hamstringing the Milestone Program and preventing further releases.
addedWill the Milestone Program be reopening?Given that some of the people who were in the original Milestone Program are no longer present in the Phoenix Aura Discord (join if you want to at this link ), I will likely be reopening the Milestone Program to new testers once development resumes. The best place to find out about this will be the Aura Discord, but I will make an announcement here as well.
changedUnity Vulnerability: What Does It Mean for Idle Space Navy?This section is a direct copy from the Phoenix Aura Discord server. Earlier today, I received information about a significant vulnerability in all versions of Unity since 2017.1. As of now, there's no evidence that this vulnerability has been exploited, but here's what you should know.
changedUnity Vulnerability: What Does It Mean for Idle Space Navy?What is this vulnerability capable of? For certain Unity application types or applications with certain commands run at launch, there is a possibility that an attacker could perform a privilege escalation attack, allowing them to run code with more authority than they otherwise should be able to.
changedUnity Vulnerability: What Does It Mean for Idle Space Navy?Is Idle Space Navy subject to this vulnerability? While none of the command strings specified in the remediation are used in Idle Space Navy , and launching the game through Steam does not appear to result in any warnings or other alerts regarding this vulnerability, Unity reports that all non-patched versions may be vulnerable. Idle Space Navy does not appear to be currently vulnerable, and no known uses of this vulnerability have occurred, but you should exercise caution regardless until a patched version is available.
changedUnity Vulnerability: What Does It Mean for Idle Space Navy?Will you be releasing a patched version?
Idle Space Navy changes
addedLong story short, my ability to release new versions of *Idle Space Navy* got compromised when my computer failed and I had to move to much different hardware. I was not able to get my signing certificate at the time to move onto the new computer, which left me unable to release new code-signed versions of Idle Space Navy - thereby hamstringing the Milestone Program and preventing further releases.
addedGiven that some of the people who were in the original Milestone Program are no longer present in the Phoenix Aura Discord (join if you want to at this link ), I will likely be reopening the Milestone Program to new testers once development resumes. The best place to find out about this will be the Aura Discord, but I will make an announcement here as well.
changedThis section is a direct copy from the Phoenix Aura Discord server. Earlier today, I received information about a significant vulnerability in all versions of Unity since 2017.1. As of now, there's no evidence that this vulnerability has been exploited, but here's what you should know.
changedWhat is this vulnerability capable of? For certain Unity application types or applications with certain commands run at launch, there is a possibility that an attacker could perform a privilege escalation attack, allowing them to run code with more authority than they otherwise should be able to.
changedIs Idle Space Navy subject to this vulnerability? While none of the command strings specified in the remediation are used in Idle Space Navy , and launching the game through Steam does not appear to result in any warnings or other alerts regarding this vulnerability, Unity reports that all non-patched versions may be vulnerable. Idle Space Navy does not appear to be currently vulnerable, and no known uses of this vulnerability have occurred, but you should exercise caution regardless until a patched version is available.
So, quite a lot has happened. I ended up with a computer rebuild that borked things, then in a move, and now there's a Unity issue to talk about. So, let's talk about all of it.
Where's Arynnia?
Long story short, my ability to release new versions of *Idle Space Navy* got compromised when my computer failed and I had to move to much different hardware. I was not able to get my signing certificate at the time to move onto the new computer, which left me unable to release new code-signed versions of Idle Space Navy - thereby hamstringing the Milestone Program and preventing further releases.
I'm now in the middle of a move, but once that's done, things will hopefully stabilize, so we'll see where things can go. I'm hoping to resume development by the end of the year and am targeting version 1.00 for 2027 - I'll update the Early Access information in the coming hours to days.
Will the Milestone Program be reopening?
Given that some of the people who were in the original Milestone Program are no longer present in the Phoenix Aura Discord (join if you want to at this link), I will likely be reopening the Milestone Program to new testers once development resumes. The best place to find out about this will be the Aura Discord, but I will make an announcement here as well.
Unity Vulnerability: What Does It Mean for Idle Space Navy?
This section is a direct copy from the Phoenix Aura Discord server. Earlier today, I received information about a significant vulnerability in all versions of Unity since 2017.1. As of now, there's no evidence that this vulnerability has been exploited, but here's what you should know.
What is this vulnerability capable of? For certain Unity application types or applications with certain commands run at launch, there is a possibility that an attacker could perform a privilege escalation attack, allowing them to run code with more authority than they otherwise should be able to.
Is Idle Space Navy subject to this vulnerability? While none of the command strings specified in the remediation are used in Idle Space Navy, and launching the game through Steam does not appear to result in any warnings or other alerts regarding this vulnerability, Unity reports that all non-patched versions may be vulnerable. Idle Space Navy does not appear to be currently vulnerable, and no known uses of this vulnerability have occurred, but you should exercise caution regardless until a patched version is available.
Will you be releasing a patched version?
YES.
ON WINDOWS: I have found a way that I can issue a patch to ISN versions 0.10.7 and 0.11 MS 2 without having to recompile them completely. I'm not currently able to continue active development on ISN due to financial strain preventing me from renewing my code signing certificate, but a patch has been made available where the UnityPlayer.dll on Windows will be replaced. There will be a micropatch to roll this out no later than tomorrow morning (I'm in the middle of a move, and my build computer is currently torn down for that, but I'll rush it together as best I can.)
ON MAC: Given that Mac application signing is done through the Apple Developer Program, which I have been able to maintain, I will release a recompiled MacOS version of ISN 0.10.7 and 0.11 MS 2 no later than tomorrow morning (see my note above for why the delay).
