Re: [Announce] GnuPG 2.1.1 released

2014-12-18 Thread Werner Koch
On Wed, 17 Dec 2014 13:54, dominyktil...@gmail.com said:

 I'm still hitting a new one though. If you attempt to compile using an
 external gpg-agent, rather than one with the package, you hit this:

You mean an option --disable-agent?  Do we still have this option - it
needs to be removed.  gpg-agent is not optional.



Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


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


Re: [Announce] GnuPG 2.1.1 released

2014-12-18 Thread Werner Koch
On Wed, 17 Dec 2014 22:21, 2014-667rhzu3dc-lists-gro...@riseup.net said:

 Could there be a similar issue with the %i for --photo-viewer?

 photo-viewer path\to\gpgview.exe  %i /title 0x%K.%t[%V]

I don't see any chnage in this part of the code.  Did it worked in 2.0?

Can you test on Unix too?  (Debugging there is much easier for me).


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


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


Re: [Announce] GnuPG 2.1.1 released

2014-12-18 Thread Dave Pawson
Running Fedora 21, 64 bit.
./configure gave error
missing ksba
Downloaded.
./configure gave libgpg-error is needed.

# yum install --disablerepo=Dropbox libgpg-error
Loaded plugins: langpacks
Package libgpg-error-1.13-3.fc21.x86_64 already installed and latest version
Nothing to do

Circular error?

regards


On 16 December 2014 at 16:36, Werner Koch w...@gnupg.org wrote:
 Hello!

 The GnuPG Project is pleased to announce the availability of the
 second release of GnuPG modern: Version 2.1.1.

 The GNU Privacy Guard (GnuPG) is a complete and free implementation of
 the OpenPGP standard as defined by RFC-4880 and better known as PGP.

 GnuPG, also known as GPG, allows to encrypt and sign data and
 communication, features a versatile key management system as well as
 access modules for public key directories.  GnuPG itself is a command
 line tool with features for easy integration with other applications.
 A wealth of frontend applications and libraries making use of GnuPG
 are available.  Since version 2 GnuPG provides support for S/MIME and
 Secure Shell in addition to OpenPGP.

 GnuPG is Free Software (meaning that it respects your freedom). It can
 be freely used, modified and distributed under the terms of the GNU
 General Public License.

 Three different versions of GnuPG are actively maintained:

 - GnuPG modern (2.1) is the latest development with a lot of new
   features.  This announcement is about the first release of this
   version.

 - GnuPG stable (2.0) is the current stable version for general use.
   This is what most users are currently using.

 - GnuPG classic (1.4) is the old standalone version which is most
   suitable for older or embedded platforms.

 You may not install modern (2.1) and stable (2.0) at the same
 time.  However, it is possible to install classic (1.4) along with
 any of the other versions.


 What's New in GnuPG-2.1
 ===

  * gpg: Detect faulty use of --verify on detached signatures.

  * gpg: New import option keep-ownertrust.

  * gpg: New sub-command factory-reset for --card-edit.

  * gpg: A stub key for smartcards is now created by --card-status.

  * gpg: Fixed regression in --refresh-keys.

  * gpg: Fixed regresion in %g and %p codes for --sig-notation.

  * gpg: Fixed best matching hash algo detection for ECDSA and EdDSA.

  * gpg: Improved perceived speed of secret key listisngs.

  * gpg: Print number of skipped PGP-2 keys on import.

  * gpg: Removed the option aliases --throw-keyid and --notation-data;
use --throw-keyids and --set-notation instead.

  * gpg: New import option keep-ownertrust.

  * gpg: Skip too large keys during import.

  * gpg,gpgsm: New option --no-autostart to avoid starting gpg-agent or
dirmngr.

  * gpg-agent: New option --extra-socket to provide a restricted
command set for use with remote clients.

  * gpgconf --kill does not anymore start a service only to kill it.

  * gpg-pconnect-agent: Add convenience option --uiserver.

  * Fixed keyserver access for Windows.

  * Fixed build problems on Mac OS X

  * The Windows installer does now install development files

  * More translations (but most of them are not complete).

  * To support remotely mounted home directories, the IPC sockets may
