A gpg says "encrypted with 1 passphrase". Are there situations where a
message
gets encrypted with multiple passphrases?
ayoub@vboxpwfl:~/testdir$ ls
textfile
ayoub@vboxpwfl:~/testdir$ gpg --passphrase onetwothree --symmetric textfile
ayoub@vboxpwfl:~/testdir$ ls
textfile textfile.gpg
*> Quick question: how do you send data out? *
This is not a problem. You connect the output of your data diode to a
computer that will send the data over the Internet using whatever
required protocol. Some commercially available "data diodes" include a
"bare data diode" and the necessary
>>> "BM" == Brian Minton writes:
> On Tue, Jun 09, 2020 at 09:40:25AM +0200, Bernhard Reiter wrote:
>> If you trust a set of root certificates, like the ones shipped with your
>> operating system or a different application, you could just import them all
>> and mark them trusted. Of course you
Hello,
It seems I found a bug in ed25519 key yubikey's support.
Long story short :
* Generate a ed25519 Gnupg key and 3 subkeys
* Generate an ed25519 ssh key pair (SSH authority)
* Generate a SSH certificate by signing your public key (from Gnupg)
with your SSH authority
=> When deploying SSH
It has its merits; the drawback with this is the added network
traffic, the additional crunch power and the numerous servers. (I
know, nothing comes for free, everything comes at a price.)
Adding unpredictable randomness at different levels is a
> So, as described in Rob's paper, the sending server has to
> continuously send the data over and over again, with no idea whether
> the receiving server has received any of it, parts of it, or the
> whole of it.
Correct.
Our research was done as part of an electronic voting security group at
On Tue, Jul 28, 2020 at 10:33:42PM +0200, Denis BEURIVE via Gnupg-users wrote:
> > Oh, quite the contrary. It just forces the attacker to get clever.
>
> If your server only sends data through an "outgoing data diode", then it
> does not expose any entry point (you just disable all services : no
