Uh oh, Here We Go Again!
#421
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
DougW proclaimed:
> L.W.(Bill) ------ III did pass the time by typing:
>
>> They found the the computer. But I'm wondering how they may tell
>>that information wasn't copied. Specially since I'm being phished by
>>scammers for that information.
>
>
> They can't.
>
> They are relying on system file dates that get updated every time someone
> logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
> you can simply boot from that, copy what ever you want, and there are no
> tracks left behind.
>
Any self respecting data thief that has never heard of Lazarus and
similar probably wouldn't know what to do with the information if they
did get any. As for phishing for the information, that is contradictory
as they wouldn't be phishing if they already had it. On the subject of
phishing, has anyone noticed the big drop in quality lately? Poor
spelling, logos that look like they were done with MS Paint, just truly
lame reasons why it is being sent, etc. What *has* this country come to?
> L.W.(Bill) ------ III did pass the time by typing:
>
>> They found the the computer. But I'm wondering how they may tell
>>that information wasn't copied. Specially since I'm being phished by
>>scammers for that information.
>
>
> They can't.
>
> They are relying on system file dates that get updated every time someone
> logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
> you can simply boot from that, copy what ever you want, and there are no
> tracks left behind.
>
Any self respecting data thief that has never heard of Lazarus and
similar probably wouldn't know what to do with the information if they
did get any. As for phishing for the information, that is contradictory
as they wouldn't be phishing if they already had it. On the subject of
phishing, has anyone noticed the big drop in quality lately? Poor
spelling, logos that look like they were done with MS Paint, just truly
lame reasons why it is being sent, etc. What *has* this country come to?
#422
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
Last accessed is a feature of pretty much all file systems, but it is
utterly dependent on whether or not you access the data blocks with the
file system. It has no way of knowing if someone is using a block level
utility to open the file systems metadata and use that to walk the file
system...or even just a simple image to image copy that preserves the
original even down to block errors if any.
Matt Osborn proclaimed:
> Windows XP (and some others) maintain a 'last accessed' timestamp on
> all files. I would guess that is what they are relying upon.
>
> On Sun, 2 Jul 2006 10:11:58 -0500, "DougW"
> <post.replies@invalid.address> wrote:
>
>
>>L.W.(Bill) ------ III did pass the time by typing:
>>
>>> They found the the computer. But I'm wondering how they may tell
>>>that information wasn't copied. Specially since I'm being phished by
>>>scammers for that information.
>>
>>They can't.
>>
>>They are relying on system file dates that get updated every time someone
>>logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
>>you can simply boot from that, copy what ever you want, and there are no
>>tracks left behind.
>
>
>
>
> -- msosborn at msosborn dot com
utterly dependent on whether or not you access the data blocks with the
file system. It has no way of knowing if someone is using a block level
utility to open the file systems metadata and use that to walk the file
system...or even just a simple image to image copy that preserves the
original even down to block errors if any.
Matt Osborn proclaimed:
> Windows XP (and some others) maintain a 'last accessed' timestamp on
> all files. I would guess that is what they are relying upon.
>
> On Sun, 2 Jul 2006 10:11:58 -0500, "DougW"
> <post.replies@invalid.address> wrote:
>
>
>>L.W.(Bill) ------ III did pass the time by typing:
>>
>>> They found the the computer. But I'm wondering how they may tell
>>>that information wasn't copied. Specially since I'm being phished by
>>>scammers for that information.
>>
>>They can't.
>>
>>They are relying on system file dates that get updated every time someone
>>logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
>>you can simply boot from that, copy what ever you want, and there are no
>>tracks left behind.
>
>
>
>
> -- msosborn at msosborn dot com
#423
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
Last accessed is a feature of pretty much all file systems, but it is
utterly dependent on whether or not you access the data blocks with the
file system. It has no way of knowing if someone is using a block level
utility to open the file systems metadata and use that to walk the file
system...or even just a simple image to image copy that preserves the
original even down to block errors if any.
Matt Osborn proclaimed:
> Windows XP (and some others) maintain a 'last accessed' timestamp on
> all files. I would guess that is what they are relying upon.
>
> On Sun, 2 Jul 2006 10:11:58 -0500, "DougW"
> <post.replies@invalid.address> wrote:
>
>
>>L.W.(Bill) ------ III did pass the time by typing:
>>
>>> They found the the computer. But I'm wondering how they may tell
>>>that information wasn't copied. Specially since I'm being phished by
>>>scammers for that information.
>>
>>They can't.
>>
>>They are relying on system file dates that get updated every time someone
>>logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
>>you can simply boot from that, copy what ever you want, and there are no
>>tracks left behind.
>
>
>
>
> -- msosborn at msosborn dot com
utterly dependent on whether or not you access the data blocks with the
file system. It has no way of knowing if someone is using a block level
utility to open the file systems metadata and use that to walk the file
system...or even just a simple image to image copy that preserves the
original even down to block errors if any.
Matt Osborn proclaimed:
> Windows XP (and some others) maintain a 'last accessed' timestamp on
> all files. I would guess that is what they are relying upon.
>
> On Sun, 2 Jul 2006 10:11:58 -0500, "DougW"
> <post.replies@invalid.address> wrote:
>
>
>>L.W.(Bill) ------ III did pass the time by typing:
>>
>>> They found the the computer. But I'm wondering how they may tell
>>>that information wasn't copied. Specially since I'm being phished by
>>>scammers for that information.
>>
>>They can't.
>>
>>They are relying on system file dates that get updated every time someone
>>logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
>>you can simply boot from that, copy what ever you want, and there are no
>>tracks left behind.
>
>
>
>
> -- msosborn at msosborn dot com
#424
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
Last accessed is a feature of pretty much all file systems, but it is
utterly dependent on whether or not you access the data blocks with the
file system. It has no way of knowing if someone is using a block level
utility to open the file systems metadata and use that to walk the file
system...or even just a simple image to image copy that preserves the
original even down to block errors if any.
Matt Osborn proclaimed:
> Windows XP (and some others) maintain a 'last accessed' timestamp on
> all files. I would guess that is what they are relying upon.
>
> On Sun, 2 Jul 2006 10:11:58 -0500, "DougW"
> <post.replies@invalid.address> wrote:
>
>
>>L.W.(Bill) ------ III did pass the time by typing:
>>
>>> They found the the computer. But I'm wondering how they may tell
>>>that information wasn't copied. Specially since I'm being phished by
>>>scammers for that information.
>>
>>They can't.
>>
>>They are relying on system file dates that get updated every time someone
>>logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
>>you can simply boot from that, copy what ever you want, and there are no
>>tracks left behind.
>
>
>
>
> -- msosborn at msosborn dot com
utterly dependent on whether or not you access the data blocks with the
file system. It has no way of knowing if someone is using a block level
utility to open the file systems metadata and use that to walk the file
system...or even just a simple image to image copy that preserves the
original even down to block errors if any.
Matt Osborn proclaimed:
> Windows XP (and some others) maintain a 'last accessed' timestamp on
> all files. I would guess that is what they are relying upon.
>
> On Sun, 2 Jul 2006 10:11:58 -0500, "DougW"
> <post.replies@invalid.address> wrote:
>
>
>>L.W.(Bill) ------ III did pass the time by typing:
>>
>>> They found the the computer. But I'm wondering how they may tell
>>>that information wasn't copied. Specially since I'm being phished by
>>>scammers for that information.
>>
>>They can't.
>>
>>They are relying on system file dates that get updated every time someone
>>logs onto the machine. Problem is if you have a Knoppix disc (bootable linux)
>>you can simply boot from that, copy what ever you want, and there are no
>>tracks left behind.
>
>
>
>
> -- msosborn at msosborn dot com
#425
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
DougW proclaimed:
> No laptop will ever be truly secure till the encryption is hardware based and on
> the harddrive.
>
And further that the encryption hardware must rely on an additional
source of protection that does not physically exist on the hardware in
question nor is it a common style password. Passwords are usually easy
to guess or so obscure most folks write them down.
> No laptop will ever be truly secure till the encryption is hardware based and on
> the harddrive.
>
And further that the encryption hardware must rely on an additional
source of protection that does not physically exist on the hardware in
question nor is it a common style password. Passwords are usually easy
to guess or so obscure most folks write them down.
#426
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
DougW proclaimed:
> No laptop will ever be truly secure till the encryption is hardware based and on
> the harddrive.
>
And further that the encryption hardware must rely on an additional
source of protection that does not physically exist on the hardware in
question nor is it a common style password. Passwords are usually easy
to guess or so obscure most folks write them down.
> No laptop will ever be truly secure till the encryption is hardware based and on
> the harddrive.
>
And further that the encryption hardware must rely on an additional
source of protection that does not physically exist on the hardware in
question nor is it a common style password. Passwords are usually easy
to guess or so obscure most folks write them down.
#427
Guest
Posts: n/a
Re: Uh oh, Here We Go Again!
DougW proclaimed:
> No laptop will ever be truly secure till the encryption is hardware based and on
> the harddrive.
>
And further that the encryption hardware must rely on an additional
source of protection that does not physically exist on the hardware in
question nor is it a common style password. Passwords are usually easy
to guess or so obscure most folks write them down.
> No laptop will ever be truly secure till the encryption is hardware based and on
> the harddrive.
>
And further that the encryption hardware must rely on an additional
source of protection that does not physically exist on the hardware in
question nor is it a common style password. Passwords are usually easy
to guess or so obscure most folks write them down.