07-28-2001
Sockets donot send any thing to client
I have written a socket program in C under RedHat Linux 6.2. This program is using SOCK_STREAM (TCP) to connect to any ip address at port # 23. The program is hosted on the linux machine and works well with Cisco routers. But when I am trying to connect to the same linux machine, it does not return any thing. I have checked my hosts.allow and hosts.deny files. They don't have any restrictions. I am able to use telnet client to login to my linux server.
Can any one help me sort this out ?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi,
i am trying to send mail with attachment to web-based email client like gmail.com using mailx. the problem is it is displayed in content rather than as attachment.
the code i am using is as follows,
uuencode test1.txt test1.txt | mailx -s "test only" aaaa@gmail.com
does anyone... (1 Reply)
Discussion started by: randomcz1
1 Replies
2. UNIX for Dummies Questions & Answers
i want to send email from server to the client's email-id. server is solaris. please help me out.i want to send mail to the email-id not to the var/spool/mail. (8 Replies)
Discussion started by: parmeet
8 Replies
3. Programming
Hi,
Am very new to socket programming.
When we use UDP sockets to communicate between two processess,
will both the client/server socket be able to send/recv ?
meaning can sendto()/ recvfrom() be used on both server and client?
It could be useful even if anybody provide some link on socket... (1 Reply)
Discussion started by: rvan
1 Replies
4. Programming
Hi all,
i am having a doubt regarding how to get the acknowledgement(reply) from client to server & how to recieve at the server....imagine there r 8 frames...we have to send first 4frames at a time and after tat we have to receive and ack and only after receiving an ack we have to send... (1 Reply)
Discussion started by: Rohil
1 Replies
5. UNIX for Advanced & Expert Users
Hi folks
OS- Debian Etch
Xen
postfix
courier
perdition
perdition-mysql
MySQL
Single public IP
Dom0 - Debian Etch workstation
Server-1, domU1 for routing with perdition and perdition-mysql
installed
Server-2, domU2, mail server for domain-A
Server-3, domU3, mail server for... (2 Replies)
Discussion started by: satimis
2 Replies
6. Homework & Coursework Questions
Hello everyone!I would appreciate any help you could give me,I have to make a program of an atm machine using client server sockets and semaphores.I know how to construct an ATM in c++ but don't know anything about unix c.The problem is that Don't know what to do and how to link the two programs... (0 Replies)
Discussion started by: tamanas
0 Replies
7. Solaris
Dear all,
We have SMTP server in our organization & i want to send e-mails from solaris machine using sendmail ... in which file i need to put the smtp server ip, username & passwd..
kindly help ....... (4 Replies)
Discussion started by: vishwanathhcl
4 Replies
8. Programming
Hey guys,
Is it possible to have a worker thread send data out a TCP connection while another thread is waiting using using select() on that same connection?
If not, then what is the correct way to maintain a connection, react to incoming data, and send data over a TCP connection?
Thanks... (16 Replies)
Discussion started by: scubanarc
16 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I want to send an email from server to my gmail account for all critical messages reported in the server. Kindly help me in configuring the same.
Regards
Rochit (1 Reply)
Discussion started by: rochitsharma
1 Replies
10. IP Networking
Hello All,
I am very new to socket programming and client server architecture. I have to write a client which will send some data to server and server will display it on its console. I am ready with both client and server but my problem is with packetizing of data --
I have... (1 Reply)
Discussion started by: anand.shah
1 Replies
LEARN ABOUT NETBSD
rhosts
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, ``+@netgroup'' (from
which only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, ``+@netgroup'' (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD