An off-by-one error in the inet_network() function in libbind could lead to memory corruption with certain inputs. The risk is MEDIUM. Applications linked against libbind which call inet_network() with untrusted inputs could lead to a denial-of-service or potentially code execution.
Hi All
I need to do bind of exiting filesystem to new storage allocated
mount --bind /prod/OpenCSS /var/lib/test
echo "/prod/OpenCSS /var/lib/pgsql bind bind 0 0" >> /etc/fstab
will this command just work ? (2 Replies)
When you get the message can't bind to ip already in use.
is there a command to search to see everything that is using that IP?
I've already check the host and hostname files (2 Replies)
int bind(int socket, const struct sockaddr *address,
socklen_t address_len);
Man page says it specifies the length of the sockaddr structure pointed to by the address argument.
But why bind() can't figure out the length itself, since the first member (eg:AF_INET or... (4 Replies)
Hi all,
I am a newbie of setting up DNS server. Everything went fine except one thing.
When I do "nslookup", my server name apears as "my_server.1.131.10.in-addr.arpa" rather than "my_server.my_domian.com" on my clients. Do you know how to fix it? Thanks. (2 Replies)
INET(3N)INET(3N)NAME
inet_addr, inet_network, inet_ntoa, inet_makeaddr, inet_lnaof, inet_netof - Internet address manipulation routines
SYNOPSIS
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
unsigned long inet_addr(cp)
char *cp;
unsigned long inet_network(cp)
char *cp;
char *inet_ntoa(in)
struct in_addr in;
struct in_addr inet_makeaddr(net, lna)
long net, lna;
long inet_lnaof(in)
struct in_addr in;
long inet_netof(in)
struct in_addr in;
DESCRIPTION
The routines inet_addr and inet_network each interpret character strings representing numbers expressed in the Internet standard "." nota-
tion, returning numbers suitable for use as Internet addresses and Internet network numbers, respectively. The routine inet_ntoa takes an
Internet address and returns an ASCII string representing the address in "." notation. The routine inet_makeaddr takes an Internet net-
work number and a local network address and constructs an Internet address from it. The routines inet_netof and inet_lnaof break apart
Internet host addresses, returning the network number and local network address part, respectively.
All Internet address are returned in network order (bytes ordered from left to right). All network numbers and local address parts are
returned as machine format integer values.
INTERNET ADDRESSES
Values specified using the "." notation take one of the following forms:
a.b.c.d
a.b.c
a.b
a
When four parts are specified, each is interpreted as a byte of data and assigned, from left to right, to the four bytes of an Internet
address. Note that when an Internet address is viewed as a 32-bit integer quantity on the VAX the bytes referred to above appear as
"d.c.b.a". That is, VAX bytes are ordered from right to left.
When a three part address is specified, the last part is interpreted as a 16-bit quantity and placed in the right most two bytes of the
network address. This makes the three part address format convenient for specifying Class B network addresses as "128.net.host".
When a two part address is supplied, the last part is interpreted as a 24-bit quantity and placed in the right most three bytes of the net-
work address. This makes the two part address format convenient for specifying Class A network addresses as "net.host".
When only one part is given, the value is stored directly in the network address without any byte rearrangement.
All numbers supplied as "parts" in a "." notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x
or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal).
SEE ALSO gethostbyname(3N), getnetent(3N), hosts(5), networks(5),
DIAGNOSTICS
The value -1 is returned by inet_addr and inet_network for malformed requests.
BUGS
The problem of host byte ordering versus network byte ordering is confusing. A simple way to specify Class C network addresses in a manner
similar to that for Class B and Class A is needed. The string returned by inet_ntoa resides in a static memory area.
Inet_addr should return a struct in_addr.
4.2 Berkeley Distribution May 27, 1986 INET(3N)