Banners via TcpWrapper

Banners via TcpWrapper

Post by John C. Wingenbach (6 » Sun, 13 Nov 1994 01:58:23



I am using tcpwrappers to provide a little extra security on my systems and have
received a request to also provide a banner message prior to login.  I modified
the wrappers program to print the contents of a file to stderr and it works great
for telnet.  However, others (FTP, rlogin,...) croak.  Does anyone have any clues
how I can make this work?  Or accomplish the same via another method?

---

John C. Wingenbach                 Martin Marietta Energy Systems
                                   Data Systems Research & Development

(615) 574-8345                     1099 Commerce Park
(615) 574-0792 (FAX)               Oak Ridge, TN  37830

 
 
 

Banners via TcpWrapper

Post by Wietse Vene » Tue, 15 Nov 1994 02:59:15



Quote:>I am using tcpwrappers to provide a little extra security on my systems and have
>received a request to also provide a banner message prior to login.  I modified
>the wrappers program to print the contents of a file to stderr and it works great
>for telnet.  However, others (FTP, rlogin,...) croak.  Does anyone have any clues
>how I can make this work?  Or accomplish the same via another method?

This seems to be a popular item and I will have to do something with
the next wrapper release. Problem is that talking to the client is
service dependent. The way for ftp is begin the extra lines with 220-,
as in:

        220-some text here\r\n
        220-some more text\r\n

In case of rlogind you will have to echo a null byte to stdout before
sending any text, or the client/server handshake gets messed up.

        Wietse

 
 
 

Banners via TcpWrapper

Post by Brian Blackmo » Sat, 19 Nov 1994 04:30:29



: I am using tcpwrappers to provide a little extra security on my systems
: and have received a request to also provide a banner message prior to
: login.  I modified the wrappers program to print the contents of a file to
: stderr and it works great for telnet.  However, others (FTP, rlogin,...)
: croak.  Does anyone have any clues how I can make this work?  Or
: accomplish the same via another method?

Its best to do this sort of thing at the protocol level not at the raw socket
level otherwise you can really*the higher level protocol up. Especially
for things that might use a binary protocol (rlogin will*up since you
won't have the inital NUL).

For things that create a standard login (such as telnet and rlogin) if your
UNIX supports it try creating a /etc/issue file for login to display (this
works with the standard Linux login and the shadow login package). You should
also be able to find a way to get your ftp demon to display an intro, check
your manual pages.

--
Brian Blackmore.

 
 
 

1. Banners question for tcpwrappers

I have compiled tcpwrappers 7.6 with the language extensions in order
to make use of the banners option.  In the banners file I am trying to
make a universal file that I can copy from machine to machine without
modification.  In order to do this I need to be able to use the
`hostname` command to verify the server.

However, this does not seem to work.  The banner looks something like
the following:

         Welcome to `hostname`!

        blah blah blah
        disclaimer disclaimer
        warning warning

The `hostname` does not work.  It shows up literally in the login
banner.  I'm not a scripter so I'm sure it's something simple.

How can I make this work?

Thanks,

~JK

2. /proc/kcore

3. Probs with Setting up Banners/TCPWRAPPER

4. DIP working, apps not.

5. prototype banner for sshd via tcpd ?

6. PPP server quota setting howto?

7. identd and TCPwrappers

8. Not able to connect to Internet

9. Having (t)ftp problems with tcpwrappers

10. portmap & tcpwrappers strangeness

11. TCPWRAPPER

12. tcpwrappers are scaring me!!

13. tcpwrappers and lynx 2.2.5-release