now be redirected.  This feature requires Libassuan 2.2.0.

  * Improved portability and the usual bunch of bug fixes.

 A detailed description of the changes found in 2.1 can be found at
 https://gnupg.org/faq/whats-new-in-2.1.html .


 Getting the Software
 

 Please follow the instructions found at https://gnupg.org/download/ or
 read on:

 GnuPG 2.1.1 may be downloaded from one of the GnuPG mirror sites or
 direct from its primary FTP server.  The list of mirrors can be found
 at https://gnupg.org/mirrors.html .  Note that GnuPG is not available
 at ftp.gnu.org.

 On ftp.gnupg.org you find these files:

  ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.1.tar.bz2  (4689k)
  ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.1.tar.bz2.sig

 This is the GnuPG 2.1 source code compressed using BZIP2 and its
 OpenPGP signature.

  ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.1_20141216.exe  (6364k)
  ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.1_20141216.exe.sig

 This is an *experimental* installer for Windows including GPA as
 graphical key manager and GpgEX as an Explorer extension.  Please
 de-install an already installed Gpg4win version before trying this
 installer.  This binary version has not been tested very well, thus it
 is likely that you will run into problems.  The complete source code
 for the software included in this installer is in the same directory
 with .exe replaced by .tar.xz.

 This version fixes a lot of bugs found after the release of 2.1.0 but
 there are still known bugs which we are working on.  Please check the
 mailing list archives and https://wiki.gnupg.org for known problems
 and workaround.


 Checking the Integrity
 ==

 In order to check 

Refreshing private key

2014-12-18 Thread Wayland Morgan
My current key is 2048 bits in length and I would like to have something
that is closer to 8192 bits in length. Is there a way that I can accomplish
this without revoking my key so that I can keep the same public key id?
Any preferred RTFMing you can point me to?

Thanks

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


Re: [Announce] GnuPG 2.1.1 released

2014-12-18 Thread Werner Koch
On Thu, 18 Dec 2014 11:59, dave.paw...@gmail.com said:

 ./configure gave libgpg-error is needed.

configure shows you which version of which libaries you need.  Please
install them.  The versions which come with your OS are usually too old.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


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


Re: Refreshing private key

2014-12-18 Thread Robert J. Hansen

 My current key is 2048 bits in length and I would like to have
 something that is closer to 8192 bits in length. Is there a way that
 I can accomplish this...

Definitely not from GnuPG, and probably not from without it, either.

GnuPG is capped at 4096 bits (for good reasons).

Further, you cannot change the length of the primary subkey on a
certificate.

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


RE: Unable to encrypt file with private/public key

2014-12-18 Thread Haritwal, Dhiraj
Hi,

Thanks for your response.

About the below command, it's asking for passphrase whereas my requirement is 
to use only keys to encrypt/sign it.

gpg2 -u FFEEDDCC -r AABBCCDD -se supersecret.txt

I tried below command which shows confirmation screen where I have entered y 
(yes)  now able to see a file named  supersecret.txt.gpg. m not sure what file 
it is because it think encrypted file should has an .asc extension.

./gpg --encrypt --hidden-recipient AABBCCDD supersecret.txt
gpg: 89709B71: There is no assurance this key belongs to the named user


Regards,

Dhiraj


-Original Message-
From: Gnupg-users [mailto:gnupg-users-boun...@gnupg.org] On Behalf Of Duplicity 
Mailing List
Sent: 17 December 2014 23:03
To: gnupg-users@gnupg.org
Subject: Re: Unable to encrypt file with private/public key

On 17/12/14 14:43, Haritwal, Dhiraj wrote:
 Hi,



 I am using gpg (GnuPG) 1.4.7  trying to encrypt a file with private
 key whose public key I have shared to the partner who have to decrypt
 this file. I tried with --armour -symmetric switches which requires a
 passphrase to encrypt but I have requirement to encrypt it through
 private/public key. If I am using -encrypt --hidden-recipient option
 showing below error. I am able to see the public key while running
 -list-keys option. I am running it on AIX 6.1 under root user.

If you just wish to encrypt, not sign, to the user, use:-

gpg2 --recipient AABBCCDD --encrypt supersecret.txt

Or the shorter version:-
gpg2 -r AABBCCDD -e supersecret.txt

It will dump supersecret.txt.gpg, that's your encrypted file. This isn't signed 
(I.E. the receiver won't be able to verify _you_ sent it, and can be replaced 
(Although not read) in transit). If you wish to sign it, you'll also need a GPG 
key in your keyring, then run:-

gpg2 --local-user FFEEDDCC --recipient AABBCCDD --encrypt --sign
supersecret.txt

