Interview with Dimitris Loulis from Northwind – HddSurgery

We believe that the quality of products and satisfaction of our clients are the best marketing there is. When our colleagues from data recovery and computer forensics community recommend our tools, we know that we are on the right path and making the right moves.

In order to present what data recovery community thinks about HddSurgery products, we started publishing interviews with various data recovery experts.

First in line was Dimitris Loulis from Northwind Data Recovery.
Northwind Data recovery Clean room

1. Today we are speaking with Dimitris Loulis, data recovery specialist from Northwind Data recovery. Dimitris, can you tell us about your company?

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


Unsubscribe any time. We respect your privacy - read our privacy policy.

Hello 🙂 We are one of the largest Data Recovery companies in Greece, located in Thessaloniki. We are currently setting up our expansion offices in Athens too.
We are the only Data Recovery company in Greece who are certified WD partners and also we are the only ones with a full sized Clean Room. The Clean Room is essential for opening Hard Drives in a clean environment, free of dust particles.

2. How did you start with data recovery business?

This is funny; I used to work as a freelance web designer back in 1994. I was considered the ‘guru’ of computers among friends etc and one day one of them called me and he was in panic, because he couldn’t access his university diplomatic research.

I recovered the drive, I remember it was a Quantum maybe 2GB in capacity or so, very expensive back then. And then I said, hey, I’m good at this 🙂

Read the full interview on our HddSurgery Blog page.

Folow HddSurgery on Facebook, Twitter, LinkedIn, You Tube, Google + and Instagram.

Leave a Comment

Latest Videos

Quantifying Data Volatility for IoT Forensics With Examples From Contiki OS

Forensic Focus 22nd June 2022 5:00 am

File timestamps are used by forensics practitioners as a fundamental artifact. For example, the creation of user files can show traces of user activity, while system files, like configuration and log files, typically reveal when a program was run. 

Despite timestamps being ubiquitous, the understanding of their exact meaning is mostly overlooked in favor of fully-automated, correlation-based approaches. Existing work for practitioners aims at understanding Windows and is not directly applicable to Unix-like systems. 

In this paper, we review how each layer of the software stack (kernel, file system, libraries, application) influences MACB timestamps on Unix systems such as Linux, OpenBSD, FreeBSD and macOS.

We examine how POSIX specifies the timestamp behavior and propose a framework for automatically profiling OS kernels, user mode libraries and applications, including compliance checks against POSIX.

Our implementation covers four different operating systems, the GIO and Qt library, as well as several user mode applications and is released as open-source.

Based on 187 compliance tests and automated profiling covering common file operations, we found multiple unexpected and non-compliant behaviors, both on common operations and in edge cases.

Furthermore, we provide tables summarizing timestamp behavior aimed to be used by practitioners as a quick-reference.

Learn more: https://dfrws.org/presentation/a-systematic-approach-to-understanding-macb-timestamps-on-unixlike-systems/

File timestamps are used by forensics practitioners as a fundamental artifact. For example, the creation of user files can show traces of user activity, while system files, like configuration and log files, typically reveal when a program was run.

Despite timestamps being ubiquitous, the understanding of their exact meaning is mostly overlooked in favor of fully-automated, correlation-based approaches. Existing work for practitioners aims at understanding Windows and is not directly applicable to Unix-like systems.

In this paper, we review how each layer of the software stack (kernel, file system, libraries, application) influences MACB timestamps on Unix systems such as Linux, OpenBSD, FreeBSD and macOS.

We examine how POSIX specifies the timestamp behavior and propose a framework for automatically profiling OS kernels, user mode libraries and applications, including compliance checks against POSIX.

Our implementation covers four different operating systems, the GIO and Qt library, as well as several user mode applications and is released as open-source.

Based on 187 compliance tests and automated profiling covering common file operations, we found multiple unexpected and non-compliant behaviors, both on common operations and in edge cases.

Furthermore, we provide tables summarizing timestamp behavior aimed to be used by practitioners as a quick-reference.

Learn more: https://dfrws.org/presentation/a-systematic-approach-to-understanding-macb-timestamps-on-unixlike-systems/

YouTube Video UCQajlJPesqmyWJDN52AZI4Q_i0zd7HtluzY

A Systematic Approach to Understanding MACB Timestamps on Unixlike Systems

Forensic Focus 21st June 2022 5:00 am

This error message is only visible to WordPress admins

Important: No API Key Entered.

Many features are not available without adding an API Key. Please go to the YouTube Feed settings page to add an API key after following these instructions.

Latest Articles

Share to...