search for: quick'n

..._4.8.0RC2' > > not found (required by /usr/local/samba/lib/ldb/encrypted_secrets.so) > > when you are doing your downgrade, did you clean up all the > /usr/local/samba directory or did you make && make install over the > existing installation? > > If it was a quick'n dirty make && make install over the existing 4.8 > install, could you try to do a install on a clean directory and then > copy over etc/smb.conf, private/ and var/locks/? > > Cheers, > > Denis This is exactly the issue. The install has left an ldb plugin (encry...

...ectly. Otherwise, the BIOS initializes the INT 13 vector to a place that does not give access to INT 13 4Bxx etc :-(( Possible workaround: If INT 13 4B01 fails, scan for an AWARD Bios and the location of the correct INT 13 entry point, initialize the INT 13 vector and go on. I tried this with a quick'n dirty hack, it works fine. If you are interested in the code I could clean it up and add the scan part (I hardcoded the correct vectors for my machines) cu, Knut Knut Petersen Mittelgasse 4a D-36329 Romrod

Hi, First some background: ================== I had a test environment which had two samba DCs (running v 4.8.0rc2) and 1 Windows Server 2008R2 DC. The samba DCs had been upgraded from v 4.6x and the secrets database was not encrypted (as far as I know). I decided to downgrade one of the samba DCs to v 4.7.4. On re-starting samba after the downgrade the log shows: ldb: unable to dlopen

...db-module-samba4.so: version `SAMBA_4.8.0RC2' > not found (required by /usr/local/samba/lib/ldb/encrypted_secrets.so) when you are doing your downgrade, did you clean up all the /usr/local/samba directory or did you make && make install over the existing installation? If it was a quick'n dirty make && make install over the existing 4.8 install, could you try to do a install on a clean directory and then copy over etc/smb.conf, private/ and var/locks/? Cheers, Denis > > and the samba daemons are left in a failed state. > > So I removed this failed DC (...

...tions, leading to "connection reset"s ["connection closed" on client side in fact] (of course). My first reaction was something like "go UDP" but all i effectively need is SSH, so OpenVPN is much to fully blown for a bit of scp/ssh/git over ssh, and mosh (or a quick'n dirty shot with new OpenSSL and DTLS, plus pty plus sh) is a complete disruption of the workflow. And IPSec is really, really no no no. Looking around a bit i found RFC 4953, "Defending TCP Against Spoofing Attacks", and that mentions SCTP in a few places, e.g., "O...