Skip to contentSkip to conversation

Wiretapping Linux?

DISCUSSION Joerg Pommnitz 4 participants 7 messages May 17, 2006

lore
Share & tools
lore
#0 lore raw

Hello all,
while I agree with the points made in this discussion that it is harder to get a backdoor into Linux I'm left wondering about the whole computing system Linux is running on. Modern network card have enough computing power to easily run wiretapping that you won't see in the driver code. If you are concerned about wiretapping, then the large binary blobs of firmware needed to run your peripherals should be of real concern.

The same is true for the BIOS. Even older CPUs come with a system mode that exists outside the realm controlled by the OS.

Regards
Joerg

___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

#1 lore raw
Quoted 8 lines · Joerg Pommnitz

Hello all,
while I agree with the points made in this discussion that it is harder to get a backdoor into Linux I'm left wondering about the whole computing system Linux is running on. Modern network card have enough computing power to easily run wiretapping that you won't see in the driver code. If you are concerned about wiretapping, then the large binary blobs of firmware needed to run your peripherals should be of real concern.

Quoted 6 lines

The same is true for the BIOS. Even older CPUs come with a system mode that exists outside the realm controlled by the OS.

Regards
Joerg

CPUs inside network cards (if any) don't run in the same address-space as your host CPU, memory, etc. Data is DMAed (set up on the host-CPU side) to/from this private bus, using the PCI bus. You would need very extensive cooperative code running on the host CPU (in the driver) to do anything useful. If you are going to write such driver code, you don't need the CPU inside the controller card at all because you are already running with high privileges on the correct bus.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.4 on an i686 machine (5592.89 BogoMips). New book: http://www.AbominableFirebug.com/ http://www.LymanSchool.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.

#2 lore raw
Quoted 9 lines · --- "linux-os (Dick Johnson)

CPUs inside network cards (if any) don't run in the same address-space as your host CPU, memory, etc. Data is DMAed (set up on the host-CPU side) to/from this private bus, using the PCI bus. You would need very extensive cooperative code running on the host CPU (in the driver) to do anything useful. If you are going to write such driver code, you don't need the CPU inside the controller card at all because you are already running with high privileges on the correct bus.

Wiretapping is about listening in on communication. Network cards are the means this communication is carried out and see all the traffic somebody might want to tap into. This clearly makes it at least theoretically possible to use them as a listening device (and it sees all the other traffic on its network segment, too).

Additionally its listening on the system bus. Question: Can it tap into data addressed to another peripheral (say the hd controller)? If so, then only the system RAM is outside its scope.

Regards
Joerg

___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

#3 lore raw
Quoted 2 lines · Joerg Pommnitz

Additionally its listening on the system bus. Question: Can it tap into data addressed to another peripheral (say the hd controller)? If so, then only the system RAM is outside its scope.

A pci device can read system RAM and other memory-mapped PCI devices (such as display framebuffers) using DMA. In addition, a pci (but not pci-express) device can snoop on pci bus traffic to other devices. Typically, however, hard drive controllers will be integrated into the chipset so the data is not on the bus.

Signature · 1 line
error compiling committee.c: too many arguments to function
#4 lore raw
Quoted 6 lines · --- Avi Kivity

A pci device can read system RAM and other memory-mapped PCI devices (such as display framebuffers) using DMA. In addition, a pci (but not pci-express) device can snoop on pci bus traffic to other devices. Typically, however, hard drive controllers will be integrated into the chipset so the data is not on the bus.

Thanks for providing this information. This makes the binary firmware required for peripherals even more interesting for security conscious people.

Regards
Joerg

Signature · 11 lines
Regards
       Joerg



	

	
		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
#5 lore raw
Quoted 9 lines · Joerg Pommnitz
Quoted 2 lines · --- Avi Kivity

A pci device can read system RAM and other memory-mapped PCI devices (such as display framebuffers) using DMA. In addition, a pci (but not pci-express) device can snoop on pci bus traffic to other devices. Typically, however, hard drive controllers will be integrated into the chipset so the data is not on the bus.

Thanks for providing this information. This makes the binary firmware required for peripherals even more interesting for security conscious people.

Note that some machines have IOMMUs so it may be possible to prevent a device from reading main memory, perhaps at a performance cost.

My AMD machine disables the IOMMU on startup.

If you don't trust your hardware there are only two solutions: keep it off the net or keep it off.

Signature · 1 line
error compiling committee.c: too many arguments to function
#6 lore raw
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines

A pci device can read system RAM and other memory-mapped PCI devices (such as display framebuffers) using DMA. In addition, a pci (but not pci-express) device can snoop on pci bus traffic to other devices. Typically, however, hard drive controllers will be integrated into the chipset so the data is not on the bus.

Thanks for providing this information. This makes the binary firmware required for peripherals even more interesting for security conscious people.

Quoted 7 lines

Note that some machines have IOMMUs so it may be possible to prevent a device from reading main memory, perhaps at a performance cost.

My AMD machine disables the IOMMU on startup.

If you don't trust your hardware there are only two solutions: keep it off the net or keep it off.

It gets even more complex with remote management solutions, ranging from simple PCI boards that can reset the machine to fully-integrated [like Sun's RSC] processors that can poke anything.

Jan Engelhardt