cpu 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161
  1. .TH CPU 1
  2. .SH NAME
  3. cpu \- connection to cpu server
  4. .SH SYNOPSIS
  5. .B cpu
  6. [
  7. .B -h
  8. .I server
  9. ] [
  10. .B -a
  11. .I auth-method
  12. ] [
  13. .B -e
  14. .I encryption-hash-algs
  15. ] [
  16. .B -k
  17. .I keypattern
  18. ] [
  19. .B -c
  20. .I cmd args ...
  21. ]
  22. .SH DESCRIPTION
  23. .I Cpu
  24. starts an
  25. .IR rc (1)
  26. running on the
  27. .I server
  28. machine, or the machine named in the
  29. .B $cpu
  30. environment variable if there is no
  31. .B -h
  32. option.
  33. .IR Rc 's
  34. standard input, output, and error files will be
  35. .B /dev/cons
  36. in the name space where the
  37. .I cpu
  38. command was invoked.
  39. Normally,
  40. .I cpu
  41. is run in an
  42. .IR rio (1)
  43. window on a terminal, so
  44. .IR rc
  45. output goes to that window, and input comes from the keyboard
  46. when that window is current.
  47. .IR Rc 's
  48. current directory is
  49. the working directory of the
  50. .I cpu
  51. command itself.
  52. .PP
  53. The name space for the new
  54. .I rc
  55. is an analogue of the name space where the
  56. .I cpu
  57. command was invoked:
  58. it is the same except for architecture-dependent bindings such as
  59. .B /bin
  60. and the use of fast paths to file servers, if available.
  61. .PP
  62. If a
  63. .B -c
  64. argument is present, the remainder of the command line is executed by
  65. .I rc
  66. on the server, and then
  67. .I cpu
  68. exits.
  69. .PP
  70. The
  71. .B -a
  72. command allows the user to specify the authentication mechanism used
  73. when connecting to the remote system. The two possibilities for
  74. .I auth-method
  75. are:
  76. .TF netkey
  77. .TP
  78. .B p9
  79. This is the default. Authentication is done using the standard Plan 9
  80. mechanisms, (see
  81. .IR authsrv (6)).
  82. No user interaction is required.
  83. .TP
  84. .B netkey
  85. Authentication is done using challenge/response and a hand held
  86. authenticator or the
  87. .I netkey
  88. program
  89. (see
  90. .IR passwd (1)).
  91. The user must encrypt the challenge and type the encryption
  92. back to
  93. .IR cpu .
  94. This is used if the local host is in a different protection domain than
  95. the server or if the user wants to log into the server as a different
  96. user.
  97. .PD
  98. .PP
  99. The
  100. .B -e
  101. option specifies an encryption and/or hash algorithm to
  102. use for the connection. If both are specified, they must
  103. be space separated and comprise a single argument, so they
  104. must be quoted if in a shell command. The default is
  105. .L rc4_256
  106. encryption and
  107. .L sha1
  108. hashing. See
  109. .IR ssl (3)
  110. for details on possible algorithms. The argument
  111. .L clear
  112. specifies no encryption algorithm and can be used to talk
  113. to older versions of the
  114. .B cpu
  115. service.
  116. .PP
  117. The
  118. .B -k
  119. flag specifies a key pattern to use to restrict the keys
  120. selected by the
  121. .I auth_proxy
  122. call used for authentication.
  123. .PP
  124. The name space is built by running
  125. .B /usr/$user/lib/profile
  126. with the root of the invoking name space bound to
  127. .BR /mnt/term .
  128. The
  129. .B service
  130. environment variable is set to
  131. .BR cpu ;
  132. the
  133. .B cputype
  134. and
  135. .B objtype
  136. environment variables reflect the server's architecture.
  137. .SH FILES
  138. The name space of the terminal side of the
  139. .B cpu
  140. command is mounted, via
  141. .IR exportfs (4),
  142. on the CPU side on directory
  143. .BR /mnt/term .
  144. The files such as
  145. .B /dev/cons
  146. are bound to their standard locations from there.
  147. .SH SOURCE
  148. .B /sys/src/cmd/cpu.c
  149. .SH SEE ALSO
  150. .IR rc (1) ,
  151. .IR rio (1)
  152. .SH BUGS
  153. Binds and mounts done after the terminal
  154. .B lib/profile
  155. is run are not reflected in the new name space.
  156. .PP
  157. When using the
  158. .B -a
  159. option to `log in' as another user, be aware that
  160. resources in the local name space will be made
  161. available to that user.