SecureCRT 9.0.0 軟體資訊交流 Mac

winXmac軟體社群 Mac 檔案傳輸分享 VanDyke Software, Inc. 未分類 Rate 90

SecureCRT for Mac,軟體教學,軟體下載,軟體社群,Windows軟體,Mac軟體

SecureCRT 9.0.0 Mac


適用於 Mac 的 SecureCRT 客戶端為計算專業人士提供了堅實的終端仿真工具,通過高級會話管理以及多種節省時間和簡化重複任務的方式提高了生產率。適用於 macOS 的 Secure CRT 為組織中的每個人提供安全的遠程訪問,文件傳輸和數據隧道傳輸。

無論您是要替換 Telnet 還是終端,還是需要功能更強大的安全遠程訪問工具,Secure CRT 都是您可以全天候使用的應用程序長。憑藉 SSH 的可靠安全性,廣泛的會話管理和高級腳本編寫功能,SecureCRT for Mac 將幫助您提高工作效率至第 n 級。

配色方案
包括 Solarized 在內的預定義配色方案可輕鬆更改終端工作區的外觀。

Tab 組
Tab 組可讓您在同一 SecureCRT 窗口中比較兩個會話的輸出以及與群組相關的會話的輸出,從而可以在更少的時間內完成更多工作時間。您可以在標籤中組織會話並在它們之間輕鬆切換。或者,您可以在一個選項卡中工作,同時監視另一個選項卡中命令的輸出,然後在命令完成後返回到單個選項卡組。

Emulations
可以從各種終端仿真中進行選擇,包括 TN3270,VT100,VT102,VT220,ANSI ,SCO ANSI,Wyse 50/60,Xterm 和 Linux 控制台 - 全部具有配色方案,並且大多數具有 ANSI 顏色支持。

按鈕 Bar
將按鈕映射到命令或操作,例如發送字符串,運行腳本,菜單功能和協議命令,或啟動外部程序,例如您喜歡的編輯器,cmd.exe 或 regedit。您可以為特定的會話或操作創建不同的按鈕欄,並為按鈕圖標分配顏色,以便於查看和組織。按鈕欄管理器允許您添加,複製,編輯,刪除,重命名和重新排列按鈕欄。

命令窗口
“命令”窗口為您提供了一種在將文本發送到遠程系統之前對其進行撰寫的方法。使用命令歷史記錄,您可以查看,編輯和發送以前的命令。 “立即發送字符”模式允許您在“命令”窗口中鍵入控製字符和轉義序列,以便您可以編輯文件,停止運行命令以及完成製表符。通過向所有連接的會話,所有可見的會話或特定的選項卡組發出命令,您甚至可以提高工作效率。

功能和亮點
從運行 Windows,Linux 和 Mac 的計算機上安全地訪問 UNIX,Linux 或 VMS 上的業務應用程序–對 VT100 / 102/220,TN3270,ANSI,SCO ANSI,Wyse 50/60,Xterm 和 Linux 控制台的仿真支持。通過完全控制回滾,鍵映射,顏色,字體等來配置,管理和組織所有會話 - 無論您有一個會話還是數千個會話。使用 SSH(SSH2,SSH1),Telnet,Telnet / TLS,串行和其他協議從一個客戶端訪問完整的網絡設備。利用具有節省時間的功能的高生產率 GUI,包括多會話啟動,選項卡式會話,選項卡組,平鋪式會話,克隆的會話,用於重複命令的按鈕欄和映射鍵。取決於開放標準的安全外殼(SSH)協議以獲取加密的登錄和會話數據,靈活的身份驗證選項以及 FIPS 140- 2 批准的可選密碼。通過使用 VBScript,JScript,PerlScript 或 Python 運行腳本來自動執行 Secure CRT 中的重複性任務。腳本記錄器將您的擊鍵構建為 VBScript 或 Python 腳本。使用 SFTP,Xmodem,Ymodem,Zmodem 或 Kermit 在網絡設備之間傳輸文件。內置的 TFTP 服務器提供了額外的文件傳輸靈活性。通過緊密集成程序和 SecureFX®文件傳輸客戶端,可以節省步驟,它們共享會話和設置,使您可以運行 SFTP,FTP,SCP 和 FTP / TLS 文件傳輸會話,而無需重新輸入密碼。注意:30 天試用版。

