DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd+ml@fritha.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Encryption info
Date: Tue, 6 Jan 2015 07:47:37 +0100	[thread overview]
Message-ID: <20150106064737.GA1953@fritha.org> (raw)
In-Reply-To: <CA+JQLgK3+oEYG-B1ETvhLUD5v0y16jTnsuutRY7dT=d7UkxH+Q@mail.gmail.com>

On 05.01.2015, Gary Evetts wrote: 

> Are you able to help me with the un-encrypting of the data files that have
> been encrypted or are the offenders the only source of a resolution?

LUKS/cryptsetup is not used here, since you are on Windows.
However, you should check if your files are actually encrypted or
not. For me, there's a possibility that they only want you to click on
the .EXE, with all the nasty consequences this could have.

Btw: You have a backup of your data?

  parent reply	other threads:[~2015-01-06  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7FD87F5D-AD43-4CC1-8FBA-724919533835@it-inc.co.za>
2015-01-05  9:51 ` [dm-crypt] Fwd: Encryption info Gary Evetts
2015-01-05 12:54   ` Arno Wagner
2015-01-06  6:47   ` Heinz Diehl [this message]
2015-01-06  8:33     ` Arno Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150106064737.GA1953@fritha.org \
    --to=htd+ml@fritha.org \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox