• 0 Posts
  • 1.08K Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle





  • Huge difference, Ukraine military operations were for a long time purely defensive, only engaging in their own territory. Now they are starting to target military facilities in Russian territory more with no evidince of excessive collatoral damage, which is still understandable. If Russia withdrew offensive forces, Ukraine would not be trying to ‘wipe out’ Russia.

    Versus Israel where just tremendous indiscriminate operations are inflicting more ‘collateral’ damage than what would be considered understandable targets for deliberate damage. I think the world might have been pretty fine with surgical incursions against Hamas and Hezbollah, but Israel has not displayed that discipline.






  • Problem they had was that ssh doesn’t really have any way to enforce details of how the client key manifests and behaves. They could ship out the authentication devices after the security team trusted the public key, but that was more than they would have been willing to deal with.

    Rotating the passphrase in the key wouldn’t do any good anyway. If an attacker got a hold of your encrypted key to start guessing the passphrase, that instance of the key will never know that another copy has a passphrase change.







  • As I said, I’ve dealt with logging where the variable length text was kept as plain text, with external metadata/index as binary. You have best of both worlds here. Plus it’s easier to have very predictable entry alignment, as the messy variable data is kept outside the binary file, and the binary file can have more fixed record sizes. You may have some duplicate data (e.g. the text file has a text version of a timestamp duplicated with the metadata binary timestamp), but overall not too bad.



  • I still have weird glitches where applications don’t seem to update on screen (chrome and firefox, both natively doing wayland).

    Lack of any solution for programmatic geometry interaction. This one has been afflicted with ‘perfect is enemy of good’, as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative.

    The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The ‘share your screen’ was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened.

    Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent.

    I’ve been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts.


  • Thing is that they could have preserved the textual nature and had some sort of external metadata to facilitate the ‘fanciness’. I have worked in other logging systems that did that, with the ability to consume the plaintext logs in an ‘old fashioned’ way but a utility being able to do all the nice filtering, search, and special event marking that journalctl provides without compromising the existence of the plain text.