Search results

  1. SX

    Beats of Rage Anniversary

    Honestly I just needed to pick a name and I'm terrible at naming stuff. But it was easy to remember and kind of rolled off the tongue. I still have the domain registered.... lol
  2. SX

    OpenBOR 4.0

    Agree. If back in 2005.... had I been well versed in cryptography I would have done it differently.... using certificates solves this issue and the pak file itself would be entirely encrypted and no change to the structure would be necessary.
  3. SX

    OpenBOR 4.0

    the two file formats would have to co-exist to not break backward compatibility. If I'm not mistake the signature of the file is located right in the beginning and so you could utilize function pointers to reassign the file loading behavior once the magic key has been identified. That's what I...
  4. SX

    OpenBOR 4.0

    hahaha... well like you said it was secure for years but like anything else it can be broken. Really this would require a closed source solution on the engine side and utilize asynchronous cryptography and a new packing structure since there are many of those who are familiar with how the PAK...
  5. SX

    OpenBOR 4.0

    That's what it did originally.... but unless you employ an asynchronous encryption model (Public [read]/Private [write] Keys) it can always be hacked. Asynchronous encryption is the only REAL solution to ensure integrity and have the responsibilities fall under the creator. From a technical...
  6. SX

    OpenBOR 4.0

    LOL.... Fair enough... I guess I never shared the code because I didn't want anyone to compromise future PAKS... Then I guess the answer to that question is NO... OpenBOR has not have plans for locking down PAKS. However, you could still provide a service where you can sell that source code...
  7. SX

    OpenBOR 4.0

    @DCurrent This sounds a lot like SecurePAK. Back in the day we had this functionality baked into limited runs when a OpenBOR creator wanted to lock down their resources because they either had heavily modified artwork or created artwork from scratch and did not want others to manipulate the...
  8. SX

    OpenBOR on MAC

    Im sorry but I don’t have the schedule or the desire to do the iOS port.  I was bored at work and figured I could provide some insight to why the OS X version didn’t compile.  I will leave it to others to maintain it if they choose to.
  9. SX

    OpenBOR on MAC

    About 6 years ago I had ported the code to run on iOS and if I remember correctly it took less than a week (spare time).  There weren't that many changes and the engine was running well.  The engine utilizes SDL on Linux/Win/OSX and SDL is also available for iOS as static libraries.  The only...
  10. SX

    OpenBOR on MAC

    The following changes are necessary in order to build openbor.  Note that MacPorts does not have libsd2_gfx, thus you will need to build this on your end and place the includes and libs in their respective /opt/local/**** Also... I had to disable -Werror as there are a few warnings being...
  11. SX

    OpenBOR on MAC

    Will do..... this may take a couple of days based on my schedule but I will look into it.
  12. SX

    OpenBOR on MAC

    If people are still interested I can try and build the code tomorrow and see what happens.
  13. SX

    10 years later...

    I just realized today.... it was 10 years ago when I was introduced to the world of beats of rage.  Greetings everyone!
  14. SX

    Time to Move on?

    Sorry DC.  You now have Admin privileges on the SourceForge Openbor Project. As for your thoughts on moving forward with the engine's core.  I whole heartedly agree that anything new should be done using well known design patterns (Request Factories (Entity Generation), Abstract Interfaces (Low...
Back
Top Bottom