This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
DRoleplaysBG's profile picture

How to block monitors, printers and disk drives from working on a specific RedNet cable?

Started by DRoleplaysBG, 21 March 2018 - 05:42 PM
DRoleplaysBG #1
Posted 21 March 2018 - 06:42 PM
So I've got a rednet network used, well, mostly like the internet, however I want to block my users from using monitors, printers and disk drives for security reasons (obvious). How would I go around to do that?
KingofGamesYami #2
Posted 21 March 2018 - 07:20 PM
You can't.
Wilma456 #3
Posted 21 March 2018 - 07:40 PM
You need to overwrtite the peripheral API
Lupus590 #4
Posted 21 March 2018 - 07:52 PM
Firewall computers? Have a computer which separates parts of your network and filters traffic between the two parts. (Your firewall computers will need to proxy the peripherals)

Or

Have private peripherals on a separate network.
Edited on 21 March 2018 - 06:53 PM
Dog #5
Posted 21 March 2018 - 07:55 PM
The only solutions that come to mind aren't exactly elegant. You could place a computer at each peripheral as a go between that would handle authorization, or you could break your network into 'subnets' and have a computer manage authorization to the peripheral 'subnet'.

Being that your network is already established, I have a feeling the second idea isn't an option at this point.

EDIT: :ph34r:/> 'd
Edited on 21 March 2018 - 06:56 PM
Bomb Bloke #6
Posted 22 March 2018 - 03:02 AM
If you want to block certain systems from ALL peripherals, then your answer would be to only give those systems wireless modems. Hook up a go-between computer with both a wired and wireless connection, and then just have it run the repeat script on startup. Bonus points if you can give it an Ender modem, as that'll effectively give all other regular wireless modems unlimited range.

If you want to block certain systems from just SOME peripherals, then it gets dramatically more complicated. To do it with your current run of cabling, you'd need to write a wrapper for the peripheral API with a whole lot of "security" code baked into it - unless you're already familiar with encryption, it'd be a very steep learning curve.

Given that network cabling is so cheap, you might be better off making two separate cabling runs to "authorised" systems (one with computers, one with peripherals), and a single "computer only" run to "unauthorised" systems.