Couple Can Sue Laptop-Tracking Company (LoJack) for Spying on Sex Chats

[Dustin]

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
news:j47jmm01ben@news4.newsguy.com:

> From: "Dustin" <bughunter.dustin@gmail.com>
>
>> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
>> news:j46lig02i2d@news3.newsguy.com:
>>
>>> It may be used w/o Internet access.
>>
>> For a period of time. You paid for the software and the monitoring
>> service which comes with it. You are understanding that you will
>> provide it a way to check in every so often, or it will, for your
>> protection, bios lock the boot process.
>>
>>> It may be used on a closed network.
>>
>> Actually, the dropped exe brags about being able to call home
>> regardless of firewall presence and network configuration.
>>
>>> It may be used as a tool or lab device.
>>
>> A tool for what?
>>
>
> You aren't getting it. When I say a closed network I mean a "closed
> network" as in a closed loop without any Internet access at all. A
> private network. Two come to mind.
>
> There are times when a notebook will be used as an instrument or
> toolo to setup other equipment such as programming radios. The
> notebook has specialty software and via USB hooks up to the
> equipment and the notebook's software is used to setup and programme
> the device.

I gotcha. In those cases, Lojack probably wouldn't fit the bill. It has
to be able to call home every so often. To ehh, check in.


--
I am a sinner
Hold my prayers upto the sun
I am a sinner
Heaven's closed for what I've done.

[David H. Lipman]

From: "Dustin" <bughunter.dustin@gmail.com>

> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
> news:j47jmm01ben@news4.newsguy.com:
>
>> From: "Dustin" <bughunter.dustin@gmail.com>
>>
>>> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
>>> news:j46lig02i2d@news3.newsguy.com:
>>>
>>>> It may be used w/o Internet access.
>>>
>>> For a period of time. You paid for the software and the monitoring
>>> service which comes with it. You are understanding that you will
>>> provide it a way to check in every so often, or it will, for your
>>> protection, bios lock the boot process.
>>>
>>>> It may be used on a closed network.
>>>
>>> Actually, the dropped exe brags about being able to call home
>>> regardless of firewall presence and network configuration.
>>>
>>>> It may be used as a tool or lab device.
>>>
>>> A tool for what?
>>>
>>
>> You aren't getting it. When I say a closed network I mean a "closed
>> network" as in a closed loop without any Internet access at all. A
>> private network. Two come to mind.
>>
>> There are times when a notebook will be used as an instrument or
>> toolo to setup other equipment such as programming radios. The
>> notebook has specialty software and via USB hooks up to the
>> equipment and the notebook's software is used to setup and programme
>> the device.
>
> I gotcha. In those cases, Lojack probably wouldn't fit the bill. It has
> to be able to call home every so often. To ehh, check in.
>
>

Right and those cases can be "exploited" (so to speak) to prevent LE from using LoJack
recovery successfully.

Lets say that the ROM code is able to communicate directly to the NIC. It isn't far
fetched. The ROM code would be hard coded for the embedded NIC and use Crynwar Packet
Drivers or NDIS2 stack. Disable the embedded NIC and install your own NIC. Thus the ROM
code for the embedded NIC would fail and wouldn't be able to use the installed NIC (e.g.,
PCMCIA, USB, etc). Install Linux and drivers for the new NIC and the whole process is
thwarted. Of course the thief has to be tech savvy to use thwarting techniques which,
initially, would low incidence occurrence.

--
Dave
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
http://www.pctipp.ch/downloads/dl/35905.asp

[G. Morgan]

David H. Lipman wrote:

> Thus the ROM
>code for the embedded NIC would fail and wouldn't be able to use the installed NIC (e.g.,
>PCMCIA, USB, etc). Install Linux and drivers for the new NIC and the whole process is
>thwarted.

What about after Linux is loaded and the new NIC starts working, don't
you think the ROM code will detect an active TCP/IP session and do it's
thing?

[Dustin]

G. Morgan <G_Morgan@easy.com> wrote in
news:mtqf671feomr77fqa49boj5fe4722bgtqv@Osama-is-dead.net:

> David H. Lipman wrote:
>
>> Thus the ROM
>>code for the embedded NIC would fail and wouldn't be able to use the
>>installed NIC (e.g., PCMCIA, USB, etc). Install Linux and drivers
>>for the new NIC and the whole process is thwarted.
>
> What about after Linux is loaded and the new NIC starts working,
> don't you think the ROM code will detect an active TCP/IP session
> and do it's thing?

The versions I've seen presently don't, no. However, a future update
might. I think the updates depend on the upcoming court case tho. [g]


--
I am a sinner
Hold my prayers upto the sun
I am a sinner
Heaven's closed for what I've done.

[G. Morgan]

Dustin wrote:

>G. Morgan <G_Morgan@easy.com> wrote in
>news:mtqf671feomr77fqa49boj5fe4722bgtqv@Osama-is-dead.net:
>
>> David H. Lipman wrote:
>>
>>> Thus the ROM
>>>code for the embedded NIC would fail and wouldn't be able to use the
>>>installed NIC (e.g., PCMCIA, USB, etc). Install Linux and drivers
>>>for the new NIC and the whole process is thwarted.
>>
>> What about after Linux is loaded and the new NIC starts working,
>> don't you think the ROM code will detect an active TCP/IP session
>> and do it's thing?
>
>The versions I've seen presently don't, no. However, a future update
>might. I think the updates depend on the upcoming court case tho. [g]

Hmmm. Are you going to reveal everything you have learned about the
code here? I'd be interested in your findings.

[Dustin]

G. Morgan <G_Morgan@easy.com> wrote in
news:ni3g671ke1higu7tbuo80pte43rjc9t4h5@Osama-is-dead.net:

> Hmmm. Are you going to reveal everything you have learned about the
> code here? I'd be interested in your findings.

Nope. If I decide to compile my notes into something techie readable,
it'll go on the site where everybody hangs out and disects these little
baddies. Oh wait... you don't know the site eh? LOL.


--
I am a sinner
Hold my prayers upto the sun
I am a sinner
Heaven's closed for what I've done.

[G. Morgan]

Dustin wrote:

>G. Morgan <G_Morgan@easy.com> wrote in
>news:ni3g671ke1higu7tbuo80pte43rjc9t4h5@Osama-is-dead.net:
>
>> Hmmm. Are you going to reveal everything you have learned about the
>> code here? I'd be interested in your findings.
>
>Nope. If I decide to compile my notes into something techie readable,
>it'll go on the site where everybody hangs out and disects these little
>baddies. Oh wait... you don't know the site eh? LOL.

No Dustin, I don't know where the blackhats hang out. You got me there!
I also don't know where the NAMBLA meetings are, do tell.

[David H. Lipman]

From: "G. Morgan" <G_Morgan@easy.com>

> David H. Lipman wrote:
>
>> Thus the ROM
>> code for the embedded NIC would fail and wouldn't be able to use the installed NIC
>> (e.g.,
>> PCMCIA, USB, etc). Install Linux and drivers for the new NIC and the whole process is
>> thwarted.
>
> What about after Linux is loaded and the new NIC starts working, don't
> you think the ROM code will detect an active TCP/IP session and do it's
> thing?
>

It doesn't like Linux and won't communicate through this OS to use the new NIC.


--
Dave
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
http://www.pctipp.ch/downloads/dl/35905.asp

[G. Morgan]

David H. Lipman wrote:

>From: "G. Morgan" <G_Morgan@easy.com>
>
>> David H. Lipman wrote:
>>
>>> Thus the ROM
>>> code for the embedded NIC would fail and wouldn't be able to use the installed NIC
>>> (e.g.,
>>> PCMCIA, USB, etc). Install Linux and drivers for the new NIC and the whole process is
>>> thwarted.
>>
>> What about after Linux is loaded and the new NIC starts working, don't
>> you think the ROM code will detect an active TCP/IP session and do it's
>> thing?
>>
>
>It doesn't like Linux and won't communicate through this OS to use the new NIC.

Ah..