Beta 3.0

Introducing

• New command style. Pull Request #29, #33.
• License notices. Pull Request #39.
• New Commands - license, license notice, pwd, computehash. Pull Request #39, #41, #50.
• New Documentation. Pull Request #44.
• In-depth tab completion. Pull Request #49.

Fixes

• Passwords are shown in clear text. Issue #30.
• show is checking connection with password nicknames too. Issue #32.
• Could not find a part of the path "C:\path\to\swsh\swsh-data". Issue #43.
• Fix cd. Issue #48.

Enhancements

• Made clear and exit independent commands. Commit b0e3114.
• Code Cleanup. Pull Request #38, #45.
• Url management. Pull Request #40.
• New method for connection. Pull Request #46.
• Remove unnecessary code. Pull Request #47.
• New help output. Commit c8678d4.

---

Notes

Reason for commits 8531cf1, 3c06de0 and ec6db79 is to make SWSH a program that multiple users can run. If installed via an installer (currently in development), SWSH creates data files, i.e., swsh-data/*.swsh, swsh_history and SSH keys (by default), in its local directory, which would be the installation path, and that makes it vulnerable. Sometimes, it requires "root/admin" privileges to run and create data files.

If you want to keep your data files from previous versions, I suggest you to manually move everything you have on SWSH's directory, except *.dll and *.exe to %appdata%/SWSH. BUT before doing that, make sure you ran the new version of SWSH (after the commits mentioned above) at least once or ran these commands in Command Prompt to make SWSH's directory in your %appdata% folder.

cd %appdata%
mkdir SWSH

%appdata% should resolve to C:\Users\YOUR-USERNAME\AppData\Roaming

Contributors

• Nabeel Omer - @nabeelomer
  • Pull Request #35

For more details, visit

• Project #1
• Milestone #4
• Pull Request #28