[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-crypto
Subject: Re: "Clean" way of getting a key over to aespipe
From: Matthias Schniedermeyer <ms () citd ! de>
Date: 2005-10-09 12:44:03
Message-ID: 43491093.8040804 () citd ! de
[Download RAW message or body]
Jari Ruusu wrote:
> Matthias Schniedermeyer wrote:
>
> > aespipe -p3 -d < <data> 3< <key>
> > didn't seam to work for me. :-(
>
>
> aespipe -d -e AES128 -p3 3<cleartext-65-line-key-file <inputFile >outputFile
> ^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> aespipe -d -e AES128 -p3 3< <( ./cleartext-65-line-key-outputting-script ) \
> <inputFile >outputFile ^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> aespipe -d -e AES128 -K foo.gpg -p3 3<cleartext-1-line-gpg-passphrase-file \
> <inputFile >outputFile ^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> aespipe -d -e AES128 -K foo.gpg -p3 3< <( \
> ./cleartext-1-line-gpg-passphrase-outputting-script ) <inputFile >outputFile ^^^ \
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Thanks for your help in enlighten me to a bid more of "shell-magic". :-)
Seems for the "simple" 3< cases i just used the wrong order.
The "process substitution"-cases gave me a headache at first (Just got
syntax-errors).
They don't seem work from a Shell-Script with "#!/bin/sh" as shebang.
But after trying them on the commandline and then with "#!/bin/bash" as
shebang they work like charm. :-))
"ls -la /bin/sh" shows a symlink to bash. Guess there are some
compatibility things that can throw with stones. ;-)
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic