• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • I have just dumped code into a Chrome console and saved a cert while in a pinch. It’s not best practices of course, but when you need something fast for one-time use, it’s nice to have something immediately available.

    You could make your own webpage that works in the browser (no backend) and make a cert. I haven’t published anything publicly because you really shouldn’t dump private keys in unknown websites, but nothing is stopping you from making your own.









  • ShortFuse@lemmy.worldtoMemes@lemmy.mlplease
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    4 months ago

    No. Microsoft is not liable, at least when it applies to HIPAA.

    The HIPAA Rules apply to covered entities and business associates.

    Individuals, organizations, and agencies that meet the definition of a covered entity under HIPAA must comply with the Rules’ requirements to protect the privacy and security of health information and must provide individuals with certain rights with respect to their health information. If a covered entity engages a business associate to help it carry out its health care activities and functions, the covered entity must have a written business associate contract or other arrangement with the business associate that establishes specifically what the business associate has been engaged to do and requires the business associate to comply with the Rules’ requirements to protect the privacy and security of protected health information. In addition to these contractual obligations, business associates are directly liable for compliance with certain provisions of the HIPAA Rules.

    If an entity does not meet the definition of a covered entity or business associate, it does not have to comply with the HIPAA Rules. See definitions of “business associate” and “covered entity” at 45 CFR 160.103.

    https://www.hhs.gov/hipaa/for-professionals/covered-entities/index.html


  • ShortFuse@lemmy.worldtoMemes@lemmy.mlplease
    link
    fedilink
    arrow-up
    18
    ·
    edit-2
    4 months ago

    HIPAA doesn’t even require encryption. It’s considered “addressable”. They just require access be “closed”. You can be HIPAA compliant with just Windows login, event viewer, and notepad.

    (Also HIPAA applies to healthcare providers. Adobe doesn’t need to follow HIPAA data protection, though they probably do because it’s so lax, just because you uploaded a PDF of a medical bill to their cloud.)









  • ShortFuse@lemmy.worldtoMemes@lemmy.mlsIGmA BeHaiovouR
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    7 months ago

    Steam has limited rollback support from the command line which we had to do plenty of times for Starfield when working on Luma. Sometimes updates are small. Sometimes the entire exe gets reshuffled so you have to find where to patch the exe all over again.

    All the versions are apparently there. You just need to download the “depot” and it’ll dump into a folder. From there you copy that folder over your game directly.

    It also works the other way around. I can download the depot for the latest version and stay on the version I’m at. It’s useful to pick apart and diff what was actually changed.

    Why they can’t add that as an option I’m not sure. That seems more of a UX/UI issue rather than a technical one (like avoiding people using old versions on the web server).


  • I was about to mod the game for HDR and then found out news of FO4 getting updated.

    Updates break mods. Just how it is. Though, after seeing the work needed for modding Starfield after each exe change, I’m doing shader replacement now. As long as they don’t change from DirectX, I should be good.