DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Encryption info
Date: Tue, 6 Jan 2015 09:33:40 +0100	[thread overview]
Message-ID: <20150106083340.GA32360@tansi.org> (raw)
In-Reply-To: <20150106064737.GA1953@fritha.org>

On Tue, Jan 06, 2015 at 07:47:37 CET, Heinz Diehl wrote:
> 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.

Good idea. I think this is a definite possibility. Privilege
escalation with user action is far easier than without, especially
if the click then asks for escalation.
 
> Btw: You have a backup of your data?

If the data is encrypted, your best bet is likely reconstruction
from backup and then patching it before connecting it to
the net again.

Arno

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

      reply	other threads:[~2015-01-06  8:33 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
2015-01-06  8:33     ` Arno Wagner [this message]

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=20150106083340.GA32360@tansi.org \
    --to=arno@wagner.name \
    --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