• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: August 5th, 2023

help-circle
  • Our system wasn’t quite as critical, thankfully, but the app owners failing to respond to “Hey, by the way, your service account for your data base is gonna be closed” is just gross negligence. My condolences that you had to take the brunt of their scrambling to cover their asses.

    For all the complaints I may have about certain processes and keeping certain stakeholders in the loop about changing the SQL Views they depend on, at least I acknowledge that plenty of people did heed the announcement and make the switch. It’s just that the “Oops, that mail must have drowned in my pile of IDGAF what our sysadmins are writing about again. Can’t you just give me the new password again, pretty please?” are far more visible.


  • luciferofastora@discuss.onlinetoMemes@lemmy.mlOur Computer
    link
    fedilink
    arrow-up
    23
    arrow-down
    1
    ·
    1 year ago

    They probably have to recite a standard company line, gritting their teeth as you both know it’s bullshit.

    I don’t envy customer service reps. Most of them probably didn’t apply for the job because they love Microsoft or enjoy the prospect of fielding frustrated customers’ calls.


  • We had that some time ago with a service account for a specific system where individual personal accounts weren’t (yet) feasible. The credentials were supposed to be treated with confidence and not shared without the admins’ approval. Yeah, you can guess how that went.

    When the time came to migrate access to the system to a different solution using personal accounts, it was announced that the service account password would be changed and henceforth kept under strict control by the sysadmin, who would remotely enter it where it was needed but never hand it out in clear text. That announcement was sent to all the authorised credential holders with the instruction to pass it on if anyone else had been given access, and repeated shortly before the change.

    The change was even delayed for some sensitive reasons, but eventually went through. Naturally, everyone was prepared, had gone through the steps to request the new access and all was well. Nobody called to complain about things breaking, no error tickets were submitted to entirely unrelated units that had to dig around to find out who was actually responsible, and all lived happily ever after. In particular, the writer of this post was blissfully left alone and not involuntarily crowned the main point of contact by any upset users passing their name on to other people the writer had never even seen the name of.








  • I can’t comment on the general trend, but this specific one seems a bit too circumstantial to be of use for a serious spying effort. You’d have to have the spyware running parallel to the apps usong passwords you want to steal in a specific way.

    The risk exists, which is bad enough for stochastic reasons (eventually, someone will get lucky and manage to grab something sensitive, and since the potential damage from that is incalculable, the impact axis alone drives this into firm "you need to get that fix out asap), but probably irrelevant in terms of consistency, which would be what you’d need to actually monitor anyone.

    If you manage to grab enough info to crack some financial access data, you can steal money. If you can take over some legit online account or obtain some email-password combo, you can sell it. But if you want to monitor what people are doing in otherwise private systems, you need some way to either check on demand or log their actions and periodically send them to your server.

    It would be far more reliable to have injection backdoors to allow you access by virtue of forcing a credential check to come up valid than to hope for the lucky grab of credentials the user might change at an arbitrary moment in time.


  • Fuck printers, and fuck personal printers.

    I’m not in tech support, thankfully, but in a network-oriented role and trying to hunt down just what the fuck kind of device is associated with a given IP and who is responsible for it is a nightmare when you’ve got an inventory system where “DHCP” is a valid entry for IPs, hostnames are optional, manually entered and not validated against some uniform pattern, serial number entries that differ from the actual device’s in several possible ways and no MAC-Address…

    Assuming they’re logged in the inventory at all, that is.




  • You mean the magazine would pay people to write a story people would want to read… only to make money for the magazine? Like, they’re doing it for profit, and not out of the goodness of their hearts? Next you’re going to tell me my grocer is only selling me food to generate revenue.

    There’s a difference between “just marketing” and “buy this stuff, but also, turns out Lebanon has quite some distance to go in terms of human rights in general and gender equality in particular”. Companies can’t have morals, because they’re not a natural person, but the humans working for them can, and it’s not unthinkable for this story to be both: An expression of moral frustration on part of the journalist that also happens to be profitable for their employer.



  • What, 2023-223 for the 223rd day of the year 2023? That… is oddly appealing for telling the actual progress of the year or grouping. No silly “does this group have 31, 30, 29 or 28 members”, particularly the “is this year a multiple of four, but not of 100, unless it’s also a multiple of 400?” bit with leap days.

    You’ll have oddities still, no matter which way you slice it, because our orbit is mathematically imperfect, but it’s a start.



  • Together with hh:mm(:ss) for times and +hh:mm for timezones. Don’t make me deal with that 12am/pm bullshit that doesn’t make any sense, and don’t make make me look up just what the time difference is between CEST and IST. Just give me the offsets +02:00 and +05:30, and I can calculate that my local time of 06:55+03:30=10:25 in India.



  • The whole point of making a federated network of independent instances is to avoid the issues arising with one central instance, right? Putting the content out to multiple instances plays into that: If it’s important content, no single authority can easily censor it, and the loss of a single instance won’t erase it.

    If it’s trash, of course, every community in every instance you post it to will have to clean it up separately. Arguably, that puts more strain on the respective moderation teams, but if (ideally) those are disjunct people (again, to avoid the issues of a single authority), the strain should be distributed.

    And on the plus side, it would enable each community (in the lemmy sense) to enforce their own nuanced rules, additionally leading to slightly more choice between the types of moderation you favour (as opposed to “There’s one big sub, take it or leave it”).

    Individual communities may be smaller, but maybe some more form of coordination of similar communities across instances could amend that (like linking to the other communities in your sidebar etc.).

    I could also imagine a super-community solution that would allow you to aggregate several communities across instances similar to multireddits. I’m new here, so I’m not sure if that exists, nor have I given the implementation any thought, but I suppose that could be convenient.