GnuPG Mini Howto - Revision history

Onnowpurbo: /* Exporting a public key */

2023-01-29T10:14:28Z

Exporting a public key

Onnowpurbo: /* Mempublikasi public key */

2020-12-11T13:25:31Z

Mempublikasi public key

Onnowpurbo at 02:51, 17 November 2020

2020-11-17T02:51:06Z

Onnowpurbo: /* =Detached Signature */

2020-11-17T02:43:19Z

=Detached Signature

Onnowpurbo: /* Encrypting dan Decrypting */

2020-10-13T01:11:17Z

Encrypting dan Decrypting

Onnowpurbo: /* Encrypting dan Decrypting */

2020-05-17T01:28:48Z

Encrypting dan Decrypting

Onnowpurbo: /* Encrypting dan Decrypting */

2020-05-17T01:28:24Z

Encrypting dan Decrypting

Onnowpurbo at 01:13, 17 May 2020

2020-05-17T01:13:39Z

Onnowpurbo: /* Encrypting dan Decrypting */

2017-06-11T11:43:39Z

Encrypting dan Decrypting

Onnowpurbo: /* Security Tips */

2017-06-11T11:36:47Z

Security Tips

@@ Line 214: / Line 214: @@
 To send your public key to a correspondent you must first export it. The command-line option --export is used to do this. It takes an additional argument identifying the public key to export. As with the --gen-revoke option, either the key ID or any part of the user ID may be used to identify the key to export.
-  alice% gpg --output alice.gpg --export alice@cyb.org
+  gpg --output alice.gpg --export alice@cyb.org
 The key is exported in a binary format, but this can be inconvenient when the key is to be sent though email or published on a web page. GnuPG therefore supports a command-line option --armor[1] that that causes output to be generated in an ASCII-armored format similar to uuencoded documents. In general, any output from GnuPG, e.g., keys, encrypted documents, and signatures, can be ASCII-armored by adding the --armor option.
-  alice% gpg --armor --export alice@cyb.org
+  gpg --armor --export alice@cyb.org
   -----BEGIN PGP PUBLIC KEY BLOCK-----
   Version: GnuPG v0.9.7 (GNU/Linux)
@@ Line 225: / Line 225: @@
   [...]
   -----END PGP PUBLIC KEY BLOCK-----
 ===Importing a public key===

← Older revision		Revision as of 13:25, 11 December 2020
Line 181:		Line 181:

	gpg --keyserver=x-hkp://pgp.mit.edu -a --send-keys <key-ID>		gpg --keyserver=x-hkp://pgp.mit.edu -a --send-keys <key-ID>
		+	gpg --keyserver=https://keys.openpgp.org:443 -a --send-keys <key-ID>
		+

	Karena saat ini anda hanya memiliki kunci sendiri di keyring anda, anda juga bisa menghapus deskripsi. Kemungkinan kedua adalah menggunakan antarmuka web. Di sana anda harus menyalin-paste kunci anda. Agar bisa menyalin kunci anda, berikut perintahnya:		Karena saat ini anda hanya memiliki kunci sendiri di keyring anda, anda juga bisa menghapus deskripsi. Kemungkinan kedua adalah menggunakan antarmuka web. Di sana anda harus menyalin-paste kunci anda. Agar bisa menyalin kunci anda, berikut perintahnya:

← Older revision		Revision as of 02:51, 17 November 2020
Line 197:		Line 197:

	gpg --search-keys <description>		gpg --search-keys <description>
		+
		+	==Exchange Keys==
		+
		+
		+	gpg --list-keys
		+
		+	/users/alice/.gnupg/pubring.gpg
		+	---------------------------------------
		+	pub 1024D/BB7576AC 1999-06-04 Alice (Judge) <alice@cyb.org>
		+	sub 1024g/78E9A8FA 1999-06-04
		+
		+	===Exporting a public key===
		+
		+	To send your public key to a correspondent you must first export it. The command-line option --export is used to do this. It takes an additional argument identifying the public key to export. As with the --gen-revoke option, either the key ID or any part of the user ID may be used to identify the key to export.
		+
		+	alice% gpg --output alice.gpg --export alice@cyb.org
		+
		+	The key is exported in a binary format, but this can be inconvenient when the key is to be sent though email or published on a web page. GnuPG therefore supports a command-line option --armor[1] that that causes output to be generated in an ASCII-armored format similar to uuencoded documents. In general, any output from GnuPG, e.g., keys, encrypted documents, and signatures, can be ASCII-armored by adding the --armor option.
		+
		+	alice% gpg --armor --export alice@cyb.org
		+	-----BEGIN PGP PUBLIC KEY BLOCK-----
		+	Version: GnuPG v0.9.7 (GNU/Linux)
		+	Comment: For info see http://www.gnupg.org
		+
		+	[...]
		+	-----END PGP PUBLIC KEY BLOCK-----
		+
		+
		+	===Importing a public key===
		+
		+	A public key may be added to your public keyring with the --import option.
		+
		+	alice% gpg --import blake.gpg
		+
		+	gpg: key 9E98BC16: public key imported
		+	gpg: Total number processed: 1
		+	gpg: imported: 1
		+
		+	alice% gpg --list-keys
		+
		+	/users/alice/.gnupg/pubring.gpg
		+	---------------------------------------
		+	pub 1024D/BB7576AC 1999-06-04 Alice (Judge) <alice@cyb.org>
		+	sub 1024g/78E9A8FA 1999-06-04
		+
		+	pub 1024D/9E98BC16 1999-06-04 Blake (Executioner) <blake@cyb.org>
		+	sub 1024g/5C8CBD41 1999-06-04
		+
		+	Once a key is imported it should be validated. GnuPG uses a powerful and flexible trust model that does not require you to personally validate each key you import. Some keys may need to be personally validated, however. A key is validated by verifying the key's fingerprint and then signing the key to certify it as a valid key. A key's fingerprint can be quickly viewed with the --fingerprint command-line option, but in order to certify the key you must edit it.
		+
		+	alice% gpg --edit-key blake@cyb.org
		+
		+	pub 1024D/9E98BC16 created: 1999-06-04 expires: never trust: -/q
		+	sub 1024g/5C8CBD41 created: 1999-06-04 expires: never
		+	(1) Blake (Executioner) <blake@cyb.org>
		+
		+	Command> fpr
		+	pub 1024D/9E98BC16 1999-06-04 Blake (Executioner) <blake@cyb.org>
		+	Fingerprint: 268F 448F CCD7 AF34 183E 52D8 9BDE 1A08 9E98 BC16
		+
		+	A key's fingerprint is verified with the key's owner. This may be done in person or over the phone or through any other means as long as you can guarantee that you are communicating with the key's true owner. If the fingerprint you get is the same as the fingerprint the key's owner gets, then you can be sure that you have a correct copy of the key.
		+
		+	After checking the fingerprint, you may sign the key to validate it. Since key verification is a weak point in public-key cryptography, you should be extremely careful and always check a key's fingerprint with the owner before signing the key.
		+
		+	Command> sign
		+
		+	pub 1024D/9E98BC16 created: 1999-06-04 expires: never trust: -/q
		+	Fingerprint: 268F 448F CCD7 AF34 183E 52D8 9BDE 1A08 9E98 BC16
		+
		+	Blake (Executioner) <blake@cyb.org>
		+
		+	Are you really sure that you want to sign this key
		+	with your key: "Alice (Judge) <alice@cyb.org>"
		+
		+	Really sign?
		+	Once signed you can check the key to list the signatures on it and see the signature that you have added. Every user ID on the key will have one or more self-signatures as well as a signature for each user that has validated the key.
		+
		+	Command> check
		+	uid Blake (Executioner) <blake@cyb.org>
		+	sig! 9E98BC16 1999-06-04 [self-signature]
		+	sig! BB7576AC 1999-06-04 Alice (Judge) <alice@cyb.org>
		+
		+
		+
		+
		+
		+

	==Personal Key-Ring Anda==		==Personal Key-Ring Anda==

@@ Line 328: / Line 328: @@
   gpg --clearsign doc
-===Detached Signature==
+===Detached Signature===
 Supaya tanda bisa terpisah

← Older revision		Revision as of 01:11, 13 October 2020
Line 307:		Line 307:

	Anda akan diminta password anda untuk membuka file. File yang didekrip disimpan dalam newdecryptedfile.		Anda akan diminta password anda untuk membuka file. File yang didekrip disimpan dalam newdecryptedfile.
		+
		+
		+
		+
		+	==Membuat dan Verifikasi Tanda Tangan Digital==
		+
		+	Membuat tanda tangan digital dari dokumen doc
		+
		+	gpg --output doc.sig --sign doc
		+
		+	Verifikasi dokumen dengan tanda tangan digital
		+
		+	gpg --output doc --decrypt doc.sig
		+
		+
		+	===Membuat Clear Sign===
		+
		+	Dokumen di tanda tangan, tapi tidak di enkripsi
		+
		+	gpg --clearsign doc
		+
		+	===Detached Signature==
		+
		+	Supaya tanda bisa terpisah
		+
		+	gpg --output doc.sig --detach-sig doc
		+
		+	Cek
		+
		+	gpg --verify doc.sig doc

	==How to set up pine for use with GPG==		==How to set up pine for use with GPG==

