Cum sa faci un server SSH & HTTPS

[FearDotCom]

Multi m-au intrebat daca se poate face un server SSH (nologin) sau HTTPS pe Windows

Tutorialul l-am facut in format PDF pt ca am vazut pe alte forumuri tutoriale scrise de mine si postate de altii si se lauda ca ei au facut tutorialul respectiv

Tutorialu il poti descarca de pe unu din link-urile:

Link 1. Cum sa faci un server SSH & HTTPS.pdf 2shared - download

Link 2. Download Cum sa faci un server SSH & HTTPS.pdf - FisierulMeu.ro

Link 3. ShareMobile - File Info

[SirXulescu]

Fear :

client connection closed before completion of protocol

. Rezolvare?

09:01:56.056 Accepted SOCKS5 connection from 127.0.0.1:1434 to 206.82.210.25:443.
09:02:02.002 Closing SOCKS5 connection from 127.0.0.1:1436, sent: 0, received: 0.
09:02:02.002 SOCKS5 connection from 127.0.0.1:1436 failed: Client connection closed before completion of protocol.
09:02:21.021 Accepted SOCKS5 connection from 127.0.0.1:1438 to 125.252.224.82:80.
09:02:24.024 Accepted SOCKS5 connection from 127.0.0.1:1440 to 72.14.221.136:80.
09:02:28.028 Closing SOCKS5 connection from 127.0.0.1:1442, sent: 0, received: 0.
09:02:28.028 SOCKS5 connection from 127.0.0.1:1442 failed: Client connection closed before completion of protocol.
09:02:29.029 Closing SOCKS5 connection from 127.0.0.1:1444, sent: 0, received: 0.
09:02:29.029 SOCKS5 connection from 127.0.0.1:1444 failed: Client connection closed before completion of protocol.
09:02:29.029 Closing SOCKS5 connection from 127.0.0.1:1446, sent: 0, received: 0.
09:02:30.030 SOCKS5 connection from 127.0.0.1:1446 failed: Client connection closed before completion of protocol.
09:02:30.030 Closing SOCKS5 connection from 127.0.0.1:1448, sent: 0, received: 0.
09:02:30.030 SOCKS5 connection from 127.0.0.1:1448 failed: Client connection closed before completion of protocol.
09:02:36.036 Closing SOCKS5 connection from 127.0.0.1:1440, sent: 653, received: 178.
09:02:48.048 Closing SOCKS5 connection from 127.0.0.1:1450, sent: 0, received: 0.
09:02:48.048 SOCKS5 connection from 127.0.0.1:1450 failed: Client connection closed before completion of protocol.
09:02:49.049 Closing SOCKS5 connection from 127.0.0.1:1452, sent: 0, received: 0.
09:02:49.049 SOCKS5 connection from 127.0.0.1:1452 failed: Client connection closed before completion of protocol.
09:02:50.050 Closing SOCKS5 connection from 127.0.0.1:1454, sent: 0, received: 0.
09:02:50.050 SOCKS5 connection from 127.0.0.1:1454 failed: Client connection closed before completion of protocol.
09:03:04.004 Closing SOCKS5 connection from 127.0.0.1:1456, sent: 0, received: 0.
09:03:04.004 SOCKS5 connection from 127.0.0.1:1456 failed: Client connection closed before completion of protocol.
09:03:07.007 Closing SOCKS5 connection from 127.0.0.1:1458, sent: 0, received: 0.
09:03:07.007 SOCKS5 connection from 127.0.0.1:1458 failed: Client connection closed before completion of protocol.
09:03:09.009 Closing SOCKS5 connection from 127.0.0.1:1460, sent: 0, received: 0.
09:03:09.009 SOCKS5 connection from 127.0.0.1:1460 failed: Client connection closed before completion of protocol.
09:03:11.011 Closing SOCKS5 connection from 127.0.0.1:1462, sent: 0, received: 0.
09:03:11.011 SOCKS5 connection from 127.0.0.1:1462 failed: Client connection closed before completion of protocol.
09:03:12.012 Closing SOCKS5 connection from 127.0.0.1:1464, sent: 0, received: 0.
09:03:13.013 SOCKS5 connection from 127.0.0.1:1464 failed: Client connection closed before completion of protocol.
09:03:14.014 Closing SOCKS5 connection from 127.0.0.1:1466, sent: 0, received: 0.
09:03:14.014 SOCKS5 connection from 127.0.0.1:1466 failed: Client connection closed before completion of protocol.
09:03:26.026 Closing SOCKS5 connection from 127.0.0.1:1468, sent: 0, received: 0.
09:03:26.026 SOCKS5 connection from 127.0.0.1:1468 failed: Client connection closed before completion of protocol.

Edited February 7, 2012 by SirXulescu

[dansud2007]

Foarte folositor!

[pyth0n3]

Multi m-au intrebat daca se poate face un server SSH (nologin) sau HTTPS pe Windows

In primul rad faptul ca ai creat un tutorial e de apreciat OK

Server ssh emulat pentru windows e OK

SSL/HTTPS pentru Windows e OK

Nologin WTF?

Eu iti mai pun o intrebare:

Cu care directiva ai alocat un shell nologin userilor in windows ?

Eu nu am vazut nici un shell cu restrictii pentru user , nici macar acel shell care e emulat nu are restrictii nologin.

Cum poti sa creezi ceva care nu a existat vreodata nici macar emulat.

Inghititi cuvantul nologin si nu mai deschideti gura, nu il mai puneti aiurea in context

P.S Daca nu as avea alternativa , in loc sa platesc licenta pentru vizual WRAPPING as folosi Cygwin care are deja un server sshd .

(openSSH) ESTE ---> open source

cygrunsrv --start sshd

Edited February 8, 2012 by pyth0n3

[wildgenin]

Multumesc.

Foarte util.