也可用:下載適用於 Windows 的 SecureCRT

檔案版本 SecureCRT 9.0.0
檔案名稱 scrt-9.0.0-2430.osx_x64.dmg
檔案大小
系統 macOS 10.12 Sierra or later
軟體類型 未分類
作者 VanDyke Software, Inc.
更新日期 https://www.vandyke.com/products/securecrt/index.html
軟體類型 2021-02-19
更新日誌

What's new in this version:

SecureCRT 9.0.0
Fixed:
- When a script was specified on the SecureCRT command line, the error "script is currently running" was incorrectly reported. The script did run after the dialog was dismissed
- Windows: If a user was denied remote desktop access on the target system, connecting with an RDP session silently failed without reporting the system error


SecureCRT 8.7.3
Bug fixes:
- When the sample ANSI color palette was shown for a color scheme, the colors displayed did not match the descriptive text for the color (e.g., "ANSI Red" text was displayed using the green color).
- The display of certain Unicode characters (e.g., emojis) inthe terminal could have caused other characters to appear as clipped
- Text displayed on the Keyboard Interactive and View Host Key dialogs could not be selected or copied
- When enabling logging via the File menu, connecting to a session caused logging to be toggled off


SecureCRT 8.7.2
Vulnerabilities addressed:
- When certain emulation functions received a large negative number as a parameter, it could have allowed the remote system to corrupt memory in the terminal process, potentially causing the execution of arbitrary code or a crash.

Bug fixes:
- If a script was launched from a button bar button or keymap shortcut and the script file could not be located, a misleading error was reported
- Mac: Attempting to authenticate using a YubiKey smartcard with the "opensc-pkcs11.so" library specified as the PKCS#11 provider resulted in an error, because the library could not be loaded.
- Mac: If the ZModem Upload List dialog was using the List view mode, which allows a folder to be expanded to display its contents, a file within an expanded folder could not be added to the upload list. Manager was expanded via the "Connect..." toolbar item, the Session Manager would briefly open, then immediately re-hide.
- Mac/Linux: If the Command Window option "Send Characters Immediately" was enabled, minimizing and restoring SecureCRT caused the option to be disabled


SecureCRT 8.7.1
New feature:
- Windows: Added an administrative policy that disallows the TFTP
server from being run

Changes:
- The performance of keyword highlighting has been improved to be as fast as and in many cases, much faster, than version 8.5.
- SecureCRT now handles the Xterm "paste bracketing" escape sequence so that indentation is correct when indented text is pasted into an editor
- Added an optional "hide output" parameter to the Session Object Lock() method
- SSH2: When doing public-key authentication, if there is no corresponding private-key file without an extension and there is a private-key file with a .ppk extension, it will be used.

Vulnerability addressed:
- TFTP: The TFTP server is off by default. However, when the TFTP server was running, SecureCRT was vulnerable to a directory traversal attack that allowed access to arbitrary files on the local system.

Bug fixes:
- When running a version of the Midnight Commander file manager that supports extended coordinate mouse clicks, mouse operations from within SecureCRT did not work
- When multiple screens were created using the "screen" utility, the scrollback from one screen could end up in the scrollback for a different screen
- When multiple screens were created using the "screen" utility, the man page output went to the scrollback buffer
- In the Manage Agent Keys dialog, the columns expanded every time the dialog opened, which eventually caused all column headers to disappear
- If two sessions were connected and then a session was sent to a new window, if the Hex view was opened, no data was displayed in the Hex view for the session
- The items "MENU_TOGGLE_KEYWORD_HIGHLIGHTING" and "MENU_CONNECT_LOCAL_SHELL" were not recognized when they were included in a custom .MNU file
- Windows: If folders were rearranged in the Command Manager, the folder order was not remembered when SecureCRT restarted
- Windows: If the Session Manager and Command Manager were unpinned (auto hide) and the Session Manager was pinned, the Command Manager became active
- Windows: Some of the arrow buttons in the Global and Session Options dialogs did not work correctly with screen readers, such as JAWS and NVDA


SecureCRT 8.7.0
Change:
- SSH2: Keyboard-interactive authentication works with a prompt that contains "password" with any combination of upper and lower case letters (e.g., "Password" or "PASSWORD").

