• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

Anti-hijack program

  • Thread starter Thread starter The Shaman
  • Start date Start date
Originally posted by Gadrin:
I was just trying to figure out the other day how a x-boat might take e-messages and store them, since they're likely to be in all sorts of shapes and forms.

Does the x-boat service encrypt messages they carry (that may already be encrypted) or just store them out in the open ?
Given the transmission-based bandwidth limitations compared to normal, physical Mail service, Xmail is probably already encrypted by the end users for privacy using an algorithm which incidentally compresses it about as far as practicable. The Xmail protocol itself is probably no more operationally complex than SMTP (since the Xnet can be considered to be just a large packet-routing data network), although you're going to want some mailserver authentication at uptake and each hand-off; to avoid Xspam, if nothing else... fortunately, there aren't going to be any "open relays" on the Xboat system.
 
Originally posted by Gadrin:
I was just trying to figure out the other day how a x-boat might take e-messages and store them, since they're likely to be in all sorts of shapes and forms.

Does the x-boat service encrypt messages they carry (that may already be encrypted) or just store them out in the open ?
Given the transmission-based bandwidth limitations compared to normal, physical Mail service, Xmail is probably already encrypted by the end users for privacy using an algorithm which incidentally compresses it about as far as practicable. The Xmail protocol itself is probably no more operationally complex than SMTP (since the Xnet can be considered to be just a large packet-routing data network), although you're going to want some mailserver authentication at uptake and each hand-off; to avoid Xspam, if nothing else... fortunately, there aren't going to be any "open relays" on the Xboat system.
 
Originally posted by boomslang:
fortunately, there aren't going to be any "open relays" on the Xboat system.
meaning ?

I suppose it's all laser com or meson com beams of information.

I think GT mentions them carrying 150 TB of data, which seems ridiculously low for something moving across several worlds, granted, some of it is going to be removed and replaced at each stop.

maybe it's just me.
 
Originally posted by boomslang:
fortunately, there aren't going to be any "open relays" on the Xboat system.
meaning ?

I suppose it's all laser com or meson com beams of information.

I think GT mentions them carrying 150 TB of data, which seems ridiculously low for something moving across several worlds, granted, some of it is going to be removed and replaced at each stop.

maybe it's just me.
 
Originally posted by Gadrin:
</font><blockquote>quote:</font><hr />Originally posted by boomslang:
fortunately, there aren't going to be any "open relays" on the Xboat system.
meaning ?
</font>[/QUOTE]Meaning that messages will only enter the system through controlled gateways (the uplink/downlink nodes of the Xboat Stations), not any old home computer with a wireless antenna or a satellite dish. This, combined with a metered rate based on data size and distance posted, means there will be no Xspam, since even spoofed messages will be traceable eventually. Then you send in the IN.
 
Originally posted by Gadrin:
</font><blockquote>quote:</font><hr />Originally posted by boomslang:
fortunately, there aren't going to be any "open relays" on the Xboat system.
meaning ?
</font>[/QUOTE]Meaning that messages will only enter the system through controlled gateways (the uplink/downlink nodes of the Xboat Stations), not any old home computer with a wireless antenna or a satellite dish. This, combined with a metered rate based on data size and distance posted, means there will be no Xspam, since even spoofed messages will be traceable eventually. Then you send in the IN.
 
Originally posted by boomslang:


Meaning that messages will only enter the system through controlled gateways (the uplink/downlink nodes of the Xboat Stations), not any old home computer with a wireless antenna or a satellite dish. This, combined with a metered rate based on data size and distance posted, means there will be no Xspam, since even spoofed messages will be traceable eventually. Then you send in the IN.

ah, excellent! common ground at last.

I think you're right, by the time it gets to the x-boat gateway, the onus is on the poster/sender to encrypt.

The only burden on the x-boat system might be some sort of compression (after the charge natch ;) )
 
Originally posted by boomslang:


Meaning that messages will only enter the system through controlled gateways (the uplink/downlink nodes of the Xboat Stations), not any old home computer with a wireless antenna or a satellite dish. This, combined with a metered rate based on data size and distance posted, means there will be no Xspam, since even spoofed messages will be traceable eventually. Then you send in the IN.

ah, excellent! common ground at last.

I think you're right, by the time it gets to the x-boat gateway, the onus is on the poster/sender to encrypt.

The only burden on the x-boat system might be some sort of compression (after the charge natch ;) )
 
I used the anti-hijack program to lock down decks, hatches, systems in case of attack either from within the ship or by a boarding party, & activate defense measures against non-ship personnel parties (mess with grav plates, electric shock, security weapons, traps).
In a related subject, I created what I called for lack of a better term: 'reactive firewalls' for the computer systems-firewall that besides blocking attacks against the computer attack back with either energy feedback, viral attack or both.
 
