nd secure Linux operating systems.
Please, do not debate me on this. Yes, we could do otherwise, but that will
incur PCI DSS v3.2 challenges unnecessary to us.
Thank you.
~ helices
On Thu, Feb 22, 2018 at 12:22 AM, Ben McGinnes wrote:
> On Wed, Feb 21, 2018 at 07:36:08AM -0800, Dan Kegel wrot
opinion, humble or otherwise.
YMMV
Are there any other questions before I get a direct answer to my original
subject question?
Thank you.
On Wed, Feb 14, 2018 at 2:20 PM, helices wrote:
> CentOS 7 uses gnupg2 v2.0.22. EPEL doesn't have anything newer.
>
> We want to move to v2
gt;
>
> And of course YOU could create the rpm and share it on EPEL yourself so
> others will have it.
>
>
>
>
>
> *From:* Gnupg-users [mailto:gnupg-users-boun...@gnupg.org] *On Behalf Of *
> helices
> *Sent:* Thursday, February 15, 2018 9:10 AM
> *To:* gnupg-users@gnup
pgrade is usually not desirable which is why people use RHEL/CentOS
> instead.
>
> -Original Message-
> From: Gnupg-users [mailto:gnupg-users-boun...@gnupg.org] On Behalf Of
> Daniel Kahn Gillmor
> Sent: Wednesday, February 14, 2018 5:31 PM
> To: helices; gnupg-users@gnupg.org
&
CentOS 7 uses gnupg2 v2.0.22. EPEL doesn't have anything newer.
We want to move to v2.2.x, and stay current, but we don't want to download
source and compile for dozens of systems.
We want all users to be using the same version all of the time.
Please, advise. Thank you.
On Wed, Jul 19, 2017 at 9:49 AM, Peter Lebbing
wrote:
> On 19/07/17 16:30, helices wrote:
> > Unchecking that box and encrypting, this file decrypted and unzipped
> > without incident: Archive.zip.gpg
>
> And if you keep the box checked, does it produce a file named
o
process files. Will the UNchecked checkbox for "Archive files with: TAR
(PGP-compatible)" be default now?
~ Mike
On Wed, Jul 19, 2017 at 8:17 AM, helices wrote:
> How to NOT gnutar files during encryption?
>
>
> Thank you for your responses; but, you are all missing my poi
How to NOT gnutar files during encryption?
Thank you for your responses; but, you are all missing my point - and not
answering my question.
First, before encryption by Kleopatra, the file IS one (1) real ZIP file
(e.g., filename.zip)
After encryption and upload to us, the file is now an encrypt
We have a simple process that has worked for thousands of files over the
years:
1) Client ZIPs up a bunch of files
2) Client GPG/PGP encrypts that ZIP file
3) Client uploads that encrypted file to us
4) Our production server automatically decrypts the file
5) Our production server automatically unz
ormation Studies
> Texas Woman's University
> Stoddard Hall, Room 408
> P.O. Box 425438
> Denton, TX 76204-5438
>
> Phone: 615-603-5354 <615-604-5354>
> Email: wse...@twu.edu
>
> On Apr 17, 2017, at 1:50 PM, helices wrote:
>
> Version info from previous post:
Version info from previous post:
CentOS release 6.8 (Final)
gpg (GnuPG) 2.0.14
CentOS Linux release 7.3.1611 (Core)
gpg (GnuPG) 2.0.22
We are NOT using pinentry.
On Mon, Apr 17, 2017 at 1:37 PM, Daniel Kahn Gillmor
wrote:
> On Wed 2017-04-12 11:02:04 -0500, helices wrote:
> > Y
What am I missing?
Why am I getting this error?
Please, advise. Thank you.
On Wed, Apr 12, 2017 at 11:02 AM, helices wrote:
> Yes, I saw that. On one host, that works.
>
> On other, I get following error:
> gpg> passwd
> Key is protected.
>
> You need a passphrase
ou are completely out of
> luck.
>
> Will
>
>
> On 4/12/2017 11:02 AM, helices wrote:
>
> Yes, I saw that. On one host, that works.
>
> On other, I get following error:
> gpg> passwd
> Key is protected.
>
> You need a passphrase to unlock the secret
n cancelled
What am I missing?
On Wed, Apr 12, 2017 at 10:51 AM, Alaric L. Dailey
wrote:
> http://blog.chapagain.com.np/gpg-how-to-change-edit-
> private-key-passphrase/
>
> ------
> *From: *"helices"
> *To: *gnupg-users@gnupg.org
> *Sent:
How can I change the passphrase on our secret keys?
I've searched Google and gnupg.org to no avail.
What am I missing?
Versions:
gpg (GnuPG) 2.0.14
gpg (GnuPG) 2.0.22
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/lis
Peter,
Thank you. That suffices.
Notice that I did provide --version in my original post.
~ helices
On Wed, Mar 29, 2017 at 10:40 AM, Peter Lebbing
wrote:
> Hello,
>
> To solve your problem, could you please also post the commands that you
> used to create the files? The inf
How can I see if an encrypted file is signed and by whom?
Please, advise. Thank you.
~ helices
On Tue, Mar 28, 2017 at 8:22 AM, helices wrote:
> My company uses several keys for signing files encrypted with one of many
> recipient public keys.
>
> Once in awhile, we get pus
?
Please, advise. Thank you.
~ helices
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
<
kristian.fiskerstr...@sumptuouscapital.com> wrote:
> On 11/10/2016 03:50 PM, helices wrote:
> > So would I!
> >
> > At this point, our company must achieve PCI DSS compliance before year
> end,
> > and the road to that necessity leads through this auditor, who
So would I!
At this point, our company must achieve PCI DSS compliance before year end,
and the road to that necessity leads through this auditor, who insists that
PGP satisfies all requirements.
There is no explanation that he shares with us.
~ Mike
On Thu, Nov 10, 2016 at 8:27 AM, Mark H. W
much of this GPG and how much whatever is on
their side.
On Thu, Apr 24, 2014 at 12:55 PM, David Shaw wrote:
> On Apr 24, 2014, at 9:15 AM, helices wrote:
>
> > Thank you, for your response.
> >
> > [1]
> > -BEGIN PGP PUBLIC KEY BLOCK-
> > Version: E
Miller) and the public key. This signature again lies about the type of the
> issuing key, although this one is made with SHA1 instead of SHA256. Again,
> the signature seems valid.
>
> -- Further remarks --
>
> I should reiterate that I'm not fluent in GPG's code, so
respect this
vendor's desire to use one (1) key pair with all of their vendors.
Can their original key be "fixed?" Why does legacy GPG accept that public
key?
I welcome all comments, suggestions and review. Thank you
~ helices
On Wed, Apr 23, 2014 at 10:25 PM, David Shaw wrote:
GPG version trying to import: gpg (GnuPG) 2.0.14
Header from shared armored public key: Version: Encryption Desktop 10.3.0
(Build 8741)
GPG error on import:
# gpg --import /tmp/imps.asc
gpg: key 845F5188: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number
24 matches
Mail list logo
