Custom ROM via crafting
#41
Posted 27 June 2014 - 07:51 AM
2. Use trusted procedure, you wrote in ROM, to change "_flash_" content.
3. Do you need more?
#42
Posted 29 June 2014 - 08:11 PM
One of the reasons I think this is such a good idea is because, currently, computercraft is very limited as to what it can do--the user is at the ROM's mercy. Letting the user make their own ROM would be a revolutionary thing for CC. It would remove most of the limitations that occur due to the way CC is. This is also the reason, I think, it's not been implemented. I feel that the last thing dan200 wants to do is to give the user complete and total freedom. Maybe I'm wrong; but if I'm right this is unlikely to be implemented. Either way I still support it as I've said earlier.
Edited by Geforce Fan, 29 June 2014 - 08:15 PM.
#43
Posted 29 June 2014 - 08:48 PM
Geforce Fan, on 29 June 2014 - 08:11 PM, said:
I think Dan200 want CC to be fool proof as much as it possible. But that is why this suggestion is so good: No user commands can break bios. Only implicit crafting only in player's hands would change rom. And you have the same way to return all to default state (craft with empty disk).
#44
Posted 19 July 2014 - 12:44 AM
Sebra, on 29 June 2014 - 08:48 PM, said:
Geforce Fan, on 29 June 2014 - 08:11 PM, said:
I think Dan200 want CC to be fool proof as much as it possible. But that is why this suggestion is so good: No user commands can break bios. Only implicit crafting only in player's hands would change rom. And you have the same way to return all to default state (craft with empty disk).
#45
Posted 19 July 2014 - 01:32 AM
cptdeath58, on 19 July 2014 - 12:44 AM, said:
Sebra, on 29 June 2014 - 08:48 PM, said:
Geforce Fan, on 29 June 2014 - 08:11 PM, said:
I think Dan200 want CC to be fool proof as much as it possible. But that is why this suggestion is so good: No user commands can break bios. Only implicit crafting only in player's hands would change rom. And you have the same way to return all to default state (craft with empty disk).
Everything can be cracked, when given enough time.
#47
Posted 19 July 2014 - 09:48 PM
Sebra, on 19 July 2014 - 04:13 AM, said:
About the ROM being a limit, I don't think that's true. A computer has its space limited, and the ROM doesn't... If you top level override, you could gain access like if there was nothing in the ROM, you would build your ROM yourself. It's not easily made, but with sandboxes and the top level override, you would pass the original ROM with the cost of the space in the computer.. That would be easily changed if you had a disk drive with a disk acting as a ROM or if you merged internal storage with the disk.
Oh god.. I wrote soo much. I hope someone does great use from it
#48
Posted 20 July 2014 - 04:44 AM
logsys, on 19 July 2014 - 09:48 PM, said:
Sebra, on 19 July 2014 - 04:13 AM, said:
About the ROM being a limit, I don't think that's true. A computer has its space limited, and the ROM doesn't... If you top level override, you could gain access like if there was nothing in the ROM, you would build your ROM yourself. It's not easily made, but with sandboxes and the top level override, you would pass the original ROM with the cost of the space in the computer.. That would be easily changed if you had a disk drive with a disk acting as a ROM or if you merged internal storage with the disk.
Oh god.. I wrote soo much. I hope someone does great use from it
Few things: 1. this idea is the best idea ever and should be at the top of the list of the CC features to be implemented. 2. you CAN get above CraftOS with a little bit of lua "magic" (its really simple actually). 3. you are wrong.
Not to be a jerk, but i'm guessing your not a programmer? Java?
Trust me, you will not be able to "crack" anything from within CC even with a custom ROM. I promise, with standard CC, you wont get out of the CC sandbox or anything like that.
However, because I am intrigued, I will take a minute and look into this further. It is an interesting topic (also relates to my OS development). But I can guarantee I wont be able to figure out anything...
there are things that cannot be cracked. Now, a watch or calculator could be... potentially. But it would require hardware hacking.
In CC though, even in the BIOS, we are VERY limited. There isn't really a whole lot that can be done in the BIOS... except for the string metatable thing but.. thats pretty much it.
If you ask me, CC and trusted code = joke. CraftOS actually... my OS may be a different story, but that's still being worked on.
Wow, I wrote a lot too...........
Geforce Fan, on 06 June 2014 - 04:00 AM, said:
To be honest, this is a very sense-making suggestion. Like he said, you make the computer, shouldn't you be able to control how it runs?
Another thing is that this could be used to protect your program so that they cannot be modified or deleted.
This can be done EXCEPT... startup disks ruin it.
I have this is my OS, a very secure system... but startup disks make it a joke.
#49
Posted 22 July 2014 - 08:31 PM
Quote
I have this is my OS, a very secure system... but startup disks make it a joke.
#50
Posted 24 July 2014 - 03:53 PM
With real i mean IN GAME attacks
Edited by Tatjam, 24 July 2014 - 03:54 PM.
#51
Posted 07 August 2014 - 01:23 AM
ROFLCopter64bit, on 25 June 2014 - 12:05 PM, said:
It would make programs like this easier to implement, as giving a bootloader direct access to the raw startup and autorun script and change it as need be (Maybe even bios.lua, but it's a last resort ) would make life much easier than relying that the user renamed /startup on their disk to /grubstartup.
The arguments would be a one-time password that the computer gives the user only once, which changes everytime you flash the ROM.
Or maybe, you can only flash it once (or a preset value) like in the OP.
If the user forgets this password, (if it's not one-time only) the user can flash back to default ROM (but other people might use this to exploit holes).
Either way, a method that gives trusted software access to flash the ROM when they really need it would be great.
Edited by Rectar2, 07 August 2014 - 01:24 AM.
#52
Posted 07 August 2014 - 01:26 AM
Rectar2, on 07 August 2014 - 01:23 AM, said:
#53
Posted 08 August 2014 - 05:26 PM
#55
Posted 13 August 2014 - 06:08 AM
#56
Posted 13 August 2014 - 08:57 PM
#57
Posted 25 August 2014 - 06:20 AM
#58
Posted 25 August 2014 - 03:36 PM
#59
Posted 28 August 2014 - 08:03 PM
Either way, I may just brew up my own custom ROM for the cc.jar that makes this possible for myself...
We'll see. Obviously it wouldn't really the the same thing but.. meh.
ADD THIS!! Seriously!!
#60
Posted 28 August 2014 - 10:16 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users