This is actually relatively easy to do. For simplicity, we will use two cubes.

On cube1, we can add a Keyboard sensor, connected to an And controller, which is connected a Message actuator.

The "To" field on the message actuator doesn't actually need to be filled in. If it is left blank, the actuator will simply broadcast the message to all objects, instead of just one. Since only one object will be listening for the message, the "To" field doesn't matter here. You could also set the "Subject" field to whatever you want.

On Cube2, we simply need a Message sensor listening for the message that Cube1 sent out. We can do that by putting the message Cube1 is sending in the "Subject" field on the message sensor on Cube2. That message sensor should connect to an And controller, which should connect to a property actuator. The easiest property for this will be a Boolean property. Add one, and name it whatever you want. Then, In the property actuator, put in the name of the property you just created. set the operation to "Assign" and the value to "True." Now, add a property sensor, with the same property in the "Property" field. you want this sensor to check if the Boolean property you created is true. To do this, set the "Value" field to True. Enable true levle triggering. This will make it so that as long as the property is true, the sensor will constantly be telling the connected bricks to run. You can connect that property sensor to an And controller, and connect that your steering actuator.

As long as the property is true, the steering actuator will be running. You can also easily do the same sort of thing to assign the property False, to deactivate the steering actuator.

This is actually relatively easy to do. For simplicity, we will use two cubes.

On cube1, we can add a Keyboard sensor, connected to an And controller, which is connected a Message actuator.

The "To" field on the message actuator doesn't actually need to be filled in. If it is left blank, the actuator will simply broadcast the message to all objects, instead of just one. Since only one object will be listening for the message, the "To" field doesn't matter here. You could also set the "Subject" field to whatever you want.

On Cube2, we simply need a Message sensor listening for the message that Cube1 sent out. We can do that by putting the message Cube1 is sending in the "Subject" field on the message sensor on Cube2. That message sensor should connect to an And controller, which should connect to a property actuator. The easiest property for this will be a Boolean property. Add one, and name it whatever you want. Then, In the property actuator, put in the name of the property you just created. Set the operation to "Assign" and the value to "True." Now, add a property sensor, with that same Boolean in the "Property" field. you want this sensor to check if the Boolean property you created is true. To do this, set the "Value" field to True. Enable true level triggering. This will make it so that as long as the property is true, the sensor will constantly be telling the connected bricks to run. You can connect that property sensor to an And controller, and connect that your steering actuator.

As long as the property is true, the steering actuator will be running. You can also easily do the same sort of thing to assign the property False, to deactivate the steering actuator.