Add support for the SSH "none" auth method.
This is used by some BBSs to enable encryption without needing to integrate the BBS user base into their SSH server (and presumably so they don't need to run multiple SSH servers). All users log in with the same username (ie: "bbs") and no password is requested or required. Once the BBS starts, it prompts for the BBS user name and password as normal. In SyncTERM, the user/password/syspass fields are redefined as SSHuser/BBSuser/BBSpassword and they are moved around when you change the connection type. This means that if you change a listing that has a syspass to SSH (no auth) and back, the syspass is lost. I'm not sure if I plan to fix this or not.
Showing
- 3rdp/build/GNUmakefile 2 additions, 1 deletion3rdp/build/GNUmakefile
- 3rdp/build/cl-allow-none-auth.patch 158 additions, 0 deletions3rdp/build/cl-allow-none-auth.patch
- src/syncterm/bbslist.c 53 additions, 15 deletionssrc/syncterm/bbslist.c
- src/syncterm/conn.c 4 additions, 3 deletionssrc/syncterm/conn.c
- src/syncterm/conn.h 1 addition, 0 deletionssrc/syncterm/conn.h
- src/syncterm/ssh.c 32 additions, 17 deletionssrc/syncterm/ssh.c
- src/syncterm/st_crypt.c 5 additions, 0 deletionssrc/syncterm/st_crypt.c
- src/syncterm/st_crypt.h 2 additions, 0 deletionssrc/syncterm/st_crypt.h
- src/syncterm/term.c 6 additions, 4 deletionssrc/syncterm/term.c
Loading
Please register or sign in to comment