From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Tue, 29 Oct 2019 13:50:36 +0100 (CET) Received: by mail-wr1-x42b.google.com with SMTP id s1so13541233wro.0 for ; Tue, 29 Oct 2019 05:50:36 -0700 (PDT) References: <1572265377.266405064@f517.i.mail.ru> From: Milan Broz Message-ID: <596ba688-9cb6-96be-9047-e36b17e2e8ff@gmail.com> Date: Tue, 29 Oct 2019 13:50:33 +0100 MIME-Version: 1.0 In-Reply-To: <1572265377.266405064@f517.i.mail.ru> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Does ver. 1.7.5 support veracrypt with PIM? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: netmonitoring , dm-crypt@saout.de On 28/10/2019 13:22, netmonitoring wrote: > Does ver. 1.7.5 support veracrypt with PIM? If so, how looks command line to mount the drive with custom PIM? No. PIM support for Veracrypt images was introduced in cryptsetup version 2.0.0, but there were more fixes in 2.0.3. You should use most recent stable version anyway (2.2.1 today, soon 2.2.2). Milan