Or the shorter version:-
gpg2 -u FFEEDDCC -r AABBCCDD -se supersecret.txt

Where FFEEDDCC is your key identifier and AABBCCDD is the recipient's key 
identifier. When they decrypt the file, they will see something along the lines 
of:-
gpg: Good signature from John Doe (john...@example.com) [ultimate]
gpg: binary signature, digest algorithm SHA512
gpg: decryption okay

the command you're using, --symmetric, is for using a passphrase for 
encryption/decrypt (I.E. symmetric encryption, not asymmetric).
--hidden-recipient should work too, and is used if you don't wish to include 
information about the recipient in the gpg file, you probably don't want to use 
this option (As oppose to --recipient) unless you really do wish to use the 
features it provides.

As for the failed public key, may I ask the exact command you're running? I get 
the same error message when I specify a recipient that doesn't exist:-

$ gpg2 -e -r ${RANDOM} b
gpg: 31546: skipped: No public key
gpg: b: encryption failed: No public key

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



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


RE: Unable to encrypt file with private/public key

2014-12-18 Thread vedaal
On 12/18/2014 at 10:38 AM, Dhiraj Haritwal dhiraj.harit...@ap.sony.com 
wrote:

About the below command, it's asking for passphrase whereas my 
requirement is to use only keys to encrypt/sign it.

gpg2 -u FFEEDDCC -r AABBCCDD -se supersecret.txt

-

'-s' in the above command means that you want to sign.

Whenever you want to sign, GnuPG asks for your passphrase to unlock your 
signing key.

=

I tried below command which shows confirmation screen where I have 
entered y (yes)  now able to see a file named  
supersecret.txt.gpg. m not sure what file it is because it think 
encrypted file should has an .asc extension.

./gpg --encrypt --hidden-recipient AABBCCDD supersecret.txt

-

'supersecret.txt.gpg' is the GnuPG encrypted output of the file 
'supersecret.txt'.

If unspecified, GnuPG will produce a .gpg file rather than a .asc file.

If you want a .asc file, you need to include the option of '--armor'
or '-a'  in your encryption command:

gpg2 -u FFEEDDCC -r AABBCCDD -a -e supersecret.txt



vedaal



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


Re: Unable to encrypt file with private/public key

2014-12-18 Thread Werner Koch
On Thu, 18 Dec 2014 16:39, dhiraj.harit...@ap.sony.com said:

 gpg2 -u FFEEDDCC -r AABBCCDD -se supersecret.txt

You asked to sign (-s) and thus it has to ask for the passphrase (unless
you key is not protected by a passphrase).

 I tried below command which shows confirmation screen where I have
 entered y (yes)  now able to see a file named supersecret.txt.gpg. m
 not sure what file it is because it think encrypted file should has an
 .asc extension.

If you want it ascii armored (which defaults to the .asc suffix) you
need to give the option --armor (or -a).


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


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


Re: Unable to encrypt file with private/public key

2014-12-18 Thread Duplicity Mailing List
On 18/12/14 15:39, Haritwal, Dhiraj wrote:
 Hi,
 
 Thanks for your response.
 
 About the below command, it's asking for passphrase whereas my requirement is 
 to use only keys to encrypt/sign it.
 
 gpg2 -u FFEEDDCC -r AABBCCDD -se supersecret.txt
 
 I tried below command which shows confirmation screen where I have entered y 
 (yes)  now able to see a file named  supersecret.txt.gpg. m not sure what 
 file it is because it think encrypted file should has an .asc extension.
 
 ./gpg --encrypt --hidden-recipient AABBCCDD supersecret.txt
 gpg: 89709B71: There is no assurance this key belongs to the named user
 
 
 Regards,
 
 Dhiraj

