README 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143
  1. This directory contains a set of scripts which have been used on Linux
  2. as well as Solaris 2.x systems to initiate or maintain a connection
  3. with PPP. The files in this directory were contributed by Al Longyear
  4. (longyear@netcom.com) and Adi Masputra (adi.masputra@sun.com)
  5. ------------------------------------------------------------------------
  6. 1. README
  7. This file. You are reading it. It is just documentation.
  8. ------------------------------------------------------------------------
  9. 2. ppp-on
  10. This script will initiate a connection to the PPP system. It will run
  11. the chat program with the connection script as a parameter. This is a
  12. possible security hole. However, it is simple. It is meant to replace
  13. the previous version of ppp-on which was not very functional.
  14. The ppp-on script has entries for the account name, password, IP
  15. addresses, and telephone numbers. The parameters are passed to the
  16. pppd process and, then in turn, to the second part of the connect
  17. script, as a set of environment variables.
  18. Please make sure that you put the full path name to the ppp-on-dialer
  19. script in the reference to it in ppp-on.
  20. ------------------------------------------------------------------------
  21. 3. ppp-on-dialer
  22. This is the second part to the simple calling script, ppp-on. It
  23. executes the chat program to connect the user with a standard UNIX
  24. style getty/login connection sequence.
  25. ------------------------------------------------------------------------
  26. 4. callback
  27. This script may be used in lieu of the ppp-on-dialer to permit the
  28. common modem callback sequence. You may need to make changes to the
  29. expected prompt string for the modem.
  30. The script works by disabling the system's detection of the DCD
  31. condition and working on the modem status message "NO CARRIER" which
  32. is generated when the modem disconnects.
  33. It is crude. It does work for my modem connection. Use as you see fit.
  34. ------------------------------------------------------------------------
  35. 5. redialer
  36. The redialer script is a replacement for the ppp-on-dialer script. It
  37. will do 'attack dialing' or 'demon dialing' of one or more telephone
  38. numbers. The first number which responds will be used for a
  39. connection.
  40. There is a limit of ten attempts and a 15 second delay between dialing
  41. attempts. Both values are set in the script.
  42. ------------------------------------------------------------------------
  43. 6. ppp-off
  44. This is a script which will terminate the active ppp connection. Use
  45. as either "ppp-off" to terminate ppp0, or "ppp-off <device>" to
  46. terminate the connection on <device>. For example, "ppp-off ppp2" will
  47. terminate the ppp2 connection.
  48. ------------------------------------------------------------------------
  49. 7. secure-card
  50. This script was written by Jim Isaacson <jcisaac@crl.com>. It is a script
  51. for the 'expect' programming language used with Tcl. You need to have
  52. expect and Tcl installed before this script may be used.
  53. This script will operate with a device marketed under the name "SecureCARD".
  54. This little device is mated with its controller. On the credit card size
  55. device, there is a sequence number which changes on a random basis. In order
  56. for you to connect you need to enter a fixed portion of your account name
  57. and the number which is displayed on this card device. The number must match
  58. the value at the controller in order for the account name to be used.
  59. The problem is that chat uses fixed response strings. In addition, the
  60. timing for running the script may prevent the use of a script that reads the
  61. value before it starts the dial sequence. What was needed was a script which
  62. asked the user at the user's console at the time that it is needed.
  63. This led to the use of expect.
  64. ------------------------------------------------------------------------
  65. 8. ppp-on-rsh
  66. This script will initiate a PPP connection to a remote machine using rsh.
  67. This is implemented by creating a master/slave pseudo-tty with the slave
  68. pointing to rsh, specifically with the 'pty' and 'notty' options of pppd.
  69. It is assumed that the remote machine contains some sort of trust
  70. mechanisms (such as ~/.rhosts, et al) to allow the local machine to
  71. connect via rsh as root.
  72. ------------------------------------------------------------------------
  73. 9. ppp-on-ssh
  74. This script will initiate a PPP connection to a remote machine using the
  75. secure shell, or ssh. I've only tested this on ssh 1.x, so those of you
  76. who are running ssh 2.x mahy need to modify the ssh options slightly.
  77. This is implemented by creating a master/slave pseudo-ttyt with the slave
  78. pointing to ssh, specifically with the 'pty' and 'notty' options of pppd.
  79. It is assumed that the remote machine can accept the ssh connection from
  80. the local host, in the sense that all ssh authentication mechanisms have
  81. been properly configured, so that a remote root user can open a ssh
  82. connection.
  83. ------------------------------------------------------------------------
  84. 10. options-rsh-loc & options-rsh-rem
  85. These options files accompany the ppp-on-rsh script mentioned above. In
  86. theory, you'd want to copy the options-rsh-rem to the remote machine where
  87. in.rshd is running. The only extra option required on the remote machine
  88. options file is the 'notty' option. In addition, all ASCII control characters
  89. [0x00 to 0x1f], plus 0xff, are escaped. This may need to be modified
  90. depending on the rsh (or pseudo-tty) implementation which may differ across
  91. platforms, for further optimizations.
  92. ------------------------------------------------------------------------
  93. 11. options-ssh-loc & options-ssh-rem
  94. These options files accompany the ppp-on-ssh script mentioned above. I've
  95. only tested this on ssh 1.x, so those of you who are running ssh 2.x need
  96. to modify the ssh options slightly. In theory, you'd want to copy the
  97. options-ssh-rem to the remote machine where sshd daemon is running. The only
  98. extra options required on the remote machine options file is the 'notty'
  99. option. In addition, all ASCII control characters [0x00 to 0x1f], plus 0xff,
  100. are escaped. This may need to be modified depending on the ssh (or
  101. pseudo-tty) implementation which may differ across platforms, for further
  102. optimizations.