> Is there any truth in the claim from some employers that having a
> mobile phone switched on within about 3 metres of a computer monitor
> allows the potential for remote compromise of the data on the screen
> via the mobile phone network?
I wouldnt believe it's common or easily available. Lots
The discussion about 'safe' text editors brings about an
interesting question:
Is an editor needed at all?
Why not just input text into gnupg and then encrypt the inputted
txt without saving it as file at all ?
example:
$ printf "just a test" | gpg -c -a
gpg: using cipher TWOFISH
gpg: writing
Am Do 13.09.2012, 11:47:06 schrieb ved...@nym.hush.com:
> Is there any limitation to the size of such a text message that
> gnupg can handle when done this way, (or any other problems)?
There is a limitation in comfort...
--
☺
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
signature.asc
On 09/13/12 16:47, ved...@nym.hush.com wrote:
> The discussion about 'safe' text editors brings about an
> interesting question:
>
> Is an editor needed at all?
>
> Why not just input text into gnupg and then encrypt the inputted
> txt without saving it as file at all ?
>
> example:
>
> $ pri
On 09/13/2012 05:47 PM, ved...@nym.hush.com wrote:
> The discussion about 'safe' text editors brings about an
> interesting question:
>
> Is an editor needed at all?
>
...
> Is there any limitation to the size of such a text message that
> gnupg can handle when done this way, (or any other pr
On 13/09/12 17:47, ved...@nym.hush.com wrote:
> $ printf "just a test" | gpg -c -a
Also, this would obviously end up in the history file unless you turn that off.
Better just invoke gpg, start typing and end with Control-D.
$ gpg -c -a
just a test
Peter.
--
I use the GNU Privacy Guard (GnuPG)
On 09/13/2012 06:22 PM, Kristian Fiskerstrand wrote:
> On 09/13/2012 05:47 PM, ved...@nym.hush.com wrote:
>> The discussion about 'safe' text editors brings about an
>> interesting question:
>>
>> Is an editor needed at all?
>>
>
> ...
>
>> Is there any limitation to the size of such a text mess
On 13/09/12 18:34, Kristian Fiskerstrand wrote:
> Apparently only half-awake here, this should of course be amended to
> include that since the plaintext is shown in the command line it is also
> available to other users on the system in a process list (e.g. ps)
I just thought of the fact that pro
Dear, on CentOS 6 (not tested in previous) below this line insists on
opening the box asking me to enter the passphrase:
echo $ PASSWORD | gpg - passphrase-fd 0 - no-tty-cv $ ARQ
But how is a script that runs from cron need you to do this automatically (in
case I have used the standard output of
Boa tarde!
Prezados, no CentOS 6 (Não testei nos anteriores) esta linha abaixo insiste
em abrir a caixa pedindo-me para digitar a frase secreta:
echo $SENHA | gpg --passphrase-fd 0 --no-tty -cv $ARQ
Porém como é um script que roda pelo cron preciso que faça isto
automaticamente (no caso tenho usa
Now I had a similar problem with debian packages.
That's what I got from dpkg-buildpackage :
dpkg-buildpackage: warning: Failed to sign .dsc and .changes file
Checking signature on .changes
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signa
11 matches
Mail list logo