← Older revision		Revision as of 01:28, 17 May 2020
Line 307:		Line 307:

	Anda akan diminta password anda untuk membuka file. File yang didekrip disimpan dalam newdecryptedfile.		Anda akan diminta password anda untuk membuka file. File yang didekrip disimpan dalam newdecryptedfile.
−
−	Namun, ini tidak begitu mudah, jika anda harus menulis email anda terlebih dahulu, lalu mengenkripsinya, lalu akhirnya mengirimkannya. Dengan demikian, akan lebih mudah jika mail-program tahu bagaimana cara menangani gpg. Dan ini yang biasanya terjadi. Berikut ini berikut contoh program email pine.

	==How to set up pine for use with GPG==		==How to set up pine for use with GPG==

@@ Line 295: / Line 295: @@
   gpg -e -a -r <description> file
-Untuk mendekrip file anda lagi gunakan perintah berikut:
+<decription> di isi dengan Key-ID dari public key tujuan. Key-ID tersebut bisa di lihat di gpg --list-keys. Tambahkan 0x di depan key-id tersebut, misalnya 0x91AD85E1. Jika anda ingin meng-enkrip file untuk anda sendiri, makaanda harus menggunakan kunci publik anda sendiri.
- gpg -d -o newdecryptedfile file.asc/gpg
+Switch -a memastikan bahwa file output menggunakan format ASCII bukan biner dengan extension .asc.
-Anda akan diminta untuk frasa sandi anda. File yang didekrip disimpan dalam newdecryptedfile.
+Untuk mendekrip file yang di enkripsi menggunakan perintah berikut:
 Namun, ini tidak begitu mudah, jika anda harus menulis email anda terlebih dahulu, lalu mengenkripsinya, lalu akhirnya mengirimkannya. Dengan demikian, akan lebih mudah jika mail-program tahu bagaimana cara menangani gpg. Dan ini yang biasanya terjadi. Berikut ini berikut contoh program email pine.

← Older revision		Revision as of 01:13, 17 May 2020
Line 24:		Line 24:
	Untuk membuat pasangan kunci, anda harus mengambil shell dan menjalankan perintah berikut:		Untuk membuat pasangan kunci, anda harus mengambil shell dan menjalankan perintah berikut:

		+	gpg --full-generate-key
	gpg --gen-key		gpg --gen-key

@@ Line 304: / Line 304: @@
 Namun, ini tidak begitu mudah, jika anda harus menulis email anda terlebih dahulu, lalu mengenkripsinya, lalu akhirnya mengirimkannya. Dengan demikian, akan lebih mudah jika mail-program tahu bagaimana cara menangani gpg. Dan ini yang biasanya terjadi. Berikut ini berikut contoh program email pine.
-===How to set up pine for use with GPG===
+==How to set up pine for use with GPG==
 Pine offers the option to include additional filers to choose from just after you press Ctrl-x for "send your mail". We will show how to set these up in a second. However there is one small problem we have to solve beforehand: GPG always uses only one interface (gpg and all details are specified in the given options. In pine however you will not see the options, but just the name of the program. So, in order to be able to specify several different filters that you can distinguish, we have to introduce artificially some new names for gpg. First you have to find out where the gpg is situated:

@@ Line 342: / Line 342: @@
 Note that there are several clever programs to simplify the use of gpg with pine even more (see the links below).
-==Security Tips==
+==Tip Security==
-GPG is used by thousands of people (up to half a million already). Therefore, it is important that you show a certain care when using it. Mainly, it is really important that you only sign keys where you are absolutely sure that key and person belong together.
+GPG digunakan oleh ribuan orang (sampai setengah juta sudah). Oleh karena itu, penting bagi anda untuk menunjukkan penanganan tertentu saat menggunakannya. Terutama, sangat penting bahwa anda hanya menandatangani kunci di mana Anda aenar-benar yakin bahwa kunci dan orang tergabung bersama.
-However, the most important point one has to remember when using GPG is that one should NEVER enter the pass phrase by remote (rlogin, telnet, etc.; exception: ssh, as ssh encrypts the transmission to the other computer), and never on a computer which one does not know or is not logged in (it is really easy to find out what you have typed, even afterwards when you have left already!).
+Namun, hal yang paling penting yang harus diingat saat menggunakan GPG adalah anda tidak PERNAH memasukkan frase sandi secara remote (rlogin, telnet, dll; pengecualian: ssh, karena ssh mengenkripsi transmisi ke komputer lain), dan tidak pernah ada Komputer yang tidak diketahui atau tidak masuk (sangat mudah untuk mengetahui apa yang telah anda ketik, bahkan setelah anda sudah meninggalkannya!).
 ==Cara menggunakan revocation certificate==