From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1J6YC6-0006Y0-TT for garchives@archives.gentoo.org; Sun, 23 Dec 2007 21:17:11 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lBNLGKKY020531; Sun, 23 Dec 2007 21:16:20 GMT Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.189]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lBNLGJpS020518 for ; Sun, 23 Dec 2007 21:16:20 GMT Received: by fk-out-0910.google.com with SMTP id 18so2563866fkq.2 for ; Sun, 23 Dec 2007 13:16:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date:user-agent:x-face:mime-version:content-type:content-transfer-encoding:message-id; bh=i6XrKGTAK23viNc8aUfWK5GzEKSu9Eo1/WPwUcNHNTs=; b=giFfPIFk2guVNJDaInSwz4VMnf12oZwGASG2UslEcNowIrGiW+82rSUrQXcK496w+6r/sxKLDQKf3J4wq/pyYs2CJaoLMvJHkLKL63vYc9JSHKR4qcfapajld8QqMDZBhHcKm4tlUbRU6KRz00yNNYmSjShOnCsHwbfx6g6Dvig= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:x-face:mime-version:content-type:content-transfer-encoding:message-id; b=tPwOXeMXtwhlYM41Vvs4C/00GPDr2GAmqefQIOoHcVaR4icqpxUiSC7OuRMKLhCcnSsPpcbdwaGP9OsvcEJvMv/aP7CSOlZxOB8syLP7XZtYDkSAmB4kcYxLVJJovOmc+dDN6Gvk0UGOaZ6anJk2Rym/o9OtcMNbr5/y2cYSB3c= Received: by 10.82.155.10 with SMTP id c10mr6940842bue.39.1198444579250; Sun, 23 Dec 2007 13:16:19 -0800 (PST) Received: from buzzja.mine.nu ( [89.190.234.75]) by mx.google.com with ESMTPS id i5sm10630829mue.7.2007.12.23.13.16.15 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 23 Dec 2007 13:16:16 -0800 (PST) From: "Ez0Tr@nK" To: gentoo/user/ru Subject: [gentoo-user-ru] pgp-agent Date: Sun, 23 Dec 2007 23:16:07 +0200 User-Agent: KMail/1.9.7 X-Face: #c_^!ZAby+Q,(`PggFTSvdMll^:),+SWon6VcH%g~5Dj6CgQNR:Y[YfL#9TOI&/(=?utf-8?q?=5BH=7Dc2e=0A=09K?=@ki"I$h8fOg!Le5F{rh0xq9m',o7Jj:ym5lA'lJ*CJ!-)2X6KigI\RC|CSL?cN"=?utf-8?q?PN=26vX3=0A=09dTaaQ=5E?=>5>Llmu_vt~pCI7.ee|{iSb'`X=Xp:>=X]#[c:3k/yf|6+Ac5DNQQPwU~Yg7< Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user-ru@gentoo.org Reply-To: gentoo-user-ru@gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2364806.rJ4U1oaWme"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712232316.10480.ezotrank@gmail.com> X-Archives-Salt: 91d053b1-37bb-4c99-9725-f5c986ee0372 X-Archives-Hash: 41ec5bd3ee93572e058a1f707050d89c --nextPart2364806.rJ4U1oaWme Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline =D0=92 =D0=BE=D0=B1=D1=89=D0=B5=D0=BC =D0=BF=D1=80=D0=BE=D0=B1=D0=BB=D0=B5= =D0=BC=D0=BC=D0=B0 =D1=82=D0=B0=D0=BA=D0=B0=D1=8F =D0=BD=D0=B5 =D0=BA=D0=B0= =D0=BA =D0=BD=D0=B5 =D0=BC=D0=BE=D0=B3=D1=83 =D1=8F =D0=B5=D0=B3=D0=BE =D0= =BF=D0=BE=D0=B4=D0=BD=D1=8F=D1=82=D1=8C. =D0=AF =D1=85=D0=BE=D1=87=D1=83 =D1=87=D1=82=D0=BE =D0=B1=D1=8B =D0=BF=D1= =80=D0=B8 =D0=BF=D0=BE=D0=BB=D1=83=D1=87=D0=B5=D0=BD=D0=B8=D0=B5 =D1=88=D0= =B8=D1=84=D1=80=D0=BE=D0=B2=D0=B0=D0=BD=D0=BD=D0=BE=D0=B3=D0=BE =D1=81=D0= =BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D1=8F =D0=B2 PSI =D0=BC=D0=BD=D0=B5= =D0=BD=D0=B5 =D0=BF=D1=80=D0=B8=D1=85=D0=BE=D0=B4=D0=B8=D0=BB=D0=BE=D1=81= =D1=8C=20 =D0=BA=D0=B0=D0=B6=D0=B4=D1=8B=D0=B9 =D1=80=D0=B0=D0=B7 =D0=B2=D0=B1=D0=B8= =D0=B2=D0=B0=D1=82=D1=8C =D0=BF=D0=B0=D1=80=D0=BE=D0=BB=D1=8C. gpg-agent gpg-agent gpg-agent[19598]: can't connect to `/home/ezotrank/.gnupg/S.gpg-agent':=20 Connection refused gpg-agent: no gpg-agent running in this session cat .gnupg/gpg.conf # Options for GnuPG # Copyright 1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, In= c. # # This file is free software; as a special exception the author gives # unlimited permission to copy and/or distribute it, with or without # modifications, as long as this notice is preserved. # # This file is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY, to the extent permitted by law; without even the # implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # # Unless you specify which option file to use (with the command line # option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf # by default. # # An options file can contain any long options which are available in # GnuPG. If the first non white space character of a line is a '#', # this line is ignored. Empty lines are also ignored. # # See the man page for a list of options. # Uncomment the following option to get rid of the copyright notice #no-greeting # If you have more than 1 secret key in your keyring, you may want to # uncomment the following option and set your preferred keyid. #default-key 621CC013 # If you do not pass a recipient to gpg, it will ask for one. Using # this option you can encrypt to a default key. Key validation will # not be done in this case. The second form uses the default key as # default recipient. #default-recipient some-user-id #default-recipient-self # By default GnuPG creates version 3 signatures for data files. This # is not strictly OpenPGP compliant but PGP 6 and most versions of PGP # 7 require them. To disable this behavior, you may use this option # or --openpgp. #no-force-v3-sigs # Because some mailers change lines starting with "From " to ">From " # it is good to handle such lines in a special way when creating # cleartext signatures; all other PGP versions do it this way too. # To enable full OpenPGP compliance you may want to use this option. #no-escape-from-lines # When verifying a signature made from a subkey, ensure that the cross # certification "back signature" on the subkey is present and valid. # This protects against a subtle attack against subkeys that can sign. # Defaults to --no-require-cross-certification. However for new # installations it should be enabled. require-cross-certification # If you do not use the Latin-1 (ISO-8859-1) charset, you should tell # GnuPG which is the native character set. Please check the man page # for supported character sets. This character set is only used for # metadata and not for the actual message which does not undergo any # translation. Note that future version of GnuPG will change to UTF-8 # as default character set. #charset utf-8 # Group names may be defined like this: # group mynames =3D paige 0x12345678 joe patti # # Any time "mynames" is a recipient (-r or --recipient), it will be # expanded to the names "paige", "joe", and "patti", and the key ID # "0x12345678". Note there is only one level of expansion - you # cannot make an group that points to another group. Note also that # if there are spaces in the recipient name, this will appear as two # recipients. In these cases it is better to use the key ID. #group mynames =3D paige 0x12345678 joe patti # Some old Windows platforms require 8.3 filenames. If your system # can handle long filenames, uncomment this. #no-mangle-dos-filenames # Lock the file only once for the lifetime of a process. If you do # not define this, the lock will be obtained and released every time # it is needed - normally this is not needed. #lock-once # GnuPG can send and receive keys to and from a keyserver. These # servers can be HKP, email, or LDAP (if GnuPG is built with LDAP # support). # # Example HKP keyserver: # hkp://subkeys.pgp.net # # Example email keyserver: # mailto:pgp-public-keys@keys.pgp.net # # Example LDAP keyservers: # ldap://pgp.surfnet.nl:11370 # ldap://keyserver.pgp.com # # Regular URL syntax applies, and you can set an alternate port # through the usual method: # hkp://keyserver.example.net:22742 # # If you have problems connecting to a HKP server through a buggy http # proxy, you can use keyserver option broken-http-proxy (see below), # but first you should make sure that you have read the man page # regarding proxies (keyserver option honor-http-proxy) # # Most users just set the name and type of their preferred keyserver. # Note that most servers (with the notable exception of # ldap://keyserver.pgp.com) synchronize changes with each other. Note # also that a single server name may actually point to multiple # servers via DNS round-robin. hkp://subkeys.pgp.net is an example of # such a "server", which spreads the load over a number of physical # servers. keyserver hkp://subkeys.pgp.net #keyserver mailto:pgp-public-keys@keys.nl.pgp.net #keyserver ldap://pgp.surfnet.nl:11370 #keyserver ldap://keyserver.pgp.com # Common options for keyserver functions: # # include-disabled =3D when searching, include keys marked as "disabled" # on the keyserver (not all keyservers support this). # # no-include-revoked =3D when searching, do not include keys marked as # "revoked" on the keyserver. # # verbose =3D show more information as the keys are fetched. # Can be used more than once to increase the amount # of information shown. # # use-temp-files =3D use temporary files instead of a pipe to talk to the # keyserver. Some platforms (Win32 for one) always # have this on. # # keep-temp-files =3D do not delete temporary files after using them # (really only useful for debugging) # # honor-http-proxy =3D if the keyserver uses HTTP, honor the http_proxy # environment variable # # broken-http-proxy =3D try to work around a buggy HTTP proxy # # auto-key-retrieve =3D automatically fetch keys as needed from the keyserv= er # when verifying signatures or when importing keys that # have been revoked by a revocation key that is not # present on the keyring. # # no-include-attributes =3D do not include attribute IDs (aka "photo IDs") # when sending keys to the keyserver. keyserver-options auto-key-retrieve include-disabled include-revoked # Uncomment this line to display photo user IDs in key listings and # when a signature from a key with a photo is verified. #show-photos # Use this program to display photo user IDs # # %i is expanded to a temporary file that contains the photo. # %I is the same as %i, but the file isn't deleted afterwards by GnuPG. # %k is expanded to the key ID of the key. # %K is expanded to the long OpenPGP key ID of the key. # %t is expanded to the extension of the image (e.g. "jpg"). # %T is expanded to the MIME type of the image (e.g. "image/jpeg"). # %f is expanded to the fingerprint of the key. # %% is %, of course. # # If %i or %I are not present, then the photo is supplied to the # viewer on standard input. If your platform supports it, standard # input is the best way to do this as it avoids the time and effort in # generating and then cleaning up a secure temp file. # # The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" # On Mac OS X and Windows, the default is to use your regular JPEG image # viewer. # # Some other viewers: # photo-viewer "qiv %i" # photo-viewer "ee %i" # photo-viewer "display -title 'KeyID 0x%k'" # # This one saves a copy of the photo ID in your home directory: # photo-viewer "cat > ~/photoid-for-key-%k.%t" # # Use your MIME handler to view photos: # photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" use-agent cat .gnupg/gpg-agent.conf pinentry-program /usr/bin/pinentry-qt no-grab default-cache-ttl 1800 =2D-=20 =2D- With best regards, ezotrank kernel 2.6.23-gentoo-r2, system uptime: 23:13:32 up 6:19, 3 users, load=20 average: 0.04, 0.11, 0.11 =2D- --nextPart2364806.rJ4U1oaWme Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBHbtAaaUhfBqOT/NcRAr9pAJ9EklLolVO8EtMxsB/8sKZwRtfxZgCeMtrL SzBtJRY9M9PjYA++Xfk41ic= =9llo -----END PGP SIGNATURE----- --nextPart2364806.rJ4U1oaWme--