.gpg is the extension of encrypted files, .asc is normally ASCII armored
files (Signatures and the like), if you'd like to generate one of those,
look into the -a option (for Ascii). A complete command would look
something like `gpg2 -u AABBCCDD -as supersecret.txt`. The generated
supersecret.txt.asc will only verify to someone who already has the .txt
that it hasn't been touched/modified and that the key AABBCCDD did
verify it as being legitimate, they won't be able to extrapolate
supersecret.txt out of it. It's _only_ for signing, _not_ for
encrypting/transportation of data, which is why you often see them on
this mailing list and downloads (You want to verify that the user sent
the data, but not encrypt it (Since it's public)).

If you try to run:-

gpg -d supersecret.txt.gpg

It should tell you it's encrypted and the destination public key, then
error out (As it's not destined for you). As for the There is no
assurance this key belongs to thhe named user, this is because you
haven't trusted them yet. If you do trust the key as being the key they
claim to be, and have verified the key through out-of-bands means (I.E.
Not over the internet, or using an already secure channel over the
internet, this is *not* emails, this is *not* Skype, this is *not* text
messages), then you can take a look at this:-
https://www.gnupg.org/gph/en/manual/x334.html

P.S. I'm replying to you on-list for the reasons:-

1. People are able to verify if I say anything stupid
2. In the case I haven't said anything stupid, someone else could also
learn from this (I.E. Location this thread in the future via a search
engine).

I recommend you do the same.

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


Re: Unable to encrypt file with private/public key

2014-12-18 Thread Duplicity Mailing List
On 18/12/14 16:04, Duplicity Mailing List wrote:
 It's _only_ for signing, _not_ for
 encrypting/transportation of data


Ignore all of this. I made a huge mistake, apparently you can encrypt
data and store it in the ASCII files, I have no idea why I thought you
couldn't, it's so logical that you can, all it is doing is storing bytes
as ASCII, it's just I've never seen it in use so I never connected the
dots until I read vedaal's message.

What I'm trying to say is:-
.asc can be used for encrypted connect, albeit probably not recommending
if you're sending large files, just as much as it can be used for
signatures. Signatures are to verify the content hasn't been modified,
encryption is to verify that only the recipient can read the data, and
encrypt+sign is to verify the data hasn't been modified and the
recipient is the only one who can read it.

There we go, sorry for the mistake, I feel very stupid right about now.

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


Re: Refreshing private key

2014-12-18 Thread Daniel Kahn Gillmor
On 12/18/2014 10:24 AM, Robert J. Hansen wrote:
 My current key is 2048 bits in length and I would like to have
 something that is closer to 8192 bits in length. Is there a way that
 I can accomplish this...
 
 Definitely not from GnuPG, and probably not from without it, either.

There are clearly tools that you can use to make larger keys than
4096-bit RSA, e.g. gnutls-bin + monkeysphere:

certtool -p --bits 8192 | pem2openpgp 'Test User t...@example.org'

(this will produce a binary-formatted OpenPGP key on stdout, so you
probably want to send it to a file or something)

but I don't recommend trying to do this, because these larger RSA keys
are expensive to use compared to the marginal extra security, and their
signatures are large.

I recommend sticking with 4096-bit RSA for now; for stronger keys you'll
eventually want to move to a large ECC key (though the choices we have
at the moment for ECC have some shadow of suspicion over them).

 Further, you cannot change the length of the primary subkey on a
 certificate.

primary subkey doesn't make much sense.  I'm pretty sure Robert means
primary key.

--dkg



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: [Announce] GnuPG 2.1.1 released

2014-12-18 Thread Ingo Klöcker
On Thursday 18 December 2014 10:59:09 Dave Pawson wrote:
 Running Fedora 21, 64 bit.
 ./configure gave error
 missing ksba
 Downloaded.
 ./configure gave libgpg-error is needed.
 
 # yum install --disablerepo=Dropbox libgpg-error
 Loaded plugins: langpacks
 Package libgpg-error-1.13-3.fc21.x86_64 already installed and latest version
 Nothing to do
 
 Circular error?

I guess you are lacking the development package of libgpg-error. It's probably 
called libgpg-error-devel.

Whenever you want to build something yourself you have to install the 
development packages of all dependencies. Normal users don't need them. 
Therefore they are usually not installed by default.


Regards,
Ingo

signature.asc
Description: This is a digitally signed message part.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Refreshing private key

2014-12-18 Thread Robert J. Hansen

primary subkey doesn't make much sense.  I'm pretty sure Robert
means primary key.


Sorry, a little bit of inside baseball there [1].

tl;dr version -- Daniel's right.  Longer version follows.

At work I'm twiddling about with an OpenPGP parser and for various
reasons you really don't want me to get into, the class that defines
primary keys is a subclass of the class that defines subkeys.  It seems
backwards, but needs to be that way to preserve Liskov substitutability.

As a result, I wind up talking about primary subkeys because in my
head I'm talking about the PrimarySubkey class.  :)






[1] http://en.wikipedia.org/wiki/Inside_baseball_%28metaphor%29

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


latest version build error

2014-12-18 Thread Joshua Rogers
Hi,

I'm trying to build the latest version of gnupgp from the git repo, but
I'm encountering a problem while compiling it.

It all compiles fine up until logging.c.


gcc-g -O2 -O3 -Wall -Wcast-align -Wshadow -Wstrict-prototypes
-Wformat -Wno-format-y2k -Wformat-security -W -Wno-sign-compare
-Wno-missing-field-initializers -Wdeclaration-after-statement
-Wno-pointer-sign -Wpointer-arith   -o t-stringhelp t-stringhelp.o
t-support.o libcommon.a -lgcrypt -lassuan -L/usr/lib/x86_64-linux-gnu
-lgpg-error -L/usr/local/lib -lgpg-error
libcommon.a(libcommon_a-logging.o): In function `set_file_fd':
gnupg/common/logging.c:449: undefined reference to `gpgrt_fclose'
gnupg/common/logging.c:457: undefined reference to `_gpgrt_get_std_stream'
gnupg/common/logging.c:457: undefined reference to `gpgrt_fileno'
gnupg/common/logging.c:516: undefined reference to `gpgrt_fopencookie'
gnupg/common/logging.c:523: undefined reference to `gpgrt_setvbuf'
gnupg/common/logging.c:521: undefined reference to `_gpgrt_get_std_stream'
[.]

From a Google search, gpgrt_fclose, for example, is in libgpg-error.
# strings -a /usr/local/lib/libgpg-error.so.0 | grep 'gpgrt_fclose'
gpgrt_fclose
gpgrt_fclose_snatch
_gpgrt_fclose_snatch
_gpgrt_fclose
_gpgrt_fclose
_gpgrt_fclose_snatch
gpgrt_fclose_snatch
gpgrt_fclose



I run:
# ./configure --build=x86_64-pc-linux-gnu --enable-maintainer-mode
--with-libgpg-error-prefix=/usr/local


which outputs no errors, and this info:

GnuPG v2.1.2 has been configured as follows:

Revision:  5cb6df8  (23734)
Platform:  GNU/Linux (x86_64-pc-linux-gnu)

OpenPGP:   yes
S/MIME:yes
Agent: yes
Smartcard: yes
G13:   yes
Dirmngr:   yes
Gpgtar:yes

Protect tool:  (default)
LDAP wrapper:  (default)
Default agent: (default)
Default pinentry:  (default)
Default scdaemon:  (default)
Default dirmngr:   (default)

Dirmngr auto start:  yes
Readline support:yes
LDAP support:yes
DNS SRV support: yes
TLS support: gnutls




Any suggestions?

P.S: Please CC me, as I'm not subscribed to this list.

Thanks,
-- 
-- Joshua Rogers https://internot.info/



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Installation

2014-12-18 Thread realhosting
I can't install. Please help

root@server1:/var/www/gnupg-2.0.26#  ./configure
bash: ./configure: Permission denied
root@server1:/var/www/gnupg-2.0.26# chmod -R 777 *
root@server1:/var/www/gnupg-2.0.26#  ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
configure: autobuild project... gnupg
configure: autobuild revision... 2.0.26
configure: autobuild hostname... server1
configure: autobuild timestamp... 20141218-193017
checking for style of include used by make... GNU
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: in `/var/www/gnupg-2.0.26':
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details

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


Re: [Announce] GnuPG 2.1.1 released

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



On Thursday 18 December 2014 at 9:03:45 AM, in
mid:87388d5nym@vigenere.g10code.de, Werner Koch wrote:


 I don't see any chnage in this part of the code.  Did
 it worked in 2.0?

I had not used 2.0 much at all because my email app of choice doesn't
play nice with it (but is fine with 2.1). I have 2.0.20 and 2.0.26 to
hand; I just tested with them and found it didn't work for me. For
both of these, the error message was slightly different than I see
with 2.1:-

gpg: system error while calling external program: Permission denied
gpg: unable to display photo ID!  ^

instead of:-

gpg: system error while calling external program: No error
gpg: unable to display photo ID!  



 Can you test on Unix too?  (Debugging there is much
 easier for me).

The best I can do is try to get my Linux partition working again, if
the wife doesn't invent too much that needs doing over Christmas.


- --
Best regards

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

After all is said and done, a lot more will be said than done.
-BEGIN PGP SIGNATURE-

iQF8BAEBCgBmBQJUk0wwXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwZc8IAIEkdqDjV5WK7Y6cHZF2Vi54
JCDD0U1set5Cs0nczv7jFTXAI15JIsw5brWRcPlKzDM4uBwNgnhFBC5Arr4f/UHB
2Yd1cmaGFE90ArQ4j9resAZ6Pv0MIvbvL3GwL/kvUAU6gPAqS72PlO9dyafmIbYz
id6xDJCwOpJFT5XVYSAThJ2n/+Ao4KuOMsPqt9sU1QdSMNJwKS7MUdFil/85AK1p
kIW7I/sIK+sLYwrvDIon3T8V/Za/eMeJVjM8AgD1A7pNbynh161hV9bH+GHXNGxC
GkM1Kbj4ufK0dkow9ZEhwKeQnG7wx8Y+bcUoFJ9KNIorfEke/wU+b3ZQP87DrSuI
vgQBFgoAZgUCVJNMOF8UgAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45LljAQCATOKlAtFkQd+KRGSeO4QLj/HR
PXMd+g/TcollLscJNQEATn+VQZ6opqQZxDvtAewoqSRSYLGBETmzJhKiA0Wjgw8=
=GTud
-END PGP SIGNATURE-


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


Re: latest version build error

2014-12-18 Thread Daniel Kahn Gillmor
On 12/18/2014 05:14 AM, Joshua Rogers wrote:

 I'm trying to build the latest version of gnupgp from the git repo, but
 I'm encountering a problem while compiling it.

I think you mean gnupg, not gnupgp :)

 libcommon.a(libcommon_a-logging.o): In function `set_file_fd':
 gnupg/common/logging.c:449: undefined reference to `gpgrt_fclose'
 gnupg/common/logging.c:457: undefined reference to `_gpgrt_get_std_stream'
 gnupg/common/logging.c:457: undefined reference to `gpgrt_fileno'
 gnupg/common/logging.c:516: undefined reference to `gpgrt_fopencookie'
 gnupg/common/logging.c:523: undefined reference to `gpgrt_setvbuf'
 gnupg/common/logging.c:521: undefined reference to `_gpgrt_get_std_stream'
 [.]
 
 From a Google search, gpgrt_fclose, for example, is in libgpg-error.

You don't mention what platform you're on, but given your recent reports
in the debian BTS, i think you're using debian.  The package you're
probably looking for is libgpg-error-dev.

hth,

--dkg



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Installation

2014-12-18 Thread Fraser Tweedale
On Thu, Dec 18, 2014 at 09:34:40AM -0500, realhost...@safe-mail.net wrote:
 I can't install. Please help
 
 root@server1:/var/www/gnupg-2.0.26#  ./configure
 bash: ./configure: Permission denied
 root@server1:/var/www/gnupg-2.0.26# chmod -R 777 *
 root@server1:/var/www/gnupg-2.0.26#  ./configure
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for a thread-safe mkdir -p... /bin/mkdir -p
 checking for gawk... gawk
 checking whether make sets $(MAKE)... yes
 checking build system type... x86_64-unknown-linux-gnu
 checking host system type... x86_64-unknown-linux-gnu
 configure: autobuild project... gnupg
 configure: autobuild revision... 2.0.26
 configure: autobuild hostname... server1
 configure: autobuild timestamp... 20141218-193017
 checking for style of include used by make... GNU
 checking for gcc... no
 checking for cc... no
 checking for cl.exe... no
 configure: error: in `/var/www/gnupg-2.0.26':
 configure: error: no acceptable C compiler found in $PATH
 See `config.log' for more details
 
Hi,

A compiler cannot be found.  Do you have a C compiler installed?  If
so, which compiler (and operating system?)  If not, you could
install `gcc' and try again.

Cheers,

Fraser


pgpz03dUJx1v4.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: latest version build error

2014-12-18 Thread Daniel Kahn Gillmor
On 12/19/2014 01:35 AM, Joshua Rogers wrote:
 On 19/12/14 09:20, Daniel Kahn Gillmor wrote:
 You don't mention what platform you're on, but given your recent reports
 in the debian BTS, i think you're using debian.  The package you're
 probably looking for is libgpg-error-dev.
 I'm using
 ftp://ftp.gnupg.org/gcrypt/libgpg-error/libgpg-error-1.17.tar.gz , but
 still to no avail.
 
 Is that the right package?

how is it installed?  if you're using debian testing or unstable, it's
probably best to just do:

 apt-get install libgpg-error-dev

--dkg



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users