Running_the_Software.mdwn 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738
  1. If you are logged in as the user who will manage the CA and have a graphical
  2. session, all you need to go is run TinyCA. On my system it doesn't have an entry
  3. in the application menu. If yours has, run it from there. Otherwise, you can
  4. run it from the command line (or Alt-F2):
  5. $ tinyca2
  6. For long term use, you can create a menu item easily. Graphical menu editors
  7. exist for several desktop environments (e.g. Alacarte for GNOME), in which you
  8. can add an entry, e.g. under the System category.
  9. If you created a new 'ca' user for managing the CA, here are the steps to get a
  10. graphical session in which you can run TinyCA as above.
  11. The new 'ca' user doesn't have password access. You'll need to become 'ca' by
  12. being root first. For commandline use, e.g. when using GnuTLS or OpenSSL
  13. directly, you can do as follows:
  14. $ su
  15. # su - ca
  16. Now you are 'ca' on that terminal. But we're going to use a GUI application for
  17. the CA management, which means you'll need to run the X server. This won't work
  18. with a terminal emulator, but you can do as follows. First read all the steps,
  19. before you start.
  20. 1. Press `Ctrl-Alt-F1` to open a new login shell. At any point, `Ctrl-Alt-F7`
  21. should take you back. However, at least for me, there's an X server error if
  22. I try to Ctrl-Alt-F7 and again Ctrl-Alt-F1 after X has been launched on the
  23. new F1 terminal. I suggest you try this once to see what happens. If there's
  24. an error, just reopen this page in the new shell so you don't need to go back
  25. here and can work with the new shell.
  26. 2. Log in as root (user is "root", then enter root password)
  27. 3. `# su - ca`
  28. 4. `$ startx`
  29. Now you can run TinyCA as explained above.