Debian Codegraph @

FAQ

raw ◀ ▶
Source reconstructed at patch state 0 of 2 — not the installed (fully patched) source.
2 Debian patches touch this file
1 Q: I'm not real sure what httptunnel can be used for exactly?
2
3 A: It's a generic tool for sending data in and out through an HTTP proxy.
4 This is not very useful in itself, so you must run another program
5 which uses this data "tunnel". For example, you could use telnet
6 to log in on a computer ouside the proxy.
7
8 Q: httptunnel craches my SuSE 5.3 box, why?
9
10 A: I don't know, but upgrading to 6.0 seems to help.
11
12 Q: I'm responsible for network security in our company. My question
13 is: are there any characteristics of the communication that may be
14 detected at the proxy?
15
16 A: Maybe. I make no guarantees. Use the source.
17
18 Q: I wrote 'hts -d /dev/ptyq1' but 'cat </dev/ptyq1' returns an error.
19
20 A: Use 'cat </dev/ttyq1' instead.
21
22 Q: My friend runs hts at port 8888, but when I try to connect to it,
23 there is no response.
24
25 A: As for now, hts can't handle multiple tunnels. You must run your
26 own instance of hts listening to another port.
27
28 Q: Is there a Windows/95/98/NT version?
29
30 A: It's possible to build and run httptunnel in the Cygwin environment.
31 See http://sourceware.cygnus.com/cygwin/.
32
33 Q: Are there binaries of httptunnel for win32(Windows/95/98/NT) anywhere?
34
35 A: On the homepage, there is a link to someone maintaining
36 win32 binaries.
37
38 Q: Is there a Macintoch version?
39
40 A: Not that I know of.
41
42 Q: My firewall requires HTTP user authentication (which is currently
43 not supported by httptunnel). Do you plan to add something like
44 that?
45
46 A: Yes.
47
48 Q: How hard would it be to implement "hts" as a cgi running on a
49 normal web server?
50
51 A: hts can't be called directly from the HTTP server, because hts will
52 service many connections during the lifetime of the tunnel. If the
53 HTTP server executed a new instance of hts every time a new request
54 was made, each new hts wouldn't have access to the prior state of
55 the tunnel.
56
57 However, a CGI proxy which forwards the requests to a normal hts
58 listening to a port != 80 whould most probably be quite trivial to
59 implement.
60
61 Q: Have you thought of using HTTPS?
62
63 A: It has been suggested, but I'd rather avoid all the nasty export
64 restrictions. You can use external software to get an encrypted
65 tunnel.
66
67 Q: On REMOTE (brugd.ctrl-c.liu.se) I do the following:
68 hts -F localhost:23 8888
69
70 This worked the first time, but never since... now I only get:
71 hts: couldn't create tunnel
72
73 A: The first hts is still running in the background.
74
75 Q: On LOCAL (dhcp-XXX.enea.se) I do:
76 htc -F 2323 -P http://internwebb/proxy2.pac:8000 brugd.ctrl-c.liu.se:8888
77
78 Now, I try:
79 [root@localhost httptunnel-1.101]# telnet localhost 2323
80 Trying 127.0.0.1...
81 telnet: Unable to connect to remote host: Connection refused
82
83 A: [Christian Brideau] http://internwebb/proxy2.pac:8000 is not
84 exactly the proxy's adress. This is the location of the
85 Proxy-Auto-Configure (PAC) file. This file contains the adress of
86 the proxy server. To discover the real adress, just go to an
87 external web page using a browser and then use netstat to figure
88 out what adress your browser is using.
89
90 Q: Why does 'configure' fail on HP-UX?
91
92 A: Because you haven't installed gcc. If
93 CFLAGS=-O ./configure
94 doesn't work, you must get gcc, or at least an ANSI C compiler.