2600problems Posted March 29, 2017 Share Posted March 29, 2017 I've decided that the best way to fuck with pirates is to password protect the games that I make. so here's a small snippet of my code: 10 print "are you a pirate" 20 input a$ 30 print "hello, my name is c64..., please give password 40 input a$ 50 if a$= 1000 to 9000 (or brute forced) goto 80 60 if a$= 8145 or 99872 goto 90 70 goto 80 80 (loops) 90 (unlocks computer) what I want to do is separate them into 2 different code batches. 1 to protect any games I make or upload to this site 2. to unlock it if needed. (I trust those I give the password to will not spread it over the internet) currently in alpha stage Quote Link to comment Share on other sites More sharing options...
fujidude Posted March 29, 2017 Share Posted March 29, 2017 I'm (rather atypically) at a loss for words here at this moment. 6 Quote Link to comment Share on other sites More sharing options...
pirx Posted March 29, 2017 Share Posted March 29, 2017 bloody pirates!!! Quote Link to comment Share on other sites More sharing options...
Goochman Posted March 29, 2017 Share Posted March 29, 2017 (edited) Edited March 29, 2017 by Goochman 4 Quote Link to comment Share on other sites More sharing options...
Rybags Posted March 29, 2017 Share Posted March 29, 2017 If the password is in the program it'll be found in no time. If you do fancy encryption it'll take seconds/minutes longer. In the modern day, emulation and debugging means you can't hide much at all. The way to go with a password would be to encrypt most of the program then have the password actually form most of the decryption key. By doing that, it's not discoverable by any other way than actually getting it right. Then again, brute force password hacking is easy with fast modern CPUs. 1 Quote Link to comment Share on other sites More sharing options...
Nukey Shay Posted March 29, 2017 Share Posted March 29, 2017 Exactly who is supposed to be pirating Atari Basic programs these days? 12 Quote Link to comment Share on other sites More sharing options...
Stewart_Pidd Posted March 29, 2017 Share Posted March 29, 2017 Who would have known that my plans for world domination would be thwarted by a password subroutine in basic? 9 Quote Link to comment Share on other sites More sharing options...
zzip Posted March 29, 2017 Share Posted March 29, 2017 I've decided that the best way to fuck with pirates is to password protect the games that I make. so here's a small snippet of my code: 10 print "are you a pirate" 20 input a$ 30 print "hello, my name is c64..., please give password 40 input a$ 50 if a$= 1000 to 9000 (or brute forced) goto 80 60 if a$= 8145 or 99872 goto 90 70 goto 80 80 (loops) 90 (unlocks computer) what I want to do is separate them into 2 different code batches. 1 to protect any games I make or upload to this site 2. to unlock it if needed. (I trust those I give the password to will not spread it over the internet) currently in alpha stage Add these lines for additional protection: 5 print "Please pry off the Break key with a screwdriver before continuing, then press any key to continue" 6 input $a 5 Quote Link to comment Share on other sites More sharing options...
+Stephen Posted March 29, 2017 Share Posted March 29, 2017 I wouldn't worry too much about a strong password generator. It's getting that damn pesky PEEK command in C64 BASIC to work. 1 Quote Link to comment Share on other sites More sharing options...
+MrFish Posted March 29, 2017 Share Posted March 29, 2017 (edited) Excellent, now you're down to only 2,599 problems! Edited March 29, 2017 by MrFish 4 Quote Link to comment Share on other sites More sharing options...
+MrFish Posted March 29, 2017 Share Posted March 29, 2017 5 print "Please pry off the Break key with a screwdriver before continuing, then press any key to continue" 6 input $a Come on man, he's still in the "alpha" stage... 1 Quote Link to comment Share on other sites More sharing options...
tep392 Posted March 29, 2017 Share Posted March 29, 2017 It might help if you add this. 5 REM IGNORE THE NEXT TEN LINES OF CODE. NOTHING TO SEE HERE. 3 Quote Link to comment Share on other sites More sharing options...
+Stephen Posted March 29, 2017 Share Posted March 29, 2017 Perhaps it would be better to distribute the games to trusted individuals, if you get the source printed at Kinkos. 1 Quote Link to comment Share on other sites More sharing options...
+CharlieChaplin Posted March 29, 2017 Share Posted March 29, 2017 Control-3 Error 136 L. 1 Quote Link to comment Share on other sites More sharing options...
2600problems Posted March 29, 2017 Author Share Posted March 29, 2017 great answers, i'm laughing so hard right now 1 Quote Link to comment Share on other sites More sharing options...
2600problems Posted March 29, 2017 Author Share Posted March 29, 2017 I also did this for the BBC micro: 10 print "are you a dick?" 20 input a$ 30 rem yes or no doesn't matter 40 if a$= "yes" goto 50 50 print "shutting down" 60 print "good, shutting down" 2 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted March 30, 2017 Share Posted March 30, 2017 Control-3 Error 136 L. This actually worked for me on a particularly difficult BASIC program. It shall remain nameless because of how I "re-used" some of the code I was able to unprotect. It was a combination of rapid fire hitting break and Ctrl-3 and pressing System Reset here and there, but I finally got a READY prompt. This disk had no DOS, it booted directly to the BASIC program, and all disk I/O was handled by the program. Once I got READY, I had to save it, but no DOS was booted. I had to use C:. What a pain, but it worked. Booted a DOS disk, loaded from C: then saved to D: 1 Quote Link to comment Share on other sites More sharing options...
TMR Posted March 30, 2017 Share Posted March 30, 2017 what I want to do is separate them into 2 different code batches. 1 to protect any games I make or upload to this site 2. to unlock it if needed. (I trust those I give the password to will not spread it over the internet) What stops the pirates from simply viewing the BASIC listing and spotting the password or removing the "protection"? There's nothing you can do as a BASIC programmer to obfuscate your program that a cracker - someone who usually has a lot of "in the field" machine code knowledge - can't undo and even if the program is compiled it doesn't take much picking around for someone with that skillset to find the password. The bigger question that springs to mind though is why would you bother in the first place?! Even something that'd put up a fight from assembly language is pretty pointless because one password leak or weak algorythm later and everything is undone. 1 Quote Link to comment Share on other sites More sharing options...
fujidude Posted March 30, 2017 Share Posted March 30, 2017 Guys.... um let's just indulge the enthusiasm without bothering with the wider scope of it all. I'm pretty sure there's a reason for it all. Quote Link to comment Share on other sites More sharing options...
+Gemintronic Posted March 30, 2017 Share Posted March 30, 2017 Actually, I wouldn't mind having something that I could check to make sure my game is running on actual AtariAge boards. Be it 2600, 5200 or 7800. Quote Link to comment Share on other sites More sharing options...
zzip Posted March 30, 2017 Share Posted March 30, 2017 Guys.... um let's just indulge the enthusiasm without bothering with the wider scope of it all. I'm pretty sure there's a reason for it all. I don't think OP was actually serious, read his followups 1 Quote Link to comment Share on other sites More sharing options...
TMR Posted March 30, 2017 Share Posted March 30, 2017 Guys.... um let's just indulge the enthusiasm without bothering with the wider scope of it all. I'm pretty sure there's a reason for it all. Okay, so who fancies explaining the reason behind "screwing with pirates" then...? Enthusiasm is fantastic, but piling all of that energy into something like this is akin to driving up a cul-de-sac in a rocket-powered car, it's going to end messily... 1 Quote Link to comment Share on other sites More sharing options...
fujidude Posted March 30, 2017 Share Posted March 30, 2017 Okay... I'll just get it over with. The OP has either started a humorous exercise in futility, or he's suffering from some kind of mental affliction. In the 1st case, there's not much fun in pointing out the futility, as that kills the joke/humor. In the second case, it's best not to tear down his grand ideas as he enthusiastically explores programming an Atari 8-bit, less he have some kind of mental episode or psychotic break. 1 Quote Link to comment Share on other sites More sharing options...
TMR Posted March 31, 2017 Share Posted March 31, 2017 The OP has either started a humorous exercise in futility, or he's suffering from some kind of mental affliction. In the 1st case, there's not much fun in pointing out the futility, as that kills the joke/humor. Assuming there was something to kill in the first place... In the second case, it's best not to tear down his grand ideas as he enthusiastically explores programming an Atari 8-bit, less he have some kind of mental episode or psychotic break. If he's losing the plot that's going to happen sooner or later anyway, probably around the time he tries to use players from BASIC. But okay, i won't bother responding to his posts any more because i'm not going to waste time working out if he's being serious or not. Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted March 31, 2017 Share Posted March 31, 2017 It becomes clear why [sarcasm] and [irony] tags are always required on Internet forums. 2 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.