Try putting -vvv when you connect and see what’s happening. I can imagine this happening if you have multiple identities (private/public key pairs) on the client and you hit a max retry limit. Pub key is always tried first, and it should ask for password once all the local keys have been tried.
Mr Krab there surely doesn’t have the same customers I have, if he’s so relaxed
At least once, yes
Thank you and all the others that took time to educate me on what is for me a “I know some of those words” subject
At the cost of sounding naive and stupid, wouldn’t it be possible to improve compilers to not spew out unsafe executables? Maybe as a compile time option so people have time to correct the source.
Like the S in IoT stands for security. Got it.
Boh, my average experience is “apt install foo”. Let’s not perpetuate myths.
What kind of prompt does your company 2FA provide? Using openconnect with networkmangler, I get a pop up to input my pin+totp. I haven’t done the script way in the last few years, but the connection script is plain shell and I was able to handle the 2FA from there too
For anyconnect: openconnect works perfectly, either as standalone script or via networkmangler.
Unfortunately falcon self updates. And it will not work properly if you don’t let it do it.
Also add “customer has rejected the maintenance window” to your list.
USAF started removing marks form transport and other large planes about one year ago.
There’s an even worse thing: timezone selection UIs that don’t let you choose UTC
It was a struggle. You went to buy some device and you had to check it was not one of those windows-only ones. Modems were particularly bad, for example.
You had to read the how-tos and figure things out. Mailing lists and newsgroups were the only places to find some help.
You had to find the shop willing to honour warranty on the parts and not on the whole system, as they had no knowledge of Linux at all. But once you found them, you were a recurring customer so they were actually happy. You might even have ended up showing them memtest86!
You would still be able to configure the kernel and be able to actually know some of those names, compilation would take several hours but it was a learning experience.
You could interact with very helpful kernel developers and get fixes to test.
You could have been the laughing stock of your circles of friends, but within you, you knew who’d have had the last laugh.
And yes, Loki games had some titles working on Linux natively, Railroad Tycoon was one. Too bad they were ahead of the times and didn’t last much.
You can choose KDE as desktop environment during Debian installation, or replace whatever DE you installed at any time.
Oh, come on, did you really have to pull emacs into this crossfire? Leave us weirdos alone!
It is very usable, provided you pay attention to major upcoming changes. To give you a very recent example, during May they switched the time libraries to use 64 bits, and like others said, it was dependency hell until the tide of all the packages being recompiled passed. In those cases, unless you know EXACTLY what to do, it’s better to wait for updates to come in, let apt sort out what could be updated and what had to wait, and just make sure it doesn’t propose you to delete things. After 2 weeks it was all business as usual. Side note: aptitude (my package manager of choice) was unusable, while apt threaded on and pulled me out of the tangle.
I tried once. Could not figure it out. I’ll leave that to the young people.
Comedy can be staged and still be funny. It’s acting.