My idea is that user would be able to choose what to boot first, for example command in shell: "bootpriority computer" or "bootpriority disk", it would store it like labels are, when talking about labels if computer doesn't have label then bootpriority setting would be wiped after breaking the computer(like all the files).
This is a read-only snapshot of the ComputerCraft forums,
taken in April 2020.
Limit disk boot at startup
Started by GreenByteSoftware, 17 May 2014 - 03:53 PMPosted 17 May 2014 - 05:53 PM
This is about that now anyone can go around computer's inside startup program, by creating the startup file in disk and then put to the computer what for example has password protection.
My idea is that user would be able to choose what to boot first, for example command in shell: "bootpriority computer" or "bootpriority disk", it would store it like labels are, when talking about labels if computer doesn't have label then bootpriority setting would be wiped after breaking the computer(like all the files).
My idea is that user would be able to choose what to boot first, for example command in shell: "bootpriority computer" or "bootpriority disk", it would store it like labels are, when talking about labels if computer doesn't have label then bootpriority setting would be wiped after breaking the computer(like all the files).
Edited on 24 May 2014 - 05:28 PM
Posted 17 May 2014 - 06:17 PM
Oh crap! I disabled CTRL-T on startup, and now I can't use my boot disk to get back into the computer, on multiplayer!
Edit: :P/>
Edit: :P/>
Edited on 17 May 2014 - 04:17 PM
Posted 17 May 2014 - 06:25 PM
Well, by default it would still be able to boot from disk, and while in shell it would be able to changeOh crap! I disabled CTRL-T on startup, and now I can't use my boot disk to get back into the computer, on multiplayer!
Edit: :P/>
Edited on 17 May 2014 - 04:27 PM
Posted 17 May 2014 - 06:27 PM
- snip snap -
Yes, but what if you had a program running in a loop?
Posted 17 May 2014 - 06:41 PM
This would be your problem, you can always add password in startup file, then setup bootpriority to computer and after that you could run any program, you could be smart enough to create terminatable part if you want to boot something after startup without writing in shell and if it is your looped program you could terminate the process before entering loop program.- snip snap -
Yes, but what if you had a program running in a loop?
Edited on 17 May 2014 - 04:42 PM
Posted 18 May 2014 - 06:44 AM
1.Take responsibility for your actions.Oh crap! I disabled CTRL-T on startup, and now I can't use my boot disk to get back into the computer, on multiplayer!
2.Do not change boot sequence if you do not want it.
3.Make yourself new computer.
Posted 18 May 2014 - 08:59 AM
This can easily be acheived by editing the rom startup file, but you'd need access to the server files to do that. I would indeed like to be able to disable this from in game.
Posted 18 May 2014 - 10:01 AM
Yes, but if there would be an option for an individual user who doesn't have any access to server files. It would be loaded in like labels are - from specific for example "bootpriority.dat" file.This can easily be acheived by editing the rom startup file, but you'd need access to the server files to do that. I would indeed like to be able to disable this from in game.
Posted 18 May 2014 - 12:32 PM
While i get what you are coming from i personally don't like any system that would allow end user to brick up their computers. Why you ask? While i get that if user was messing up with it and bricked it up ok his fault. But you have to take into consideration the malicious user. There are people who would brick all computers they can get to and laugh.
Posted 18 May 2014 - 05:10 PM
Well, crafting a new computer need really small amount of stuff, the user should be smart enough to protect his pc in couple ways: 1st option - setup password at startup first and after that change the bootpriority, 2nd option - hide the computer, 3rd option - probably easiest if you were soooo stupid to don't put password(or don't know how to program), change bootpriority and it has some important files is to set label and put it to inventory. Anyways, protection always can brick the system, the user fault is to forget putting some software protection to protect from trols who can brick users' systemsWhile i get what you are coming from i personally don't like any system that would allow end user to brick up their computers. Why you ask? While i get that if user was messing up with it and bricked it up ok his fault. But you have to take into consideration the malicious user. There are people who would brick all computers they can get to and laugh.
Posted 18 May 2014 - 07:24 PM
"Dangit, someone hacked my computer, changed the startup program to a virus, then turned off the ability to boot from a floppy!"
if you remove the ability to boot from a floppy, you're going to need to add a way to access a computer's storage remotely. Like, take out the HDD
if you remove the ability to boot from a floppy, you're going to need to add a way to access a computer's storage remotely. Like, take out the HDD
Edited on 18 May 2014 - 05:25 PM
Posted 18 May 2014 - 08:27 PM
Now they can break instead. Is it any better?There are people who would brick all computers they can get to and laugh.
Posted 19 May 2014 - 12:21 AM
shell.run("bootpriority computer")
print("You have been hacked!")
os.pullEvent = os.pullEventRaw
sleep(2^32)
os.reboot()
Edited on 18 May 2014 - 10:22 PM
Posted 19 May 2014 - 02:31 AM
I see where you're coming from, and I definitely do not agree. If you're really concerned about it place your disk drive on the top of the computer (and hide it), its the first place the bios checks. This means your disk will take priority over any others and your startup will run, not others.
Posted 19 May 2014 - 02:55 PM
Computer is cheap, information is important.Delete all files and computer is almost a brick.shell.run("bootpriority computer") print("You have been hacked!") os.pullEvent = os.pullEventRaw sleep(2^32) os.reboot()
Nothing can protect computer from malicious bomber, this suggestion ask for information protection.
No external means would protect computer from loosing info except complete isolation.
Posted 19 May 2014 - 03:58 PM
Block protection would protect the computer. And i have to ask, wtf do you people keep on your cc computers that is so important?Computer is cheap, information is important.Delete all files and computer is almost a brick.
Nothing can protect computer from malicious bomber, this suggestion ask for information protection.
No external means would protect computer from loosing info except complete isolation.
Posted 19 May 2014 - 07:09 PM
For me, nothing. It all sits in my Google Drive and gets copied over automatically. Other people, well, I have no idea…
Posted 20 May 2014 - 11:40 AM
Wow, I didn't think that there will be similar amount of people on both sides…
Posted 24 May 2014 - 06:31 AM
Actually what is better?
1. Anyone can get in to your computer, read files then delete them
2. Bootpriority option which if you have a strong password program enabled at pc startup and you have a small chance to get computer bricked unless you keep it turned on.
1. Anyone can get in to your computer, read files then delete them
2. Bootpriority option which if you have a strong password program enabled at pc startup and you have a small chance to get computer bricked unless you keep it turned on.
Edited on 24 May 2014 - 04:31 AM
Posted 24 May 2014 - 01:08 PM
Actually what is better?
1. Anyone can get in to your computer, read files then delete them
2. Bootpriority option which if you have a strong password program enabled at pc startup and you have a small chance to get computer bricked unless you keep it turned on.
Well, the way you phrased number 1, you're trying to make it sound like it's the worst option here, when in reality it might not be.
Let's rephrase these options so that they aren't so biased.
1. No bootpriority
2. Yes bootpriority
Now let's look at number 1 first. Number 1 is what we have right now, regular CC. The most we can really do (without encrypting all of our files), is create some sort of login system to prevent "evil doers" from getting our files. Sadly, all they have to do is just put a disk into our drive, and our computer is "hacked". Not good.
Now let's look at number 2. If CC had bootpriority, then we could just set bootpriority to our computer, then people wouldn't be able to "hack" our computers using floppys! Yay! But wait, what if somehow, your login system had a bug? A bug that allowed the evil doer to get to the shell? Or what if
shell.run("bootpriority computer") print("You have been hacked!") os.pullEvent = os.pullEventRaw sleep(2^32) os.reboot()
Now our computer, with all of our important files, has not only lost them to the hacker, but has also bricked itself in the process. Let's just use a floppy to get the virus off of my compute… Oh…
Now if you have made sure that your login system is completely secure, good for you, but that doesn't mean everyone else has.
I believe it should be easier to compare this suggestion to old CC with these 2 scenarios.
Edited on 24 May 2014 - 11:09 AM
Posted 24 May 2014 - 02:39 PM
1. You have no chance to protect your data and no chance to brick your comp.
2. You have chance to protect your data and can brick your comp beyond repair.
It seems second scenario still better.
2. You have chance to protect your data and can brick your comp beyond repair.
It seems second scenario still better.
Posted 24 May 2014 - 03:35 PM
Idea:, when a computer is placed and opened by the first time, craftOS would ask for a password which would be saves somewhere in ROM(like sending a request to store). When changing physical stuff(still inside computercraft, not real life) , it would require a password. That password should match with the previously set in first boot. That way, a virus couldn't change boot priority and change labels e.g.. But as always, staff should consider all options before changing computercraft working method
Posted 24 May 2014 - 03:59 PM
Yes, exactly! I will finish my "BIOS Settings" concept and put in this topic link, entering setup would require password and booting to shell would require password, with setup you could clear startup program and other stuff(going to do this in upcoming few days)Idea:, when a computer is placed and opened by the first time, craftOS would ask for a password which would be saves somewhere in ROM(like sending a request to store). When changing physical stuff(still inside computercraft, not real life) , it would require a password. That password should match with the previously set in first boot. That way, a virus couldn't change boot priority and change labels e.g.. But as always, staff should consider all options before changing computercraft working method
Posted 24 May 2014 - 04:38 PM
I really support this idea, also if it would include BIOS Setup about which TheDiamondGames said, it would be perfect
Posted 24 May 2014 - 06:52 PM
take the I love it and the i hate it off the poll, it confuses everybody and messes with the voting
Posted 24 May 2014 - 07:29 PM
Just took it outtake the I love it and the i hate it off the poll, it confuses everybody and messes with the voting
Posted 24 May 2014 - 08:19 PM
Too complicated imho.…entering setup would require password and booting to shell would require password, with setup you could clear startup program and other stuff(going to do this in upcoming few days)
Custom ROM via crafting is better.
Edited on 24 May 2014 - 06:20 PM
Posted 30 May 2014 - 07:30 PM
But still more people want it and don't care compared to who doesn't want it
Posted 30 May 2014 - 08:02 PM
Just because people want something doesn't mean it will happen. I'm sure a lot of people would love to get two thousand dollars from their government for nothing, but that doesn't mean the government will do that.But still more people want it and don't care compared to who doesn't want it
Posted 30 May 2014 - 08:41 PM
Gotta agree with Sebra, i would love custom ROM crafting. It's not really any of us' call though. It all comes down to wether Dan wants it or not.
Posted 01 June 2014 - 01:50 AM
Also if you wanted to disable copying quickly you just do
Edit copy
Some random stuff
This should then bring up an error message every time you attempt to copy a file over and you can do the same for edit edit
Edit copy
Some random stuff
This should then bring up an error message every time you attempt to copy a file over and you can do the same for edit edit
Edited on 31 May 2014 - 11:51 PM