README 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108
  1. _ _
  2. __ _| |_| | ___ __ __ _ ___ _ __ ___ __ _ _ __
  3. / _` | __| |/ / '_ \ / _` / __| '_ ` _ \ / _` | '_ \
  4. | (_| | |_| <| |_) | (_| \__ \ | | | | | (_| | | | |
  5. \__, |\__|_|\_\ .__/ \__,_|___/_| |_| |_|\__,_|_| |_|
  6. |___/ |_|
  7. -----------
  8. What is it?
  9. -----------
  10. It is a graphical interface to manage the usage of passwords related to servers
  11. or services, grouped by customers (plateforms, etc.) The purpose is to provide
  12. system and network administrators a convenient tool to manage a passwords
  13. knowledge base related to customers, servers, services... It can help to
  14. retrieve passwords, or even connect to servers (ssh, telnet, ftp...) Unix, C
  15. compiler, GTK+ libraries are required in addition to gnupg. Passwords must be
  16. kept in a gnupg crypted file. The structure of the file is predefined, but
  17. very easy to edit and maintain.
  18. ---------------
  19. What is needed?
  20. ---------------
  21. - C compiler
  22. - GTK+ libraries (gtkpasman v>0.9 need versions 2 or 3.x)
  23. - gnupg (pgp should work)
  24. ------------------------
  25. Where does it come from?
  26. ------------------------
  27. gtkpasman was a project based on gpasman (project of Olivier Sessink) The RC2
  28. crypted method has been replaced by calls to gnupg. The encryption is now
  29. external to the application.
  30. As the 'Eye view' and its menus have been removed, the application is now
  31. completely distinct.
  32. -----------------
  33. How does it work?
  34. -----------------
  35. Typical use:
  36. - Edit a password file (see format below)
  37. - crypt the password file with your gpg key:
  38. gpg --encrypt --no-encrypt-to --recipient YOURKEYID gpasman4.sample
  39. - remove uncrypted file
  40. - launch gtkpasman:
  41. gtkpasman gpasman4.sample.gpg
  42. Buttons under the list of accounts on servers, help you to connect:
  43. - you can have the password copied in the paste buffer. (Convenient if you
  44. just want to enter it in an HTTP, ldap, or any kind of authentication)
  45. - launching xterm-like program of your choice; just point a server or a user
  46. on a service in the list, and you are connected, paste password with
  47. middle-clic or paste shortcut and you are in.
  48. - alternately, you can just launch an xterm, if you use ssh keys and do not
  49. need to enter passwords for some servers. gtkpasman just helps you to group
  50. servers by customers in this case
  51. - when multiple selection is made, gtkpasman tries to launch a specific
  52. command for ssh targets, so that you can use multiplexers programs like
  53. cluster-ssh (cssh) on your selection.
  54. There is also a search field to find out a server/group/customer in the list.
  55. The password file should contain one line per password; The format of a line
  56. in the encrypted file must be the same as the following:
  57. - ";" is the separator
  58. - spaces at start and end are allowed
  59. - empty fields are allowed
  60. - no separator is required for the last field (password)
  61. - field names are in order:
  62. customer, group, server, service, serviceplus, user, password
  63. A sample file:
  64. see src/gpasman4.sample
  65. This file would give a represented tree like this :
  66. +customer1
  67. +Group 1
  68. | +srvA
  69. | | +ssh
  70. | | +root2
  71. | +srvB
  72. | +ssh
  73. | +root
  74. +Group 2
  75. +srvC
  76. +ssh
  77. +root
  78. +customer2
  79. +Group 1
  80. +srvD
  81. +ssh
  82. +root
  83. +acc
  84. +customer3
  85. +Group A
  86. +srvE
  87. | +ssh
  88. | +port 322
  89. | +root
  90. +srvF
  91. +ssh
  92. +port 322
  93. +root