cultural reviewer and dabbler in stylistic premonitions

  • 8 Posts
  • 67 Comments
Joined 3 years ago
cake
Cake day: January 17th, 2022

help-circle







  • security updates are for cowards, amirite? 😂

    seriously though, Debian 7 stopped receiving security updates a couple of years prior to the last time you rebooted, and there have been a lot of exploitable vulnerabilities fixed between then and now. do your family a favor and replace that mailserver!

    From the 2006 modification times, i wonder: did you actually start off with a 3.1 (sarge) install and upgrade it to 7 (wheezy) and then stopped upgrading at some point? if so, personally i would be tempted to try continuing to upgrade it all the way to bookworm, just to marvel at debian stable’s stability… but only after moving its services to a fresh system :)


  • why bother opening a pathway in the first place

    i’ve never had an IG account myself, but i think your mistake is in assuming that someone accepting your follow request on a restricted IG account is an indicator of desire for chatting with strangers. accepting your follow request might just mean they glanced at your profile and assessed that you aren’t a spammer or bot, not that they want to chat with you.

    perhaps just need to find out somewhere in the real world where I could bond more easily with real people?

    for sure that is a good idea 😂

    but there are also many places online where it is much more reasonable to assume people are interested in chatting with strangers.


  • Having some distrust in Wikipedia is healthy; you certainly shouldn’t take it as the final word about facts you’re depending on the accuracy of. But, it is very often a good starting point for learning about a new subject.

    Spending a minute or two reading that “source code” article (or another version of it which is likely available in your first language) would give you a much better understanding of the concept of source code (which is a prerequisite for understanding what “closed source” means) than any of the answers in this thread so far.









  • “Sorry, I got to return this video”

    2004 is when the Blockbuster video rental chain was at its peak (cite), and VHS was still in wide use at the time having only been surpassed by DVD rentals a year earlier. Speed dial was also still a thing then, payphones still exist today, and, although complaints were filed against Bill Cosby much earlier the public wasn’t widely aware of them until 2014.

    How about “John Kerry is the candidate who can prevent a second Bush term” ?



  • (disclaimer: this information might be years out of date but i think it is still accurate?)

    SSH doesn’t have a null cipher, and if it did, using it still wouldn’t make an SSH tunnel as fast as a TCP connection because SSH has its own windowing mechanism which is actually what is slowing you down. Doing the cryptography at line speed should not be a problem on a modern CPU.

    Even though SSH tunnels on your LAN are probably faster than your internet connection (albeit slower than LAN TCP connections), SSH’s windowing overhead will also make for slower internet connections (vs rsync or something else over TCP) due to more latency exacerbating the problem. (Whenever the window is full, it is sitting there not transmitting anything…)

    So, to answer OP’s question:

    • if you want to rsync over SSH, you usually don’t need a daemon (or to specify --rsh=ssh as that is the default).
    • if you the reason you want to use the rsync daemon is performance, then you don’t want to use SSH. you’ll need to open a port for it.
    • besides performance, there are also some rsync features which are only available in “daemon mode”. if you want to use those, you have at least 3 options:
      • open a port for your rsync daemon, and don’t use SSH (bonus: you also get the performance benefit. downside, no encryption.)
      • setup an SSH tunnel and tell the rsync client it is connecting to a daemon on localhost
      • look at man rsync and read the section referred to by this:
        • The remote-shell transport is used whenever the source or destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an rsync:// URL is specified (see also the USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION section for an exception to this latter rule).

    HTH.