Encrypt says it can be loaded onto a device. If I hack into a device with encrypt am I still able to issue commands to the drone? Can I still spoof a drone running encrypt?

I view it as encrypting the messages, not as a secondary firewall. Another player disagrees.

Anyone know?

Before you can do anything, you have to decrypt first.

So you don't think hacking into the commlink essentially gives you the authority to view encrypted files?

Only if you find a file namend secretcodes.pic

kinda like how one can use a third party program to encrypt files or part of the file system. disconnecting it from the os makes you need the codes, admin or no admin.

hell, set up a encrypted file system in linux and your toast if you loose the key, no matter your access level. same should be for windows realy, alltho i cant say as i have never "tested".

To me when it says that a device can be encrypted, it means that the encrypt program sits at all of the device's comunications ports, filtering all of the device's outputs through the encryption scheme and bouncing any inputs that aren't encrypted in the same scheme, esentially making any attempts to hack into the device itself useless unless you crack the encryption.

As for the other question, can you still spoof a drone if it's using encrypted communications links, you can, you just have to use decrypt to crack the scheme, then make sure your own spoofed commands match the encryption that the device at the other end of the communications link is expecting.

I would say you have to decrypt immediately after you are "in", wouldn't even recognize the icons "inside" otherwise

Personally I think if the user of the commlink doesn't have to decrypt than neither does a hacker who gains user access. IE, all valid users are given the proper authorization code to view the files.

Encrypt should only be for the wireless signal or for files that don't need to be read by just anyone.

My view of running Encrypt on a device/node is that it works like the systems shown in the movie Sneakers. You can connect to it, but even the logon screen itself is scrambled, leaving your Exploit tools no point of reference to begin their attack, until you break the encryption.

Even a legitimate user of the system would need to be able to suppy the proper decryption key to be able to log on.

To throw another movie reference into the mix, take the ending to Lawnmower Man. They trapped Jobe in the system by loading a virus that encrypted all the ports to the outside world (except for that one maintence access backdoor that the virus didn't recognize as a port). While this is the turned-inside-out version of how I view encrypting a device, I still belive it's a good concpetual representation.

The designers went out of the way to state that the three things you can encrypt are files (chunks of data just sitting somewhere), communications links (streaming data moving from one place to another), and devices. The way I see it, the only way that encrypting a device has any meaning is that if to access the device, you have to have some means of decrypting it (either legitimately via passcode, or by breaking it using the decrypt program).

I look at devices as in all the communicatiosn from a certain device are encrypted. The only thing that backs up the extra level of security is the "and devices" phrase. It's not listed under breaking in or spoofing or anything else.

I just read the decrypt again and it says to decrypt you need to spend a simple action if you have the code or use the decrpyt program if you don't.

So if they have an encrypted commlink and are sending messages to the drone wouldn't the drone have to spend a simple action every time to read the message?

Or maybe you encrypt you commlink when you turn it off and decrypt it when you turn it on, IE it's decrypted while running it and that's why it's not mentioned in the breaking in section.

Its that second one, lord ben. Apon first making connection to the device, you have to either decrypt it or supply the code. Once the code is supplied, then you don't have to decrypt any more, as all new data coming in goes through the code to come out decrypted.

Seriously, as the rules are written, it is the device you encrypt, not it's incoming and outgoing signals. Yes, they are encrypted too, but Ecrypt does indeed act as a second firewall. This is what everyone is telling you, and the other view, while Maybe more in line with how things really work (I wouldn't know), is not how the rules are written.

If you encrypt a connection, as long as it is established, it is encrypted - decryption would only matter when trying to listen to it.

If you encrypt a file or a device, every time it is accessed it must be decrypted.

I think that they are using the term device in the UNIX sense of the term: an external device or something that the OS treats like one. So you can encrypt a security camera, or a network link (wireless or not), but you can't encrypt an entire node.