Today's mini-project: got SSH going on Caldera 1.1.
First I tried Ylönen SSH 1.2.12, which built and ran fine but gave packet checksum errors when I tried to log in with #PuTTY. Next was OSSH 1.2.16, which also built and ran fine (after tracking down the needed libs) but did the same thing. Finally I tried OSSH 1.5.12, the last pre-OpenSSH release I could find. That worked! No more telnet! :NinetiesConfetti:
Tradeoffs.
Microsoft Terminal does italics, strikethrough, and invisible properly, but it does underlining at the glyph baseline, making some characters difficult to read.
MobaXTerm's built-in PuTTY places underlining properly *under* the glyphs, but does not handle italics, strikethrough, and invisible at all.
Настройка SSH для коммитов в репозиторий
Итак вам надо клонировать репозиторий с компанейского репозитория и git просит какие-то непонятные пароли. Знакома ситуация? В этой заметке я написал как настроить ssh ключи.
https://habr.com/ru/articles/746810/
#ssh #putty #GitLab #git #PuTTYgen #pageant #plink #Рassphrase #GIT_SSH
I found out that the way PuTTY stores the server finger print is different from the way OpenSSH does do it:
OpenSSH takes the hostname you provide, so foo and foo.example.net are two different ones, even if the search domains (in /etc/resolv.conf for example) makes it so that foo is actually foo.example.net.
PuTTY on the other hand looks at the DNS name, so if your foo which before pointed to foo.example.net now suddenly points to the CNAME of foo.example.net which points to bar.example.net, it will complain.
It will not properly complain. It will still say "I don't know the server fingerprint for foo", but at the top left of the PuTTY window title bar it will show "bar.example.net" instead of the expected name "foo.example.net" and that is the only indication on what went wrong.
So much for a "Let's prepare this change in DNS so that it will be transparent for users" 🙂
Recently I wanted to test #backrest on a Windoze machine using #plink (part of #PuTTY) to connect backup repository on a Linux server. Turns out: you can't do this. While it is working using #restic from the command line with somethng like
restic -o sftp.command="'./plink.exe' -s backupserver sftp" -r sftp:backupserver:path/to/repository <restic command>
it is failing if you are using that sftp.command part as a flag in #backrest repository configuration.
1/3
If you're on phone, the Termux app can work as a PuTTY replacement, and when combined with the screen command, you can host multiple game servers on one Linux machine!
Advantage of using work-specific VMs when using personal equipment for "work from home": when you're required to install work-specific software.
My company's partnering with another cloud asset-reporting vendor. Vendor needed us to set up an instantiation of their product in one of our #AWS accounts. The AWS account in question is configured to only allow access via VPN.
The #VPN software my company uses for that account is Tailscale. Didn't particularly feel like installing it to my (whole) laptop, so, I opted to install it into an EL9 #Linux VM (between PuTTY — I use PuTTY-CAC because I have projects that require me to be able to SmartCard passthrough — and VcXsrv
Why don't I use a work-supplied laptop for work tasks? I live in a very small house with not a lot of area — especially not to dedicate to work-specific hardware. So, I refused the work-issued laptop: while space was the primary driver of that refusal, it's also the fact that work normally issues MBPs …and I'm the opposite of a Mac fan (that said, they had offered to get me the PC of my choice running the OS of my choice, but that still leaves the "house too smol" problem to surmount).
At any rate, a locally-installed hypervisor allows me to get around the "how to keep work and personal separate" question.
#PuTTY
#VcXsrv
Raspberry Pi als Heimserver – #3 – FreshRSS
Es ist eine Weile her, seit ich den letzten Beitrag meiner "Raspberry Pi als Heimserver"-Reihe veröffentlicht habe. Am 17.09.2023 habe ich euch im zweiten Teil gezeigt, wie ihr OpenMediaVault und Docker inklusive Portainer installiert. Heute möchte ich euch einen spannenden Dienst vorstellen, der euren Heimserver bereichern wird: FreshRSS. […]
@deepthoughts10 @SophosXOps @thepacketrat
Any person, who'll try to block #putty for "security" reasons on my workplace will probably get the most spiky CPU cooler I'd be able to find around shoved down their asshole as a last move before I leave the building forever.
UPD the same is true for 7Zip.
Finally found out how to disable that press-enter-to-complete-paste thing.
On the bash shell (and login again):
[edwin@sg-shared-oel9 ~]$ cat .inputrc
set enable-bracketed-paste off
Or in the PuTTY configuration, see image:
Wer #putty verwendet, hat die Kontrolle über sein Leben verloren.
-- Karl Lagerfeld
How to Fix a Nutanix CVM Stuck in Maintenance Mode | https://techygeekshome.info/how-to-fix-a-nutanix-cvm-stuck-in-maintenance-mode/?fsp_sid=16343 | #Guide #Hyperconvergence #Nutanix #PuTTy #SSH #Virtualisation
https://techygeekshome.info/how-to-fix-a-nutanix-cvm-stuck-in-maintenance-mode/?fsp_sid=16343
How to Fix a Nutanix CVM Stuck in Maintenance Mode | https://techygeekshome.info/how-to-fix-a-nutanix-cvm-stuck-in-maintenance-mode/?fsp_sid=16342 | #Guide #Hyperconvergence #Nutanix #PuTTy #SSH #Virtualisation
https://techygeekshome.info/how-to-fix-a-nutanix-cvm-stuck-in-maintenance-mode/?fsp_sid=16342
Always nice when software developers have thought of the thing you wanted already.
When #git on my laptop wants to talk to my machine at home (usually to continue work on something I left half-finished, append another commit or two, and push it back to my home checkout), it has to use #PuTTY rather than OpenSSH, because only my PuTTY configuration knows how to find its way to that machine. So I have to set either GIT_SSH or core.sshCommand to "plink". Ideally the latter, and only in the context of that one checkout.
What this _really_ needs, I thought, is an option to 'git clone' that will set an arbitrary 'git config' option early enough to affect the actual cloning operation, and then leave it set in the resulting checkout. That'd be perfect. I wonder if the git developers have thought to provide one?
And they have! #TIL 'git clone -c key=value'.
git clone -c core.sshCommand=plink my-home-machine:src/half-finished-thing
[screenreader users, the following contains a lot of non-alphabet characters]
Fix/Workaround for me - still interested in info:
SendEnv LANG LC_* in my *local* .ssh/config
ls output is now 'Árstíðir - Hvel' etc etc
Update:
I am going to point towards #tmux and #WindowsTerminal here too, I can paste "Árstíðir - Hvel - 12 Unfold.flac" but touching a file with UTF-8 characters causes the same issues.
#PuTTY displays it correctly! The only difference I can see is that LANG="en_AU.UTF-8" is exported.
#Linux friends, what do I do with a filename like "''$'\303\201''rst'$'\303\255\303\260''ir - Hvel - 12 Unfold.flac'"? (https://arstidirsom.bandcamp.com/album/hvel if you're wondering)
The correct, or original filename from the zip file is "Árstíðir - Hvel - 12 Unfold.flac"
If I set LANG to something with UTF-8, I get _rst__ir - Hvel - 12 Unfold.flac, but ls *12\ Unfold.flac does not find it.
What's the equivalent of hexdump for filenames? This particular example is on ZFS but I have seen the same on ext4 and btrfs so I am sure it's not (entirely) filesystem specific.
If you search for this answer, what keywords did you use? I am having trouble here.
