Remove wsssh and wsscp from the project

- Remove wsssh.c and wsscp.c source files
- Remove wsssh.1 and wsscp.1 man pages
- Remove wsssh.conf.example and wsscp.conf.example config files
- Update configure.sh to exclude wsssh and wsscp from build
- Update debian/control to reflect remaining tools (wssshc + wsssht)
- Verified build works with only wssshc and wsssht binaries
- Project now focuses on wssshc (client) and wsssht (tunnel tool with pipe mode)
parent 76ac4c24
...@@ -58,12 +58,12 @@ LDFLAGS = $(shell pkg-config --libs openssl) ...@@ -58,12 +58,12 @@ LDFLAGS = $(shell pkg-config --libs openssl)
# Source files # Source files
LIB_SRCS = libwsssht/wssshlib.c libwsssht/websocket.c libwsssht/wssh_ssl.c libwsssht/tunnel.c libwsssht/utils.c libwsssht/modes.c libwsssht/threads.c LIB_SRCS = libwsssht/wssshlib.c libwsssht/websocket.c libwsssht/wssh_ssl.c libwsssht/tunnel.c libwsssht/utils.c libwsssht/modes.c libwsssht/threads.c
LIB_OBJS = $(LIB_SRCS:.c=.o) LIB_OBJS = $(LIB_SRCS:.c=.o)
SRCS = wssshc.c wsssh.c wsscp.c wsssht.c SRCS = wssshc.c wsssht.c
OBJS = $(SRCS:.c=.o) OBJS = $(SRCS:.c=.o)
TARGETS = wssshc wsssh wsscp wsssht TARGETS = wssshc wsssht
# Man pages # Man pages
MANPAGES = man/wssshc.1 man/wsssh.1 man/wsscp.1 man/wsssht.1 MANPAGES = man/wssshc.1 man/wsssht.1
# Default target # Default target
all: $(TARGETS) all: $(TARGETS)
...@@ -72,12 +72,6 @@ all: $(TARGETS) ...@@ -72,12 +72,6 @@ all: $(TARGETS)
wssshc: wssshc.o libwsssht/wssshlib.o libwsssht/websocket.o libwsssht/wssh_ssl.o libwsssht/tunnel.o wssshc: wssshc.o libwsssht/wssshlib.o libwsssht/websocket.o libwsssht/wssh_ssl.o libwsssht/tunnel.o
$(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS) $(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS)
wsssh: wsssh.o libwsssht/wssshlib.o libwsssht/websocket.o libwsssht/wssh_ssl.o libwsssht/tunnel.o
$(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS)
wsscp: wsscp.o libwsssht/wssshlib.o libwsssht/websocket.o libwsssht/wssh_ssl.o libwsssht/tunnel.o
$(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS)
wsssht: wsssht.o $(LIB_OBJS) wsssht: wsssht.o $(LIB_OBJS)
$(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS) $(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS)
...@@ -108,20 +102,12 @@ install: all ...@@ -108,20 +102,12 @@ install: all
uninstall: uninstall:
# Remove from both possible locations # Remove from both possible locations
rm -f $(DESTDIR)/usr/local/bin/wssshc rm -f $(DESTDIR)/usr/local/bin/wssshc
rm -f $(DESTDIR)/usr/local/bin/wsssh
rm -f $(DESTDIR)/usr/local/bin/wsscp
rm -f $(DESTDIR)/usr/local/bin/wsssht rm -f $(DESTDIR)/usr/local/bin/wsssht
rm -f $(DESTDIR)/usr/local/share/man/man1/wssshc.1 rm -f $(DESTDIR)/usr/local/share/man/man1/wssshc.1
rm -f $(DESTDIR)/usr/local/share/man/man1/wsssh.1
rm -f $(DESTDIR)/usr/local/share/man/man1/wsscp.1
rm -f $(DESTDIR)/usr/local/share/man/man1/wsssht.1 rm -f $(DESTDIR)/usr/local/share/man/man1/wsssht.1
rm -f $(DESTDIR)/usr/bin/wssshc rm -f $(DESTDIR)/usr/bin/wssshc
rm -f $(DESTDIR)/usr/bin/wsssh
rm -f $(DESTDIR)/usr/bin/wsscp
rm -f $(DESTDIR)/usr/bin/wsssht rm -f $(DESTDIR)/usr/bin/wsssht
rm -f $(DESTDIR)/usr/share/man/man1/wssshc.1 rm -f $(DESTDIR)/usr/share/man/man1/wssshc.1
rm -f $(DESTDIR)/usr/share/man/man1/wsssh.1
rm -f $(DESTDIR)/usr/share/man/man1/wsscp.1
rm -f $(DESTDIR)/usr/share/man/man1/wsssht.1 rm -f $(DESTDIR)/usr/share/man/man1/wsssht.1
.PHONY: all clean install uninstall .PHONY: all clean install uninstall
......
...@@ -16,5 +16,4 @@ Description: WebSocket SSH Tools - C implementation ...@@ -16,5 +16,4 @@ Description: WebSocket SSH Tools - C implementation
route SSH/SCP traffic through registered client machines. route SSH/SCP traffic through registered client machines.
. .
This package contains the C implementation of the WebSocket SSH tools: This package contains the C implementation of the WebSocket SSH tools:
wssshc (client registration), wsssh (SSH wrapper), wsscp (SCP wrapper), wssshc (client registration) and wsssht (tunnel setup tool with pipe mode).
and wsssht (tunnel setup tool). \ No newline at end of file
\ No newline at end of file
.TH WSSCP 1 "September 2025" "wsssh-tools 1.4.0" "WebSocket SSH Tools"
.SH NAME
wsscp \- WebSocket SCP wrapper for secure file transfer
.SH SYNOPSIS
.B wsscp
[\fB\-\-local\-port\fR \fIPORT\fR]
[\fB\-\-tunnel\fR \fITYPES\fR]
[\fB\-\-tunnel\-control\fR \fITYPES\fR]
[\fB\-\-service\fR \fISERVICE\fR]
[\fB\-\-debug\fR]
[\fB\-\-dev\-tunnel\fR]
[\fB\-\-help\fR]
[\fISCP_OPTIONS\fR...]
\fISOURCE\fR...
\fIDESTINATION\fR
.SH DESCRIPTION
.B wsscp
is a wrapper around the standard SCP client that enables secure file transfer through WebSocket connections. It automatically establishes tunnels to registered clients and handles file transfers transparently.
.SH OPTIONS
.TP
.BR \-\-local\-port " \fIPORT\fR"
Local port for tunnel establishment (default: auto-assign)
.TP
.BR \-\-tunnel " \fITYPES\fR"
Transport types for data channel (comma-separated or 'any', default: any)
.TP
.BR \-\-tunnel\-control " \fITYPES\fR"
Transport types for control channel (comma-separated or 'any', default: any)
.TP
.BR \-\-service " \fISERVICE\fR"
Service type (default: scp)
.TP
.B \-\-debug
Enable debug output for troubleshooting
.TP
.B \-\-dev\-tunnel
Development mode: setup tunnel but don't launch SCP
.TP
.B \-\-help
Display help message and exit
.SH HOSTNAME FORMAT
Hostnames in source/destination paths follow the format: [\fIuser\fR@]\fIclient_id\fR.\fIwssshd_host\fR[:\fIport\fR]
.TP
Examples:
- \fBuser@remote.example.com:/path/file\fR → client: \fBremote\fR, server: \fBexample.com:9898\fR
- \fBserver.datacenter.com:2222/file\fR → client: \fBserver\fR, server: \fBdatacenter.com:2222\fR
.SH EXAMPLES
.TP
Copy file to remote:
.B wsscp -P 9898 localfile user@myclient.example.com:/remote/path/
.TP
Copy file from remote:
.B wsscp -P 9898 user@myclient.example.com:/remote/file ./localfile
.TP
Copy directory recursively:
.B wsscp -P 9898 -r localdir user@myclient.example.com:/remote/
.TP
Copy with debug output:
.B wsscp --debug -P 2222 file.txt user@remote.example.com:~/downloads/
.SH SCP OPTIONS
All standard SCP options are supported. The port option (\fB-P\fR) specifies the wssshd server port, not the target SSH port.
.SH ENVIRONMENT
.TP
.B WSSCP_DEBUG
Set to 1 to enable debug output (alternative to --debug)
.SH SECURITY
File transfers are secured through SSL/TLS encrypted WebSocket tunnels. All data in transit is protected by the tunnel encryption.
.SH EXIT STATUS
.B wsscp
returns the exit status of the underlying SCP command.
.SH SEE ALSO
.BR scp (1),
.BR wssshd (1),
.BR wssshc (1),
.BR wsssh (1)
.SH AUTHOR
Written by Stefy Lanza <stefy@nexlab.net>
.SH COPYRIGHT
Copyright \(co 2024 Stefy Lanza and SexHack.me. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
.SH BUGS
Report bugs to: https://git.nexlab.net/nexlab/wsssh/issues
\ No newline at end of file
.TH WSSH 1 "September 2025" "wsssh-tools 1.4.0" "WebSocket SSH Tools"
.SH NAME
wsssh \- WebSocket SSH wrapper for secure tunneling
.SH SYNOPSIS
.B wsssh
[\fB\-\-local\-port\fR \fIPORT\fR]
[\fB\-\-tunnel\fR \fITYPES\fR]
[\fB\-\-tunnel\-control\fR \fITYPES\fR]
[\fB\-\-service\fR \fISERVICE\fR]
[\fB\-\-debug\fR]
[\fB\-\-dev\-tunnel\fR]
[\fB\-\-help\fR]
\fIuser\fR@\fIclient\fR.\fIdomain\fR
[\fISSH_OPTIONS\fR...]
.SH DESCRIPTION
.B wsssh
is a wrapper around the standard SSH client that enables secure tunneling through WebSocket connections. It automatically parses hostnames to extract client IDs and server endpoints, establishes WebSocket tunnels, and launches SSH to connect through the tunnel.
.SH OPTIONS
.TP
.BR \-\-local\-port " \fIPORT\fR"
Local port for tunnel establishment (default: auto-assign)
.TP
.BR \-\-tunnel " \fITYPES\fR"
Transport types for data channel (comma-separated or 'any', default: any)
.TP
.BR \-\-tunnel\-control " \fITYPES\fR"
Transport types for control channel (comma-separated or 'any', default: any)
.TP
.BR \-\-service " \fISERVICE\fR"
Service type (default: ssh)
.TP
.B \-\-debug
Enable debug output for troubleshooting
.TP
.B \-\-dev\-tunnel
Development mode: setup tunnel but don't launch SSH
.TP
.B \-\-help
Display help message and exit
.SH HOSTNAME FORMAT
The hostname follows the format: \fIclient_id\fR.\fIwssshd_host\fR[:\fIport\fR]
.TP
Examples:
- \fBremote.example.com\fR → client: \fBremote\fR, server: \fBexample.com:9898\fR
- \fBserver.datacenter.com:2222\fR → client: \fBserver\fR, server: \fBdatacenter.com:2222\fR
.SH EXAMPLES
.TP
Basic SSH connection:
.B wsssh user@myclient.example.com -p 9898
.TP
SSH with custom options:
.B wsssh -p 9898 -i ~/.ssh/key user@myclient.example.com ls -la
.TP
SSH with debug output:
.B wsssh --debug user@remote.example.com -p 2222
.SH ENVIRONMENT
.TP
.B WSSSH_DEBUG
Set to 1 to enable debug output (alternative to --debug)
.SH SECURITY
All tunnel communications are encrypted using SSL/TLS. The client verifies server certificates. For production deployments, use properly signed certificates.
.SH EXIT STATUS
.B wsssh
returns the exit status of the underlying SSH command.
.SH SEE ALSO
.BR ssh (1),
.BR wssshd (1),
.BR wssshc (1),
.BR wsscp (1)
.SH AUTHOR
Written by Stefy Lanza <stefy@nexlab.net>
.SH COPYRIGHT
Copyright \(co 2024 Stefy Lanza and SexHack.me. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
.SH BUGS
Report bugs to: https://git.nexlab.net/nexlab/wsssh/issues
\ No newline at end of file
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment