• 1 Post
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle



  • If paying on a monthly basis, as soon as you pay for 12 consecutive months, you will receive this perpetual fallback license providing you with access to the exact product version for when your 12 consecutive months subscription started. You will receive perpetual fallback licenses for every version you’ve paid 12 consecutive months for.

    So, in your example, you unsubscribe in month 15. This means, you paid 14 months so you get to retain the version from month three (which is 12 full paid months to 14). This means a downgrade to 1.0.x and not to 1.2.x



  • I remember having a defective hdd in my PC. I brought the pc to the shop, where I bought it from to get it replaced under warranty. They told me they couldn’t restore my data (I had backups) and asked if I wanted them to install windows on it. When they asked for my key I was like “FC…” and they responded “ok, we know that one, no need to spell it out” and proceeded with the installation





  • The first one kinda works, but I think it’d be more clear, when used without “selbst”/self, as this would be read to reference the invention instead of the inventor.

    On the other hand, that then feels like “yeah, it didn’t work. The invention misfired and is crap”. Maybe “Erfindungserschafferzerstörer”? (Invention’s creator destructor) but that sounds off, too.

    There’s not really a word that I can come up with that really conveys this meaning. There’s a german saying “wer Andern eine Grube gräbt, fällt selbst hinein” (he, who digs a hole for others, will fall into it by itself). Then there’s the humorous “Rohrkrepierer” (along the lines of “died in the barrel”) which basically means something like “dead on arrival” / that went wrong and didn’t work. So it’d be probably something that references one of those, which would make it work culturally?




  • elvith@feddit.detolinuxmemes@lemmy.worldmv Windows Linux
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    7 months ago

    I found a blog post outlining exactly that. If you use it locally, it will install and start a service temporarily. That service runs as SYSTEM and invokes your command. To succeed, you need to be a local administrator.

    If you try the same remote, it tries to access \\remote-server-ip\$admin and installs the service with that. To succeed your current account on your local machine must exist on the remote machine and must be an administrator there.

    So in short: It only works, if you’ve already the privilege to do so and the tool itself is not (ab)using a privilege escalation or something like that. Any hacker and virus may do the very same and doesn’t need psexec - it’s just easier for them to use that tool.


  • Never thought about that, but since these tools just work, when you copy them to your PC… how does psexec do that? It’d either need you to be an administrator (and then it’s not really a privilege escalation as you could have registered any program into the task scheduler or as a service to run as SYSTEM) or it’d need a delegate service, that should only be available when you use an installer - which again wasn’t was has been done when just copying the tool.