Bug fixes:
- When an editor (e.g., vi or vim) was used to edit a file on the remote system, the wrong line could have been deleted when the delete line command was sent
- When a session with an authentication banner reconnected, extra newlines were inserted after the banner


SecureCRT 8.5.4
Changes:
- Updated the version of Python that ships with SecureCRT to 2.7.16

Bug Fixes:
- Windows: When using both the left and right mouse buttons to simulate a middle-button click, and the "Paste on middle button" option was enabled, the paste operation would not succeed


SecureCRT 8.5.3
Change:
- Treat the [email protected] key-exchange algorithm as
- Synonymous to the curve25519-sha256 algorithm.

Bug fixes:
- Under certain circumstances, tiled session did not resize correctly after resizing the Command window.
- If the default session protocol was set to something other than TAPI and the Quick Connect protocol was changed to TAPI, attempting to configure TAPI produced an error.
- If the Screen.get2() scripting function was called, line drawing characters in the terminal window could be corrupted.
- When a large scrollback buffer was configured, the scroll bar could get stuck at the top of the scrollback.
- SecureCRT now prevents multiple Connect bars from being added to the toolbar.
- SSH2: If the public key in use was generated with the ssh-keygen Z option, SecureCRT could crash when attempting to enter the passphrase.
- When SecureCRT was maximized or full screen, if the font was zoomed in using CTRL+ or the mouse wheel, attempting to zoom out using CTRL- or the mouse wheel did not work.
- If Python 3.x was installed on the system and the PYTHONPATH variable was set, SecureCRT could fail to launch.
- When "Background colors" tab status indicators were used and enough sessions to fill the tab bar were connected, there was a significant lag when connecting new sessions or closing sessions.


SecureCRT 8.5.2
New feature:
- Added support for the curve25519-sha256 key-exchange algorithm.

Bug fixes:
- If an OpenSSH format key was manually added to the host key database, SecureCRT crashed when attempting to connect to a host that used that key.
- If the Session Manager was pinned and the active session had keyword highlighting on and it was toggled off by selecting "Keyword
- Highlighting" from the Options menu and then the Session Manager was hidden, keyword highlighting was re-enabled.
- Windows: In the Command Window, if the option "Send Characters
- Immediately" was set, pressing CTRL+A selected all the text in the
- Command Window instead of sending the CTRL+A to the session(s).
- Windows: When using the mouse wheel to scroll session output, there was a dead spot in the terminal area where scrolling stopped if the mouse cursor was positioned there.
- Windows: Attempting to display the Activator's About box caused an error message to be displayed.
- Mac/Linux: If the Session Manager was undocked and redocked, the terminal area size changed.
- Mac: SecureCRT could crash if a session had a dependent session and the wrong password had been saved for both sessions and the wrong password was entered when attempting to connect to the session.
- Mac: If CTRL+ was used to select multiple folders in the
- Session Manager or Connect dialog and then arrow keys were pressed, the selection could not be cleared.
- Linux: On Ubuntu 18.x, when running Midnight Commander, if CTRL+O was used to show and hide panels until there was no command prompt and then Midnight Commander was restarted as root and CTRL+O was used to hide panels, the command prompt was at the top of the window and new output was displayed incorrectly.


SecureCRT 8.5.1
New feature:
- Added a new script function FileSaveDialog() that allows saving to
- a file that does not exist.

Bug fixes:
- If the command line specified a saved session (/S) and overrode the local listening IP address (/LOCAL), an error was reported and the session did not connect.
- The button bar list was empty if button bars were imported when the button bar list was not displayed and then the button bar was displayed.
- Windows: On Windows Server 2008 R2, the icons in the Session Manager and Connect dialog were not drawn correctly.
- Windows: On a high-DPI monitor scaled to 125%, the 10-point Lucida
- Console font looked larger and bold compared to how that font looked in other applications.


SecureCRT 8.5
Bug fix:
- SecureCRT could crash if a new folder was created in the Session Manager or Connect dialog and there was at least one other folder under "Sessions" and then sorting was changed to manual arrangement and a session was dragged to be between the "Session" folder and the top folder

檔案下載 檔案下載