Acasă Explorează Ajutor
Înregistrare Autentificare
Apq
/
winscp
oglindă de https://github.com/winscp/winscp.git
1
0
Bifurcare 0
Fisiere Probleme 0 Wiki
Arbore: 14d17481b3
Ramuri Etichete
winscp
/
source
/
putty
/
doc
/
sshnames.but

sshnames.but 2.5 KB
Istoric Crud

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 
  1. \A{sshnames} SSH-2 names specified for PuTTY
    2. 

  2. 

  3. There are various parts of the SSH-2 protocol where things are specified
    4. 

  4. using a textual name.  Names ending in \cw{@putty.projects.tartarus.org}
    5. 

  5. are reserved for allocation by the PuTTY team.  Allocated names are
    6. 

  6. documented here.
    7. 

  7. 

  8. \H{sshnames-channel} Connection protocol channel request names
    9. 

  9. 

  10. These names can be sent in a \cw{SSH_MSG_CHANNEL_REQUEST} message.
    11. 

  11. 

  12. \dt \cw{[email protected]}
    13. 

  13. 

  14. \dd This is sent by a client to announce that it will not have more than
    15. 

  15. one channel open at a time in the current connection (that one being
    16. 

  16. the one the request is sent on).  The intention is that the server,
    17. 

  17. knowing this, can set the window on that one channel to something very
    18. 

  18. large, and leave flow control to TCP.  There is no message-specific data.
    19. 

  19. 

  20. \dt \cw{[email protected]}
    21. 

  21. 

  22. \dd PuTTY sends this request along with some
    23. 

  23. \cw{SSH_MSG_CHANNEL_WINDOW_ADJUST} messages as part of its window-size
    24. 

  24. tuning.  It can be sent on any type of channel.  There is no
    25. 

  25. message-specific data. Servers MUST treat it as an unrecognised request
    26. 

  26. and respond with \cw{SSH_MSG_CHANNEL_FAILURE}.
    27. 

  27. 

  28. \lcont{
    29. 

  29. (Some SSH servers get confused by this message, so there is a
    30. 

  30. bug-compatibility mode for disabling it. See \k{config-ssh-bug-winadj}.)
    31. 

  31. }
    32. 

  32. 

  33. \H{sshnames-kex} Key exchange method names
    34. 

  34. 

  35. \dt \cw{[email protected]}
    36. 

  36. 

  37. \dt \cw{[email protected]}
    38. 

  38. 

  39. \dt \cw{[email protected]}
    40. 

  40. 

  41. \dt \cw{[email protected]}
    42. 

  42. 

  43. \dt \cw{[email protected]}
    44. 

  44. 

  45. \dt \cw{[email protected]}
    46. 

  46. 

  47. \dt \cw{[email protected]}
    48. 

  48. 

  49. \dt \cw{[email protected]}
    50. 

  50. 

  51. \dt \cw{[email protected]}
    52. 

  52. 

  53. \dt \cw{[email protected]}
    54. 

  54. 

  55. \dt \cw{[email protected]}
    56. 

  56. 

  57. \dd These appeared in various drafts of what eventually became RFC\_4432.
    58. 

  58. They have been superseded by \cw{rsa1024-sha1} and \cw{rsa2048-sha256}.
    59. 

  59. 

  60. \H{sshnames-encrypt} Encryption algorithm names
    61. 

  61. 

  62. \dt \cw{[email protected]}
    63. 

  63. 

  64. \dt \cw{[email protected]}
    65. 

  65. 

  66. \dd These were used in drafts of what eventually became RFC\_4345.
    67. 

  67. They have been superseded by \cw{arcfour128} and \cw{arcfour256}.
    68.