I have never had any issues moving keys between boxes. In fact I moved my
keys just last week to a box at work.
What exactly is the nature of the problem?
On Friday, November 14, 2014, da...@gbenet.com wrote:
> Hi All,
>
> After spending 62 hours on what I thought would be a simple task namely
astically lessen the chances of a
key being compromised or of a possible compromise having as much effect
on you. There is a reason things like IPSEC keys are renegotiated after
so many minutes or after so many bytes are transmitted. :)
--
Larry Brower, CCNA
Fedora Ambassador - North Amer
people. A
custom BSD distro targeted at non-technical people would be useful here.
Perhaps one which took Security and Privacy into account as design goal.
Staying away from flash would be easier if all these people who think
they are web developers would stop using it.
--
Larry Brower, CCN
hat gets plugged in the instant it is
plugged in.
--
Larry Brower, CCNA
Fedora Ambassador - North America
Fedora Quality Assurance
lbro...@fedoraproject.org
http://www.fedoraproject.org/
0x0806CF8B.asc
Description: application/pgp-keys
___
Gnupg-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/16/2013 07:56 AM, Steven Bonda wrote:
> --batch --passphrase
Have you tried to do this without --batch and --passphrase?
Is there any change?
- --
Larry Brower, CCNA
Fedora Ambassador - North America
Fedora Quality Assurance
l
>*Department: *Piracy [English]
>*Type: *Issue
>*Status: *Open
>
What is with the helpdesk being a list member?
- --
Larry Brower, CCNA
Fedora Ambassador - North America
Fedora Quality Assurance
lbro...@fedoraproject.org
http://www.fedoraproject.org/
-BEGIN PGP SI
ist Gnupg-users@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>
- --
Larry Brower, CCNA
Fedora Ambassador - North America
Fedora Quality Assurance
lbro...@fedoraproject.org
http://www.fedoraproject.org/
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jul 13, 2013 at 4:56 PM, kardan wrote:
Hi,
When I search for a key via browser on [1] I get an unencrypted answer
from [2]. This happens for some keys that are onlyavailable on some
servers. The problem is that the info, whose key I am
se
On 05/17/2011 06:56 PM, Lucélio Gomes de Freitas wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear GnuPG staff,
>
> I have Virtualbox-4.0.6 installed ok on my Linux machine, but on
> updating to the newest one . . . .
> I got the following messages using(KDE) kpackage kit:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/11/2011 06:09 PM, MFPA wrote:
> That's all fair enough, but I still think the standard MITM attack is
> an example of "some hypothetical exploit by some hypothetical attacker
> compromises your communications."
>
MITM is not hypothetical and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/22/2011 06:32 PM, Jonathan Ely wrote:
> What is ECC? Now I want that haha.
Elliptic curve cryptography
http://en.wikipedia.org/wiki/Elliptic_curve_cryptography
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/02/2011 12:14 AM, frankexcha...@nospammail.net wrote:
> As mentioned I am a Linux newbie (command line adverse) and like many
> users of Ubuntu they would not know how access details of what the
> default symmetric cipher is.
>
> Use of the te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hauke Laging wrote:
> Hello,
>
> I just had the idea that it might be a good countermeasure against malicious
> software not to use a cached passphrase without any user interaction (and
> thus
> without user notice). A good compromise would be to o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Chitwood wrote:
> Yes, that is our key.
>
Have you verified it is trusted on the system you are trying to use it
on? Perhaps the key isn't trusted.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Moz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Chitwood wrote:
> Here you go.
>
> $ gpg --list-sigs F56DBCBE
> pub 2048R/F56DBCBE 2010-09-28
> uid Patrick Ashbrook
> sig N F56DBCBE 2010-09-28 Patrick Ashbrook
> sig 359B3EB2 2010-10-05 it.security@b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Chitwood wrote:
> Robert,
>
> This is a error that is preventing us from encrypting. The key has been
> trusted and signed.
>
>
> pub 2048R/F56DBCBE created: 2010-09-28 expires: never usage: SC
> trust: full
CONNIE RODRIGUEZ wrote:
Great!! Thank you for your help. I will post on how it went.
Welcome ;) Just let us know if you have any questions on anything.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gn
CONNIE RODRIGUEZ wrote:
Sorry forgot to mention this is in unix. Also, I do not have a backup
to re-import.
I figured is was Unix. Without a backup you wont be able to decrypt
the file.
Are you certain there is no backup? No backup of the system which
could have the .gnupg directory? Ta
CONNIE RODRIGUEZ wrote:
This is a development box..no backup. Can I copy from the another
environment?
yes if you have the key on another server such as a production box.
gpg --export-secret-key -a > a-filename-here
copy it to the dev box with something like scp
then on the dev box
gpg -
CONNIE RODRIGUEZ wrote:
Help!! Just last week I was able to decrypt files for our Vendor. I
tried this morning and now I get the message below. The only changes
that occurred was that another vendor key was added last week. The
ELG-E Key is the same the message was encrypted with. Any insi
20 matches
Mail list logo
