このページは大阪弁化フィルタによって翻訳生成されたんですわ。

翻訳前ページへ


Linux-Howto.com

  TUCOWS NETWORK

   LINUXBERG | TUCOWS | FREETHEMES | GAMINGPLACE | eBarn | PDA Central | HOME

HOW TO - Home

Click here!

What's new About Us Contact Us Advertise



Welcome to HowTo! The premier Linux information resource center.
____________________________________

H HOWTO 's 

html'd
(HOWTOs in html)
plain text
(HOWTOs in plain text for printing)
html'd
(Mini-HOWTOs)
plain text
(Mini-HOWTOs)


LDP Additions
(Latest from LDP)
Other Formats
(LDP Other Formats)
Translations
(LDP Other Languages)
Unmaintained
(LDP Unmaintained)


Contrib
(Submitted Documentation)
FAQ
(Frequently Asked Questions)
Links
(Links page)
IRC Information
(IRC Page)
ISPs
(Linux Friendly ISPs)
Book Store
(Books through Amazon.com)
RFC Index
(Request For Comments)
Man Pages
(Linux Manual Pages)
LUGs
(Linux User Group Listing)

 


Firewall Piercing mini-HOWTO: Reverse piercing Next Previous Contents

5. Reverse piercing

5.1 Rationale

Sometimes, only one side of the firewall can launch telnet sessions into the other side; however, some means of communication is possible (typically, through e-mail). Piercing the firewall is still possible, by triggering with whatever messaging capability is available a telnet connection from the ``right'' side of the firewall to the other.

fwprc includes code to trigger such connections from a PGP-authentified e-mail message; all you need is add fwprc as a procmail(1) filter to messages using the protocol, (instructions included in fwprc itself). Note however, that if you are to launch pppd with appropriate priviledges, you might need create your own suid wrapper to become root. Instructions enclosed in fwprc.

Also, authentified trigger does not remotely mean secure connection. You should really use ssh (perhaps over telnet) for secure connections. And then, beware of what happens between the triggering of a telnet connection, and ssh taking over that connection. Contribution in that direction welcome.

5.2 Getting the triggering mail

If you are firewalled, your mail may as well be in a central server that doesn't do procmail filtering or allow telnet sessions. No problem! You can use fetchmail(1) to run in daemon mode to poll and get mail to your client linux system, and/or add a cron-job to automatically poll for mail every 1-5 minutes. fetchmail will forward mail to a local address through sendmail(8), which itself will have been configured to use procmail(1) for delivery. Note that if you run fetchmail(1) as a background daemon, it will lock away any other fetchmail that you'd like to run only at other times, like when you open a fwprc; of course, if you can also run a fetchmail daemon as a fake user. Too frequent a poll won't be nice to either the server or your host. Too unfrequent a poll means you'll have to wait before the message gets read and the reverse connection gets established. I use two-minute poll frequency.


Next Previous Contents

TUCOWS NETWORK
_________________________________
Last Edited: Thursday, January 21, 1999 03:11 PM
Maintainer:
Rob Kennedy (rob@linuxberg.com)
Site Design - Graphicjam Digital Arts Inc. 1999.

ョ 1999 TUCOWS Interactive Ltd. All rights reserved