Posted: Tue Dec 30, 2008 4:28 pm
I searched and found nothing, and I tried changing the "mainbkgnd2.png" file but when I do alleg says it has an invalid signature and asks me if I want to repair it.
Space battles since 2000
https://www.freeallegiance.org/forums/
So people, how log in after >>years<<, get the correct background screen.Andon wrote:QUOTE (Andon @ Dec 30 2008, 09:12 PM) Why is that?
"IT'S YOU!"Dark_Sponge wrote:QUOTE (Dark_Sponge @ Dec 31 2008, 07:26 AM) "MAIN SCREEN TURN ON"
I bitched at TE a while ago to get it up-protected, along with a load of other stuff.Dogbones wrote:QUOTE (Dogbones @ Dec 30 2008, 07:59 PM) Yep it is one of the files ASGS looks at and protects from being changed.
And there in lies the problem I think...madpeople wrote:QUOTE (madpeople @ Jan 1 2009, 11:19 AM) I bitched at TE a while ago to get it up-protected, along with a load of other stuff.
well, i say bitched.. it was more frindly really, perhaps pestered? I could just say asked, either way, i communicated an interes in getting the random files unlocked.Dogbones wrote:QUOTE (Dogbones @ Jan 2 2009, 04:58 PM) And there in lies the problem I think...
but to delve into my pm inbox....pkk wrote:QUOTE (pkk @ Dec 30 2008, 11:56 PM) So people, how log in after >>years<<, get the correct background screen.
Only TE knows why that many files are ASGS protected (like zoomcore, GoDII04, ...).![]()
TE wrote:Forget security - that's not the reason why they can't be modified.me wrote:just wondering why there is a load of R4 related artwork protected by ASGS
there are things like the image in the background when allegiance starts and introscreen.mdl that are protected.
i'm just wondering why? its not like they are security critical things, it just seems strange to prevent people from changing things which have no effect on security?
is there any reason they (and other non-security related things as those two were just some examples i've come across) can't be un-blocked? and could we not block similar things in future plz?
--mp
Those files were modified in R4 and are different from the older R2 files. When deploying the update to R4, ASGS looks at all of the updated files (including introscreen.mdl) and if there are any files on your system that do not match the newest ones on the server, they'll be downloaded and overwritten.
What you're seeing is the AU system, not a security feature - although the two technically are one and the same.
As far as "blocking", removing those files from AU will prevent any user with an R3 or earlier Allegiance from updating to the newest R4 build. They'll end up with an Allegiance.exe that crashes on launch, and will be required to uninstall, redownload the full installer, and do a fresh install.
So no. They won't be unblocked until they need to be, which will likely be when R5 is deployed (providing R5 doesn't change those files themselves, in which case they'll continue to be checked/updated on every login)
Why do you need to play Allegiance on the community servers with a modified introscreen.mdl anyways?
--TE