I used the anti-hijack program to lock down decks, hatches, systems in case of attack either from within the ship or by a boarding party, & activate defense measures against non-ship personnel parties (mess with grav plates, electric shock, security weapons, traps).
In a related subject, I created what I called for lack of a better term: 'reactive firewalls' for the computer systems-firewall that besides blocking attacks against the computer attack back with either energy feedback, viral attack or both.
 
Originally posted by Manax Darkhstarr:
I used the anti-hijack program to lock down decks, hatches, systems in case of attack either from within the ship or by a boarding party, & activate defense measures against non-ship personnel parties (mess with grav plates, electric shock, security weapons, traps).
And, to get this thread pushed into a more interesting direction...

How is it you actually implement the anti-hijack program?

Say a passenger in their stateroom pulls out some custom-built hacking equipment secreted withing their luggage. They hook it up to the terminal in the stateroom, and attempt to get past the firewalls (from your definition) or the filters (from the SOM).

How would you, as a GM, handle that?

Is it a task roll for the hacker? If so, what?

Is it a detection roll for the anti-hijack program...or for whomever is on bridge duty?

Maybe an opposed roll?

In general, how to people dice (or not dice) for computer hijacking attempts in their Trav games?
 
Originally posted by Manax Darkhstarr:
I used the anti-hijack program to lock down decks, hatches, systems in case of attack either from within the ship or by a boarding party, & activate defense measures against non-ship personnel parties (mess with grav plates, electric shock, security weapons, traps).
And, to get this thread pushed into a more interesting direction...

How is it you actually implement the anti-hijack program?

Say a passenger in their stateroom pulls out some custom-built hacking equipment secreted withing their luggage. They hook it up to the terminal in the stateroom, and attempt to get past the firewalls (from your definition) or the filters (from the SOM).

How would you, as a GM, handle that?

Is it a task roll for the hacker? If so, what?

Is it a detection roll for the anti-hijack program...or for whomever is on bridge duty?

Maybe an opposed roll?

In general, how to people dice (or not dice) for computer hijacking attempts in their Trav games?
 
Say a passenger in their stateroom pulls out some custom-built hacking equipment secreted withing their luggage. They hook it up to the terminal in the stateroom, and attempt to get past the firewalls (from your definition) or the filters (from the SOM).

How would you, as a GM, handle that?

Is it a task roll for the hacker? If so, what?

Is it a detection roll for the anti-hijack program...or for whomever is on bridge duty?

Maybe an opposed roll?

In general, how to people dice (or not dice) for computer hijacking attempts in their Trav games?
For me, it depends on how central the event is to the plot. If it is relatively unimportant I'd go with an opposed roll of some sort, but if it is a major role-playing event, then - Sacrilege Warning, Canonists stop reading now! - I'd dig out my Shadowrun books and role-play the infiltration attempt. :D
 
Say a passenger in their stateroom pulls out some custom-built hacking equipment secreted withing their luggage. They hook it up to the terminal in the stateroom, and attempt to get past the firewalls (from your definition) or the filters (from the SOM).

How would you, as a GM, handle that?

Is it a task roll for the hacker? If so, what?

Is it a detection roll for the anti-hijack program...or for whomever is on bridge duty?

Maybe an opposed roll?

In general, how to people dice (or not dice) for computer hijacking attempts in their Trav games?
For me, it depends on how central the event is to the plot. If it is relatively unimportant I'd go with an opposed roll of some sort, but if it is a major role-playing event, then - Sacrilege Warning, Canonists stop reading now! - I'd dig out my Shadowrun books and role-play the infiltration attempt. :D
 
Originally posted by Gadrin:
looks like we're going round in circles as Naasirka or whoever you bought your computer from is likely to have anti-hack updates as well.
The potential lag time between when Naassirka identifies a threat, develops a patch, and distributes it across a subsector, or a sector, or the whole Imperium and points beyond, will mean a lot of ships are facing potential failure of their A-H program in the interim (which again explains the roll to bypass the program).

It's not like a subscription to Norton Anti-Virus! ;)
Originally posted by Supplement Four:
How is it you actually implement the anti-hijack program?
In order to access the ship's computer in my games, one needs to either gain access to a terminal in engineering or on the bridge, get hold of the captain's hand computer, or splice into the computer cabling directly and connect through a hand computer the hijacker brings aboard - Computer skill provides a beneficial modifier, and if the attempt to hack the program succeeds, then the crew may attempt to create a patch for the A-H program.

Typically any attempt to hack a program is modified by the difference between the hacker's skill level and the skill level used to create the program - if the hacker has Comp-2, and the program was created by someone with Comp-3, then a -1 modifier applies. I don't typically use opposed rolls between programmers except where a specific sort of cyberspace environment exists - I'm playing Traveller, not Shadowrun! ;)
 
Originally posted by Gadrin:
looks like we're going round in circles as Naasirka or whoever you bought your computer from is likely to have anti-hack updates as well.
The potential lag time between when Naassirka identifies a threat, develops a patch, and distributes it across a subsector, or a sector, or the whole Imperium and points beyond, will mean a lot of ships are facing potential failure of their A-H program in the interim (which again explains the roll to bypass the program).

