[Rascal]

In the last session my group encountered a problem. We had a program that needed uploading to a safe server, but the program was stuck in the headware of our Face who has no hacking skills whatsoever. The program was impossible to transfer to anything but the safe server, so our Hacker could not just take it herself.
In the end we figured out something of a custom move with the Face "slaving" his internal commlink to the Hacker´s dito, piggybacking on her and slipping through the system as it unlocked under her programs. What does the rules tell us about situations like this? Can it be done? Should there be dice penalties?
I mean, if we ever try this again it could be nice to do it according to rules...

[Bradd]

In situations like this, your hacker should get an admin account, create or steal an account for the face to use, and let the face log in normally. The hacker's job is to clear a path, making sure that everything is safe for the face to log in, access files, and so on. There's no need to slave anything.

[raggedhalo]

Slaving the face's commlink to the hacker's, so that it effectively becomes external storage, is perfectly fine by the rules.  As Bradd says, though, getting the hacker to create an admin account for the face is a good solution too.

[hobgoblin]

Well a program stuck in a specific memory device, and only transferable to another sounds like something outside of the rules from the get go...

[Rascal]

Heh, you might be right there, hobgoblin.

Thanks for the advice, Brad and raggedhalo!