I am newer to Linux/Unix/RedHat etc... I run a Linux root server with some 55 domain names, about 3 months ago the server was exploited. I need some good advice as far as Firewell's go and getting everything up and running. It was a pain in my *** and cost a lot of time and money.. Thanks!
Hey Folks,
What are the ways we can provide security to kernels.
How can I make my Kernel Unique and not allow anyone to replace my Unique kernel with a standard one.
How can i implement measures to avoid any user to replace or modify GRUB and Kernel...?
Need help on this
Thank you (8 Replies)
Hello everyone ,
I want to implement a new firewall, detection system on my network composed of some 200 computers as follows: The fire wall would be a linux box with router, L7 iptable and also snort as IDPS system. These are my questions:
1. Is there any security consideration regarding... (0 Replies)
Hi, I have the following situation and proposed solution:
SITUATION
I have a notebook computer. The manufacturer ships the hardware with a Windows OS (either XP Pro, Vista or Windows 7). They provide support only for a Windows OS.
Also, I am not sure how fuss-free it is to use any Linux... (0 Replies)
Hi all, :)
I'm quite new with installation of security patches in Linux Redhat Enterprise, here's my question.
I have 2 machine of this RHEL(never patch before) since it never connects directly to the internet(block by firewall) and I want to update the patches now because my boss asked me to... (1 Reply)
Hi all. I'm so new to Linux I don't even know where to start. I'm running sles 9 and I've had it up for 2 days now. I'd like to start with information on how to secure my server. I want to use it for hosting my personal web site and email eventually.
Does anyone know of a good site that will... (2 Replies)
CURLOPT_UNIX_SOCKET_PATH(3) curl_easy_setopt options CURLOPT_UNIX_SOCKET_PATH(3)NAME
CURLOPT_UNIX_SOCKET_PATH - set Unix domain socket
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_UNIX_SOCKET_PATH, char *path);
DESCRIPTION
Enables the use of Unix domain sockets as connection endpoint and sets the path to path. If path is NULL, then Unix domain sockets are dis-
abled. An empty string will result in an error at some point, it will not disable use of Unix domain sockets.
When enabled, curl will connect to the Unix domain socket instead of establishing a TCP connection to a host. Since no TCP connection is
created, curl does not need to resolve the DNS hostname in the URL.
The maximum path length on Cygwin, Linux and Solaris is 107. On other platforms it might be even less.
Proxy and TCP options such as CURLOPT_TCP_NODELAY(3) are not supported. Proxy options such as CURLOPT_PROXY(3) have no effect either as
these are TCP-oriented, and asking a proxy server to connect to a certain Unix domain socket is not possible.
The application does not have to keep the string around after setting this option.
DEFAULT
Default is NULL, meaning that no Unix domain sockets are used.
PROTOCOLS
All protocols except for file:// and FTP are supported in theory. HTTP, IMAP, POP3 and SMTP should in particular work (including their
SSL/TLS variants).
EXAMPLE
Given that you have an nginx server running, listening on /tmp/nginx.sock, you can request a HTTP resource with:
curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, "/tmp/nginx.sock");
curl_easy_setopt(curl_handle, CURLOPT_URL, "http://localhost/");
If you are on Linux and somehow have a need for paths larger than 107 bytes, you could use the proc filesystem to bypass the limitation:
int dirfd = open(long_directory_path_to_socket, O_DIRECTORY | O_RDONLY);
char path[108];
snprintf(path, sizeof(path), "/proc/self/fd/%d/nginx.sock", dirfd);
curl_easy_setopt(curl_handle, CURLOPT_UNIX_SOCKET_PATH, path);
/* Be sure to keep dirfd valid until you discard the handle */
AVAILABILITY
Since 7.40.0.
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO CURLOPT_OPENSOCKETFUNCTION(3), unix(7),
libcurl 7.54.0 December 21, 2016 CURLOPT_UNIX_SOCKET_PATH(3)