About mpavlas

mpavlas · ‎11-16-2022

Hi, after upgrade to Splunk 9.0.2 the UFMA started to use https://[::1]:8089/services/deployment/server/clients?count=0 for REST API call which resulted into 400 Host header contains invalid characters. I was able to 'fix' this by adding connectUsingIpVersion = 4-first to [general] section in server.conf. What would be the correct way?

mpavlas · ‎12-13-2021

Sorry, you need sudo setcap 'cap_net_bind_service=+ep' /opt/splunk/bin/splunk as well

mpavlas · ‎12-13-2021

More secure way: sudo setcap 'cap_net_bind_service=+ep' /opt/splunk/bin/splunkd echo /opt/splunk/lib | sudo tee /etc/ld.so.conf.d/splunk.conf sudo ldconfig Then you can run Splunk as non-root user on port 443.

mpavlas · ‎01-07-2016

https://answers.splunk.com/answers/222947/does-splunk-ldap-support-starttls.html

mpavlas · ‎03-17-2015

According to Tenable we will have to disable LDAPS soon. Is it possible to use STARTTLS on LDAP port in Splunk instead?

mpavlas · ‎04-09-2014

Splunk 6.0.2 is linked against OpenSSL 1.0.1e which has serious security flaw (CVE-2014-0160). When will be Splunk with fixed OpenSSL (1.0.1g) available?

mpavlas · ‎10-15-2012

I got report from Nessus saying Splunk is vulnerable to CVE-2011-1473 - renegotiation DoS over SSLv3. How can I fix this?

Posts	7
Solutions	0
Karma Given	0
Karma Received	7
Member Since	‎08-15-2011

Online Status	Offline
Date Last Visited	‎11-16-2022 07:19 AM

After upgrade we are receiving this error UFMA - [...

Does Splunk LDAP support STARTTLS?

OpenSSL security bug

Splunk SSL renegotiation

After upgrade we are receiving this error UFMA - [...

Re: Splunk instances will not connect to HTTP port

Re: Splunk instances will not connect to HTTP port

Re: LDAP Auth with TLS

Does Splunk LDAP support STARTTLS?

OpenSSL security bug

Splunk SSL renegotiation