| |
| |
| |
|
Page: 1 2
Comments:
<0> this does mean that if it's still going in 30 minutes, I'll be wishing I wore a coat today.
<1> Sounds like yesterday for me.
<2> when portforwarding via ssh, is the source ip 127.0.0.1 of the incoming connection?
<2> for example, I have a box with httpd and sshd, another box with windows and putty, where putty portforwards local port 1234 onto port 80 on the other box
<2> if I filter out everything but localhost on the webserver, will the winbox still be able to access the webserver?
<2> *on port 80
<2> to make it clearer, the rule is, filter out every source ip on port 80 *except* 127.0.0.1
<0> *checks*
<0> yup.
<0> if you tell ssh to do that.
<0> -L 127.0.0.1:8080:127.0.0.1:80
<2> phyber: ah thanks
<0> I used that.
<0> so, connecting to 8080 on localhost forwarded it to 80 on the machien I'd sshed to.
<0> machine.
<2> great, so I'm going with the tcp/ip connection between my server/client
<2> + forced ssh tunneling
<2> that takes care of auth too
<0> what are you writing?
<2> db server + client api
<2> most of the communication is going to be binary
<2> underlying db backend is irrelevant really, probably enough to use sqlite for our purposes
<2> oh, that does raise a question... how would the server know which user is connecting?
<2> maybe I can read owner,user field like MATCH_OWNER in netfilter
<3> good evening to everyone (except me)
Return to
#slackware
or
Go to some related
logs:
Pete Rickets
#ubuntu
#stocks
#goal
#nhl
athonfx cost
vamecum
#beginner
#linux-noob
#nhl
|
|