RE: Unable to encrypt file with private/public key

2014-12-29 Thread Haritwal, Dhiraj
Almost done now. After I signed partner’s public key, that warring has gone.

I am using below command to encrypt file with my private key  partner’s public 
key  partner is using my private key  their public key to decrypt it but it’s 
getting fail. M I using anything wrong here.

./gpg --local-user 'MY USER’ --recipient partner_pubkey --encrypt --armor 
/tmp/test/data1.CSV

Tried to use --sign which is asking passphrase which don’t want to use. Can we 
sign without passphrase  only with public/private key.


Dhiraj


From: Pete Stephenson [mailto:p...@heypete.com]
Sent: 23 December 2014 11:24
To: Haritwal, Dhiraj
Cc: gnupg-users@gnupg.org
Subject: RE: Unable to encrypt file with private/public key


On Dec 22, 2014 7:30 AM, Haritwal, Dhiraj 
dhiraj.harit...@ap.sony.commailto:dhiraj.harit...@ap.sony.com wrote:

 Thank you very much for all the explanation/links. Now things are bit clear.
 Now I have to encrypt file with partner's Public Key. I tried with below 
 command which is still showing warning message (gpg: 89709B71: There is no 
 assurance this key belongs to the named user) whereas if I am checking 
 partner_pubkey, it's showing full trust. How can I remove this message. Even 
 I have added partner's public key as trusted.

 ./gpg --encrypt --recipient partner_pubkey --armor /tmp/test/data.CSV

I'm glad things are working better.

To resolve the issue with the assurance message, manually verify that the key 
belongs to the recipient (e.g. meet in person or call them and verify the 
fingerprint of their key) and then sign the key using GnuPG. (gpg --sign-key 
0xKEYID)

In GnuPG you vouch that a particular public key belongs to a person (or 
organization) by signing their public key. This signature can be local or 
published publicly.

Trust in GnuPG is different, and reflects how much you trust the other key to 
correctly vouch for the identity of others. If you set their key as fully 
trusted, keys that are signed by that key are treated by your copy of GnuPG 
with the same level of assurance as if you signed them yourself. Typically this 
should only be reserved for people you know to always check the identity of 
other people thoroughly and correctly before signing their keys. The default is 
for trust to be set to marginal.

By combining signatures and trust, one forms a web of trust: 
https://en.wikipedia.org/wiki/Web_of_trust

Cheers!
-Pete



This email is confidential and intended only for the use of the individual or 
entity named above and may contain information that is privileged. If you are 
not the intended recipient, you are notified that any dissemination, 
distribution or copying of this email is strictly prohibited. If you have 
received this email in error, please notify us immediately by return email or 
telephone and destroy the original message. - This mail is sent via Sony Asia 
Pacific Mail Gateway..
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Guys please all see

2014-12-29 Thread n...@enigmail.net
Guys please all see
 http://media.ccc.de/browse/congress/2014/31c3_-_6258_-_en_-_saal_1_-_201412282030_-_reconstructing_narratives_-_jacob_-_laura_poitras.html#video
to understand the important role, GPG plays.

Support us, please!

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Issue: unknown armor header: \x09Version: GnuPG v2.0.17 (MingW32)

2014-12-29 Thread Brian Minton
On Mon, Dec 22, 2014 at 5:41 AM, pkalluru pkall...@ebay.com wrote:

 *unknown armor header: \x09Version: GnuPG v2.0.17 (MingW32)*

0x09 is a tab character.  That sounds like a whitespace error.

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Gnupg-users Digest, Vol 135, Issue 42

2014-12-29 Thread Sandeep Murthy
 partner's public key as trusted.
 
  ./gpg --encrypt --recipient partner_pubkey --armor /tmp/test/data.CSV
 
 I'm glad things are working better.
 
 To resolve the issue with the assurance message, manually verify that the key 
 belongs to the recipient (e.g. meet in person or call them and verify the 
 fingerprint of their key) and then sign the key using GnuPG. (gpg --sign-key 
 0xKEYID)
 
 In GnuPG you vouch that a particular public key belongs to a person (or 
 organization) by signing their public key. This signature can be local or 
 published publicly.
 
 Trust in GnuPG is different, and reflects how much you trust the other key 
 to correctly vouch for the identity of others. If you set their key as fully 
 trusted, keys that are signed by that key are treated by your copy of GnuPG 
 with the same level of assurance as if you signed them yourself. Typically 
 this should only be reserved for people you know to always check the identity 
 of other people thoroughly and correctly before signing their keys. The 
 default is for trust to be set to marginal.
 
 By combining signatures and trust, one forms a web of trust: 
 https://en.wikipedia.org/wiki/Web_of_trust
 
 Cheers!
 -Pete
 
 
 
 This email is confidential and intended only for the use of the individual or 
 entity named above and may contain information that is privileged. If you are 
 not the intended recipient, you are notified that any dissemination, 
 distribution or copying of this email is strictly prohibited. If you have 
 received this email in error, please notify us immediately by return email or 
 telephone and destroy the original message. - This mail is sent via Sony Asia 
 Pacific Mail Gateway..
 -- next part --
 An HTML attachment was scrubbed...
 URL: /pipermail/attachments/20141229/183a0715/attachment.html
 
 --
 
 Subject: Digest Footer
 
 ___
 Gnupg-users mailing list
 Gnupg-users@gnupg.org
 http://lists.gnupg.org/mailman/listinfo/gnupg-users
 
 
 --
 
 End of Gnupg-users Digest, Vol 135, Issue 42
 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Guys please all see

2014-12-29 Thread MFPA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On Monday 29 December 2014 at 2:01:34 AM, in
mid:54a0b5fe.9090...@enigmail.net, n...@enigmail.net wrote:


 Guys please all see
 http://media.ccc.de/browse/congress/2014/31c3_-_6258_-_en_-_saal_1_-_201412282030_-_reconstructing_narratives_-_jacob_-_laura_poitras.html#video
 to understand the important role, GPG plays.

I'm not entirely sure how this relates to the thread in which you
posted it.


- --
Best regards

MFPAmailto:2014-667rhzu3dc-lists-gro...@riseup.net

You can't build a reputation on what you are going to do
-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJUoejzXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwFcAH/RcqKRDPHKvKnd8CMAP464+h
zv4LjC/MGHlqy4Pd6CeMedfhQc2MkK+Dlh30eCAQAG85AmDy030jjIYq2IaXwb0a
2qdQpCbR12viXJdcFqzU2U/1r4D9E0kuYVT83mOZ+3+3ULjeALGES+5+kn/k7XRy
koT39mBUIrNNxnF8H2QvMddmdgie+ItLyFLt0R9b/3wuGa6WnnGhNI/PECegVkH9
rRwXn36GCpK3NkEP80ZLxeWPGBCknIJGnZtDSH0E1o0mfJADKSbAcOq8VeLcJhuN
4A5O1dQKwZXgilIbwHdSpBWH2VP8puLqfV98av0ml5tMbZZOa8m1KSd1SvxL98eI
vgQBFgoAZgUCVKHo818UgAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45L7/AQBxPJEXpAljQhxWVGhqSSC8PR6D
xvOJrBkq+l6UFH/R3wEACri0zAYTJ1hgAiw/CXnEbJnnWFBlnDA4+zwujzz6aQg=
=aaDG
-END PGP SIGNATURE-


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


MOOC's

2014-12-29 Thread Dave Pawson
https://www.futurelearn.com/courses/introduction-to-cyber-security

Starting shortly, free Open course on cyber security.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users