[Someone1611]

You say skill issue, but no one can easily make a real bind shell (or reverse shell which is basically like you ssh to the machine) for windows even in python. I searched GitHub for YEARS, but there are only Linux code.

So I have to pull OpenSSH code for pty or whatever? Or use metasploit's code?

Windows sucks. Linux and other modern Unixes sucks half as much as Windows because not everything is a file. Plan 9 rocks but only support old hardware (they don't even support amd64 yet), and development have just been resumed.

Cygwin developers are the most miserable... since they have to implement tons of Linux syscall on an os which is a pain for programmers.

[sentap]

You say skill issue, but no one can easily make a real bind shell (or reverse shell which is basically like you ssh to the machine) for windows even in python. I searched GitHub for YEARS, but there are only Linux code.

So I have to pull OpenSSH code for pty or whatever? Or use metasploit's code?

Windows sucks. Linux and other modern Unixes sucks half as much as Windows because not everything is a file. Plan 9 rocks but only support old hardware (they don't even support amd64 yet), and development have just been resumed.

Cygwin developers are the most miserable... since they have to implement tons of Linux syscall on an os which is a pain for programmers.

Creating a bind shell or reverse shell in Python on Windows indeed poses unique challenges compared to Unix-like systems. The fundamental differences between the operating systems, particularly in how they handle processes and system calls, contribute to this complexity.


Windows API vs. POSIX Compliance: Unlike Linux, which adheres to POSIX standards, Windows utilizes a distinct API. This discrepancy necessitates a different approach to handle networking and process control, which can be cumbersome for developers accustomed to the Unix environment.

Socket Programming: In Python, implementing a bind shell typically involves socket programming. While the

socket
module in Python provides a straightforward interface, the lack of seamless integration with terminal interfaces on Windows complicates the establishment of interactive shells. The Windows console does not behave like a typical Unix terminal, which makes it difficult to implement features like pseudo-terminal (pty) functionality without additional libraries or tools.

Using External Libraries: As you mentioned, utilizing OpenSSH or Metasploit's code could be a viable solution. OpenSSH has robust support for remote command execution and can serve as a foundation for building more complex shell interactions. Libraries such as

pywin32
may also provide some utility for interacting with Windows-specific features, though they can introduce additional complexity. 


Cygwin and Compatibility Layers: Cygwin indeed strives to create a Unix-like environment on Windows, but this often results in significant overhead. The developers face the daunting task of translating Linux system calls to their Windows equivalents, which can lead to performance bottlenecks and compatibility issues. While Cygwin provides some functionality, it might not offer the performance or reliability needed for robust shell implementations. 

Alternative Solutions: You might consider exploring alternative frameworks such as

pyinstaller
or
pyarmor
, which can package Python scripts in a way that makes them more portable across platforms. Moreover, tools like
Win32-OpenSSH
allow for SSH functionalities directly on Windows, which can simplify the process of establishing secure shell connections. 

In conclusion, while the landscape for creating shells on Windows can be daunting, leveraging existing libraries, APIs, and tools designed specifically for the Windows environment can significantly streamline development. The intricacies of system calls and terminal handling should not be underestimated, and understanding these aspects is crucial for successful implementation.

[re4p3r]

Why would you want to do it in python instead of something like C/C++ to begin with? All you need is winsock2.h

[Someone1611]

Why would you want to do it in python instead of something like C/C++  to begin with? All you need is winsock2.h

Skill issue. But how is pty handling possible?