serverfault.com

We have FreeIPA server (LDAP) for user authentication. When user authenticate all events about it should logged into /var/log/dirsrv/slapd-DOMAIN/access file. But we found that these events are randomly logged into the file. For example when some users authenticate we don't see any logs in file. This behavior is observed for different users and sometimes we can see authentication events in the logs. We disabled buffering nsslapd-accesslog-logbuffering: off increased log level nsslapd-accesslog-level: 512 and disabled nsslapd-ndn-cache-enabled: off on server but this didn't help to solve the issue. What could be the reason for this server behavior and how to fix it?

Everybody with any computer knowledge knows that having the same public IP is dangerous. Anyone who has dealt with ISPs also knows that they don't care about users, except for the money they get from users. Most ISPs are anyway just intermediary or use network infrastructure of bigger ISPs or government, so they don't really understand much about computers or networking, just like a truck driver doesn't understand about machines he is driving from China to the USA. ISPs on purpose employ people who have no clue about computers and networking and they don't even want to learn the difference between public and private IP. Whenever I call them on the phone, they keep repeating the same things over and over again about cookies, whenever anything with IP. They also often say that I have to turn off their router in my room when anything is wrong, when I haven't done anything with their router and I don't even have software access to it. Once hackers know your public IP, you cannot defend

I'm using the Azure portal. When I hover over a clickable option, these very annoying popovers appear. They're distracting, contain no information I don't already know, and obscure parts of the page I want to read. How do I disable them?

I am attempting to connect a Rundeck container (Server A) to an OpenLDAP container (Server B) via LDAPS. While standard CLI tools work perfectly (LDAPTLS_REQCERT=never ldapsearch -H ldaps://ldap-consumer:636 -x -D "cn=rundeck,cn=services,ou=accounts,dc=example,dc=local" -w "blabla" -b "ou=users,ou=accounts,dc=example,dc=local" "(uid=userid)"), Rundeck (java) instance fails during the SSL handshake. The setup : My self-signed certificates are created using ansible : --- - name: gen server.key become: yes community.crypto.openssl_privatekey: path: "{{ app.vol.cert.path.host }}/server.key" - name: gen server.csr become: yes community.crypto.openssl_csr: path: "{{ app.vol.cert.path.host }}/server.csr" privatekey_path: "{{ app.vol.cert.path.host }}/server.key" common_name: "ldap-consume

The answers to updating the email server made me think about my current DNS settings at my Domain Registrar. DNS Settings What are the correct DNS settings for an Email Server, that also hosts postfixadmin on a subdomain (postfixadmin.example.org) and uses apache webserver for Let's Encrypt (LE) certs? The Multi-Domain Email Server, sends and receives emails for multiple domains (example.net, example.com, etc. ), managed by postfixadmin using virtual mailboxes. For simplicity the DKIM and DMARC settings are not included in the Screenshot below, nor are the settings found in the screenshot concerning the domains used in this scenario. The PTR Record set at my webserver hosting provider is mx.example.org So the dig command dig -x <IP> +short has the output of

I have two systems: System A: Windows 11 System B: Windows Server 2019 My requirement is to mount the disk of System B on System A so that it appears as a locally attached disk. In simple terms, I want to enter only the IP address of System B on System A, and then be able to see the complete disk details of System B, including: Physical disk view (disk layout, partitions, sector-level information) Logical view (volumes, file systems, and files) On Windows Server, I am facing a limitation while trying to achieve this using built-in tools only. Windows does not allow exporting a physical disk directly by specifying its device path (for example \.\PhysicalDrive1). Instead, Windows requires the disk to be converted into a VHDX file before it can be shared using the built-in iSCSI Target Server role. When I attempt to map the physical disk directly using the following command: Add-IscsiServerTargetMapping -TargetName �

We'd like to limit the source IP CIDR for M2M requests obtaining tokens. In a large organization, we have multiple AWS accounts for different departments. It's common enough for Application Client's to be allocated by one team to another to allow the other team to access specific services. However when we do this we'd like to ensure that the other team requests tokens via a passthrough on our own VLAN. We've had an incident of another team requesting tokens directly from Cognito itself rather than going to our passthrough and the result was a pretty large AWS bill. Is there a way that we can set a policy on an application client or user pool such that tokens will only be given to clients originating on our own VLAN?

I’m stuck and hoping someone here can help. I forgot the password for my Gmail account and I’m unable to recover it. The main issue is with the recovery email I had set up. My email is something like: [email protected] But for the recovery email, I mistakenly added: [email protected] (without the dot) As we know, Gmail treats emails with and without dots as the same account. So effectively, my recovery email is the same Gmail account I’m locked out of. During recovery: I do receive and enter the OTP sent to my registered mobile number But after that, Google still asks for an OTP sent to the recovery email Since I can’t access that email (it’s the same account), I’m completely stuck Has anyone faced this issue before? Is there any way to bypass the recovery email step or contact Google support for this kind of situation? Any advice would really help. Thanks in advance.

I am trying to set up a Windows 11 Azure Virtual Desktop that has access to an Azure file share via a mapped drive letter. I created the File Share and can connect to it just fine from my own workstation running Windows 11, using net use S: "\\mystorageaccount.file.core.windows.net\sharename", or New-PSDrive -Name S -PSProvider FileSystem -Root "\\mystorageaccount.file.core.windows.net\sharename" or New-SMBMapping However, I get System error 67 any time I try to mount the exact same path from any Azure machine. The hostname is found by nslookup and Test-Connection -ComputerName mystorageaccount.file.core.windows.net -Port 445 I also created a Windows Server 2022 VM to try and replicate it with an older OS, and it was exactly the same. I am authenticating using the Storage Account Key. The File Share is in the same region as the VM. I don't have any Azure Firewalls

I have Nginx running in Docker on Ubuntu 22.04 To rotate logs, I use Logrotate 3.19 After the upgrade from Ubuntu 20.04 to 22.04, Nginx stoped writing to new access.log after rotation. Manually running logrotate would run without errors and Nginx starts writing to new file. I have no idea where to look for problem here. Nginx just writes 8Gb to access.log.1 until there is no space left on device. Logrotate config file is default, not altered: /var/log/nginx/*.log { daily missingok rotate 14 compress delaycompress notifempty create 0640 www-data adm sharedscripts prerotate if [ -d /etc/logrotate.d/httpd-prerotate ]; then \ run-parts /etc/logrotate.d/httpd-prerotate; \ fi \ endscript postrotate invoke-rc.d nginx rotate >/dev/null 2>&1 endscript }