It's not like a subscription to Norton Anti-Virus! ;)
Originally posted by Supplement Four:
How is it you actually implement the anti-hijack program?
In order to access the ship's computer in my games, one needs to either gain access to a terminal in engineering or on the bridge, get hold of the captain's hand computer, or splice into the computer cabling directly and connect through a hand computer the hijacker brings aboard - Computer skill provides a beneficial modifier, and if the attempt to hack the program succeeds, then the crew may attempt to create a patch for the A-H program.

Typically any attempt to hack a program is modified by the difference between the hacker's skill level and the skill level used to create the program - if the hacker has Comp-2, and the program was created by someone with Comp-3, then a -1 modifier applies. I don't typically use opposed rolls between programmers except where a specific sort of cyberspace environment exists - I'm playing Traveller, not Shadowrun! ;)
 
Originally posted by The Shaman:


The potential lag time between when Naassirka identifies a threat, develops a patch, and distributes it across a subsector, or a sector, or the whole Imperium and points beyond, will mean a lot of ships are facing potential failure of their A-H program in the interim (which again explains the roll to bypass the program).

It's not like a subscription to Norton Anti-Virus! ;)
why not?

it should be available at every TAS business office or any imperial port. I'd imagine when you plug into a starport net, your software immediately searches for any updates to whatever software you've got. when you install them is up to you.

As for attacking Naasirka software, seems like a non-traveller plot, more for like a Cyberpunk-Trav crossover, which has its own merits. However I'm not sure how many GMs will sketch out a random hacker scenario that just does damage for the heck of it...IRL yes, that sorta crap happens on a daily basis...lots of bored people.

I can't see a trav GM doing this in every port and every ship. "YOU'RE ALWAYS VULNERABLE!!!" that sort of scenario would die a quick death.

Hacking into the Freight/Passenger system on _____ system might be interesting, but every jump along the way ? Once again a hacker-centric game might go that route, but for the most part...
 
Originally posted by The Shaman:


The potential lag time between when Naassirka identifies a threat, develops a patch, and distributes it across a subsector, or a sector, or the whole Imperium and points beyond, will mean a lot of ships are facing potential failure of their A-H program in the interim (which again explains the roll to bypass the program).

It's not like a subscription to Norton Anti-Virus! ;)
why not?

it should be available at every TAS business office or any imperial port. I'd imagine when you plug into a starport net, your software immediately searches for any updates to whatever software you've got. when you install them is up to you.

As for attacking Naasirka software, seems like a non-traveller plot, more for like a Cyberpunk-Trav crossover, which has its own merits. However I'm not sure how many GMs will sketch out a random hacker scenario that just does damage for the heck of it...IRL yes, that sorta crap happens on a daily basis...lots of bored people.

I can't see a trav GM doing this in every port and every ship. "YOU'RE ALWAYS VULNERABLE!!!" that sort of scenario would die a quick death.

Hacking into the Freight/Passenger system on _____ system might be interesting, but every jump along the way ? Once again a hacker-centric game might go that route, but for the most part...
 
Originally posted by Supplement Four:


How is it you actually implement the anti-hijack program?

Say a passenger in their stateroom pulls out some custom-built hacking equipment secreted withing their luggage. They hook it up to the terminal in the stateroom, and attempt to get past the firewalls (from your definition) or the filters (from the SOM).

How would you, as a GM, handle that?

Simple skill roll for the intruder plus any bonuses or penalities. Failed rolls results in either: A) an alert to the system engineer or B)
nothing other than that terminal being shutdown or C) both.

If it's intregal to the game (say the players are doing the intruding and need to get at recent navigation data because the ship is suspected smuggler) then you can get more detailed.

If it's a whim (bored player A is tired of leafing thru RPG books and decides suddenly to hack during jump) then if it's just going to screw up the overall scenario, it might suffer a quick death.

As a GM I'd make it as important as necessary.
 
Originally posted by Supplement Four:


How is it you actually implement the anti-hijack program?

Say a passenger in their stateroom pulls out some custom-built hacking equipment secreted withing their luggage. They hook it up to the terminal in the stateroom, and attempt to get past the firewalls (from your definition) or the filters (from the SOM).

How would you, as a GM, handle that?

Simple skill roll for the intruder plus any bonuses or penalities. Failed rolls results in either: A) an alert to the system engineer or B)
nothing other than that terminal being shutdown or C) both.

If it's intregal to the game (say the players are doing the intruding and need to get at recent navigation data because the ship is suspected smuggler) then you can get more detailed.

If it's a whim (bored player A is tired of leafing thru RPG books and decides suddenly to hack during jump) then if it's just going to screw up the overall scenario, it might suffer a quick death.

As a GM I'd make it as important as necessary.
 
Back
Top