Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Mystic BBS  <--  <--- Return to Home Page
   Networked Database  Mystic BBS   [540 / 900] RSS
 From   To   Subject   Date/Time 
Message   Static    alaorjr   Re: A39 and SSH   June 6, 2018
 12:18 AM *  

 al> I have the same problem. Can anyone help?
 al> I use netrunner over Ubuntu 18.04 and return this message:
 al> SSH-2.0-cryptlib
 al> ,&#$@#Handshake failed

AFAIK Netrunner doesn't support SSH. If it's trying to make a plain telnet
connection to the SSH port then a handshake failure is to be expected.

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
 * Origin: Subcarrier BBS (1:249/400)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Mystic BBS  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0674 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_j8tk25vgjvcie9goruje9e7c87, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_j8tk25vgjvcie9goruje9e7c87, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_j8tk25vgjvcie9goruje9e7c87, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0