Slackware: bind


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Slackware: bind
# 1  
Old 07-10-2008
Slackware: bind

LinuxSecurity.com: New bind packages are available for Slackware 8.1, 9.0, 9.1, 10.0, 10.1, 10.2, 11.0, 12.0, 12.1, and -current to address a security problem. More details may be found at the following links: http://www.isc.org/sw/bind/bind-security.php http://www.kb.cert.org/vuls/id/800113 http://cve.mitre.org/cgi-bin/cvename...=CVE-2008-1447

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Slackware

Slackware 13.

Hello everyone. I am a newbie in operating systems. so far I've been playing with Ubuntu and I like it a lot. I heard about Slackware and I wanna try it. Last night I download the iso but It didn't fit in my usb or Dvd. it is a 4.2 GB. Is there one less than 4.2GB that will fit in my usb or DVD? ... (1 Reply)
Discussion started by: openation1
1 Replies

2. Slackware

Slackware

I want to know more about the Concurrency(Process Synchronization, Deadlocks) of a slackware, i know already the Concurrency but i want to know further what else is the Concurrency(Process Synchronization, Deadlocks) of a slackware. :cool: (1 Reply)
Discussion started by: green12
1 Replies
Login or Register to Ask a Question
bind(3SOCKET)						     Sockets Library Functions						     bind(3SOCKET)

NAME
bind - bind a name to a socket SYNOPSIS
cc [ flag ... ] file ... -lsocket -lnsl [ library ... ] #include <sys/types.h> #include <sys/socket.h> int bind(int s, const struct sockaddr *name, int namelen); DESCRIPTION
The bind() function assigns a name to an unnamed socket. When a socket is created with socket(3SOCKET), it exists in a name space (address family) but has no name assigned. The bind() function requests that the name pointed to by name be assigned to the socket. RETURN VALUES
Upon successful completion 0 is returned. Otherwise, -1 is returned and errno is set to indicate the error. ERRORS
The bind() function will fail if: EACCES The requested address is protected, and {PRIV_NET_PRIVADDR} is not asserted in the effective set of the current process. EADDRINUSE The specified address is already in use. EADDRNOTAVAIL The specified address is not available on the local machine. EBADF s is not a valid descriptor. EINVAL namelen is not the size of a valid address for the specified address family. EINVAL The socket is already bound to an address. ENOSR There were insufficient STREAMS resources for the operation to complete. ENOTSOCK s is a descriptor for a file, not a socket. The following errors are specific to binding names in the UNIX domain: EACCES Search permission is denied for a component of the path prefix of the pathname in name. EIO An I/O error occurred while making the directory entry or allocating the inode. EISDIR A null pathname was specified. ELOOP Too many symbolic links were encountered in translating the pathname in name. ENOENT A component of the path prefix of the pathname in name does not exist. ENOTDIR A component of the path prefix of the pathname in name is not a directory. EROFS The inode would reside on a read-only file system. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
unlink(2), socket(3SOCKET), attributes(5), privileges(5), socket.h(3HEAD) NOTES
Binding a name in the UNIX domain creates a socket in the file system that must be deleted by the caller when it is no longer needed by using unlink(2). The rules used in name binding vary between communication domains. SunOS 5.11 20 Feb 2003 bind(3SOCKET)