search for: fuckup

...fail. Ok, <paranoia> It's better to refuse starting then *maybe* in an insecure configuration mode </paranoia> .. and yes <pedantic> test your stuff before restarting </pedantic> .. but hey, sometimes you are in a hurry .. :-} Or imagine a nulled configuration file (FS fuckup, whatever) sshd will start also.. w/ possible insecure configuration .... <rant> openssh tends to develop major paranoia .. security is also about realiablity. sshd is usually a *remote* tool, and way-to-easy-self-shoot-feet is not fun (yeah, tell me something about terminalservers) same fo...

...users actually do that). Naturally, this does not work for publicly available services, where there is currently no alternative to using well-known CAs. Of course their certs are not technically better than my own CA's or than self- signed certs, and their processes are sometimes garbage, the fuckups of Symantec being case in point. Symantec even just sold off their whole CA business to DigiCert; it seems they never really recovered from generating fake google.com certificates two years ago: https://security.googleblog.com/2015/09/improved-digital-certificate-security.html To get back on top...

On 23 May 2019, at 01:44, Marc Roos via dovecot <dovecot at dovecot.org> wrote: > I would like to redirect sometimes a user to a 5GB garbage messages mailbox. So you want to setup a service where random spammer/hacker can trivially DDOS your system? How many simultaneous 5GB streams can you handle? How much will your bandwidth bill be if you send 5GB a million times in a month? --

...IP, DNS>. The <username, cookie> portion would be a "hard key", where both would need to match in the database. The <IP, DNS> portion should be configurable, in our case we would want at least one to match, and upon a mismatch in either the DNS or IP (DHCP client, or DNS fuckup), to add that entry into the database as well. Each entry in the database would have a lifetime, and this lifetime would be updated each time you hit the entry in the database. If your tuple does not exist in the database, I could see sshd spitting back "Sorry, you're coming from a host/...

I need to change the host name on a test server, and in the past when I used hostname to change the hostname, it did not seem to change it everywhere. I really don't want to do a rebuild just yet, but I have to feel confident that hostname is really changed (reboot is not too much of an issue). What is the recommened practice? Other than get it right the first time.

...CNAME, objectGUID records are done. > SRV records like LDAP etc. are not. > > On 11.09.20 11:29, L.P.H. van Belle via samba wrote: > >> I think all is clean fine. > > You "think"..?? .. You must verify this ! > > > > Asumption is the mother of all fuckups an old boss of me > always said.. > > And he is right. > > > > Run : samba-tool fsmo show > > > > And verify both servers. > > > https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_D > NS_Record#The_objectGUID_CNAME_Record > > &...

On Wed, 9 Aug 2017 08:39:30 -0700 Gregory Sloop <gregs at sloop.net> wrote: > AV> So i?m using dovecot, and i created a self signed certificate > AV> with mkcert.sh based on dovecot-openssl.cnf. The name in there matches > AV> my mail server. > > AV> The first time it connects in mac mail however, it says the > AV> certificate is invalid and another

mdew:~# tc qdisc add dev imq0 handle 1: root htb default 12 r2q 1 Cannot find device "imq0" mdew:~# lsmod Module Size Used by Not tainted ipt_REDIRECT 728 0 (autoclean) ipt_MARK 728 2 (autoclean) iptable_mangle 2100 1 (autoclean) ipt_REJECT 2712 4 (autoclean) iptable_filter 1672 1 (autoclean)

> I think all is clean fine. You "think"..?? .. You must verify this ! Asumption is the mother of all fuckups an old boss of me always said.. And he is right. Run : samba-tool fsmo show And verify both servers. https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record#The_objectGUID_CNAME_Record And go through : https://wiki.samba.org/index.php/Active_Directory_Sites#Setting_up_a_n...

Hello, after demote and rejoun my dc2 i have problems with replication. First of all some srv records on dc1 are missing, on dc2 they are exist. root at dc2:~# dig srv _ldap._tcp.ForestDnsZones.samdom.example.com @dc2.samdom.example.com. ; <<>> DiG 9.11.5-P4-5.1+deb10u1-Debian <<>> srv _ldap._tcp.ForestDnsZones.samdom.example.com @dc2.samdom.example.com. ;; global