oleksdovz

Шукати в цьому блозі

k8s-hello-world

– лютого 11, 2023

Отримати посилання
Facebook
X
Pinterest
Електронна пошта
Інші додатки

Отримати посилання
Facebook
X
Pinterest
Електронна пошта
Інші додатки

Коментарі

Дописати коментар

Fixing "Security Warning: Untrusted VPN Server Certificate!" with CiscoAnnyConnect on Linux

Fixing "Security Warning: Untrusted VPN Server Certificate!" with Cisco AnnyConnect on Linux From Andreas Kotowicz - https://plus.google.com/+AndreasKotowicz/posts/2afhvvNZpE6 Fixing "Security Warning: Untrusted VPN Server Certificate!" with Cisco AnnyConnect on Linux After an update of the Cisco AnnyConnect Secure Mobility Client for Linux in September 2012, the following error message showed up every time while trying to connect with the VPN server: Security Warning: Untrusted VPN Server Certificate! AnyConnect cannot verify VPN server: serverName Certificate is from an untrusted source. Connecting to this server may result in a severe security compromise! What's funny about this error message is that it only shows up while trying to connect from Linux. Windows and MacOS don't seem to be affected. This is how I fixed it: # cd into hidden '.cisco' directory: $ cd /opt/.cisco/certificates # rename ca directory $ sudo mv ca ca...

MSSQL. Restore from network share

Map network drive/path, hosting file, under SAME user as MS-SQL Server. Use xp_cmdshell extended stored procedure to map network drive from inside of MS SQL -- allow changes to advanced options EXEC sp_configure 'show advanced options', 1 GO -- Update currently configured values for advanced options. RECONFIGURE GO -- To enable xp_cmdshell EXEC sp_configure 'xp_cmdshell', 1 GO -- Update currently configured values for advanced options. RECONFIGURE GO EXEC xp_cmdshell 'NET USE Z: \\Srv\Path password1 /USER:Domain\UserName' Afterwards drive Z: will be visible in Server Managment studio, or just RESTORE DATABASE DataBaseNameHere FROM DISK = 'Z:\BackNameHere.BAK' GO

Original link - http://michaelfranzl.com/2014/01/29/remote-server-hetzner-rebooting/ Now, in my case, I assumed that Grub2 was broken. So I activated the Hetzner Rescue System, booted into it, and reinstalled Grub2. I have found the following method here and it worked for me. First you have to mount the regular RAID filesystem under /mnt : mount /dev/md2 /mnt mount /dev/md1 /mnt/boot mount -t dev -o bind /dev /mnt/dev mount -t proc -o bind /proc /mnt/proc mount -t sys -o bind /sys /mnt/sys chroot /mnt mount /dev/md2 /mnt mount /dev/md1 /mnt/boot mount -t dev -o bind /dev /mnt/dev mount -t proc -o bind /proc /mnt/proc mount -t sys -o bind /sys /mnt/sys chroot /mnt At this point, you are in your regular root directory. To reinstall Grub2 the Debian Way, I did: apt-get install --reinstall grub-pc apt-get install --reinstall grub-pc To make really sure, I reconfigured the package: dpkg-reconfigure grub-pc 1 dpkg-reconfigure grub-pc It will ask you where to...

На платформі Blogger