When I set the MaxRequestWorkers to 20, all the Apache Child processes cannot be more then 20. But, that means if one users used all of the 20, the rest of the users are also not allowed to make more apache child process.
I want to set this up on a per user basis. If user John created 20 processes, and user jane only 5, she can still create up to 20.
How can I achieve this?
So, this is a fun story regarding HTTP Public Key Pinning (HPKP) and HTTP Strict Transport Security (HSTS).
I was playing with the HTST Always and HPKP preload options, not being fully aware of the consequences.
About the same time, I discovered that my "test" account that I used to 'test' on how I can fully secure users, was not secure. I was deleting it, remaking it, and one time I forgot to secure it.
It was a normal user, with little to no rights, I deleted the user, by killing the the processes owned by the user "test". Then I rm -rfv /home/test/.
However, I still did not feel save, thus I reinstalled my server, thinking that I could renew cert with Let's Encrypt, add them again, and we're done.
Alas, that was not meant to be. When I browse my website(*.eurobytes.nl), with chrome, I get the following message:
ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN
When browsing one of my subdomains, Mozilla Firefox, wont even display the website, it just doesn't go there.
I'm assuming all this can be fixed by delisting myself from the Mozilla Firefox/Google Chrome HTST and HPKP list.
How can I delist myself from HTST and HPKP?
I edited the PowerDNS conf file, and added another IP address in the allow-axfr-ips= section, but that IP address is still not allowed to do anything. I checked the firewall, that is also not interfering.
So, my question is do I need to reload, and or restart the pdns_server binary?
Recently I have been trying to secure mail ports 993/995/465 with a certificate. It works when specifying the server hostname, But that's not an option on a shared server with numerous users.
The 'working' setup is:
Protocol domain/hostname Port SSL
Incoming IMAP shared.server.tld 993 SSL
Outgoing SMTP shared.server.tld 465 SSL
I need it to work for mail.domainname. So that the only thing the customers have to do is to turn on SSL in Apple Mail/OUTLOOK/Thunderbird, and or specify the 993/465 ports.
Right now when I specify the mail.domainname I get a certificate mismatch, because the cert is for shared.server.tld and not mail.domainname
How do I secure the mail.domainname ports with a certificate specified for shared.server.tld?
We have tried with a srv DNS record, and are looking to get this working with a autodiscover.
I am currently migrating a website, and my usual method is working with mail clients, and copy the old mailbox to the new server mailbox.
But, if you have a website, with multiple mailboxes, and those mailboxes have numerous folders, the work usually takes all day.
I have searched the Internet for a far more easy and faster way, preferably open-source, but most tools are ancient, and the Q/A here are years old.
Wat is the faster and easier way of migrating mailboxes?
Paid tool:
Free Tool
Note:
I have root access on the destination server, and not on the source.
I downloaded the e-mails with the following settings
mail.DONAINNAME.com: IMAP (for receiving) smtp.DOMAINNAME.com: SMTP (for sending)