eg: What is the structure of the "Header Case Information" block?
The E01 would be adequate (barely), if accompanied by an additional
"metadata" file that describes the physical format. (In much more
detail than just "IBM PC 360K", etc.) For MOST situations, OS,
encoding, bytes per sector, secto
And, of course, a lossy compression, such as MP4 leaves room for an
enormous amount of steganographic data, with documants and data hidden
in porn. (MANY different MP4 files will still play the same movie)
On Mon, 4 Feb 2019, John Foust via cctalk wrote:
That would be a very sneaky criminal i
On 2/4/19 3:40 PM, Jim Manley via cctalk wrote:
> Did someone say "punched cards ... with steganographic bits in chads that
> are only attached along a couple of edges"?
NCR CRAM?
Did someone say "punched cards ... with steganographic bits in chads that
are only attached along a couple of edges"?
On Mon, Feb 4, 2019 at 4:36 PM Chuck Guzis via cctalk
wrote:
> On 2/4/19 3:22 PM, John Foust via cctalk wrote:
> > At 04:49 PM 2/4/2019, Fred Cisin via cctalk wrote:
> >> And, of
On 2/4/19 3:22 PM, John Foust via cctalk wrote:
> At 04:49 PM 2/4/2019, Fred Cisin via cctalk wrote:
>> And, of course, a lossy compression, such as MP4 leaves room for an enormous
>> amount of steganographic data, with documants and data hidden in porn.
>> (MANY different MP4 files will still p
On 2/4/19 2:49 PM, Fred Cisin via cctalk wrote:
> Well, conversion between E01 and IMD or teledisk formats looks
> straightforward.
>
> http://www.forensicsware.com/blog/e01-file-format.html
> Is there a better description handy?
>
> eg: What is the structure of the "Header Case Information" blo
At 04:49 PM 2/4/2019, Fred Cisin via cctalk wrote:
>And, of course, a lossy compression, such as MP4 leaves room for an enormous
>amount of steganographic data, with documants and data hidden in porn. (MANY
>different MP4 files will still play the same movie)
That would be a very sneaky crimina
On Mon, 4 Feb 2019, Chuck Guzis via cctalk wrote:
Based on my conversations with clients, the problem is not the
equipment, but rather the lack of an open, vetted and documented file
format.
As an example, customers of mine insist on a "forensic" image file of
type E01 (Encase format), which has
On 2/4/19 1:17 PM, Paul Koning wrote:
> Yes, but if the current format is wrong for the job, and people who should
> know better do not realize this, it would be a good idea (as a separate
> activity) to educate them and propose a better answer.
Yes, I know, and I've tried and written volumes ab
> On Feb 4, 2019, at 4:05 PM, Chuck Guzis via cctalk
> wrote:
>
> ...
> Based on my conversations with clients, the problem is not the
> equipment, but rather the lack of an open, vetted and documented file
> format.
>
> As an example, customers of mine insist on a "forensic" image file of
>
On 1/18/19 7:40 AM, geneb via cctalk wrote:
> This looks like a project with a ton of potential for archviving media
> without having to deal with the asshattery of the kryoflux people.
>
> https://github.com/picosonic/bbc-fdc
Yes, you can do this, as I've said many times before, with just about
This looks like a project with a ton of potential for archviving media
without having to deal with the asshattery of the kryoflux people.
https://github.com/picosonic/bbc-fdc
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll
12 matches
Mail list logo
