Shared Script Library

scanaan
scanaan Member Posts: 1 ✭
in Scripts

Does anyone "vet" these scripts before they are allowed to be cloned? I have tried numerous scripts and they either do not work or they do more harm than good. I used one today named "
Disable SMB1 and Enable SMB2" and it completely butchered multiple registry entries. It would be great if we could give feedback on these scripts as we attempt to use them so that others can be alerted to their effectiveness or ineffectiveness.

Comments

  • COOLNETAU
    COOLNETAU Member Posts: 58 ✭✭

    whilst I agree, we need to check any unvetted code before we deploy it. lesson learned here (personally).

  • gilgi
    gilgi Administrator, Moderator, Internal Posts: 294 admin

    Heya,
    This is something that I'm personally looking into, and your feedback is very relevant.

    We've recently improved the reviewing SLA for new scripts, feedback would be a great addition in this area, and I'll note this request in my reporting.

    Currently, the following applies:

    Scripts won't appear in the Shared Script Library until reviewed and approved by a moderator, and will be visible to you under 'Pending' status. We look for malicious code to ensure your and our community's security.
    Scripts are reviewed monthly.

    Moderation will either:
    Approve your script: The status of the script will change to 'Approved' (you'll receive an email confirming this). It'll then appear in the Shared Script Library.
    Reject the script: The status of the script will change to 'Rejected' (you'll receive an email confirming this).

    While we don't currently provide rejection notes, you can review your rejected script and clean it from any unintended malicious code, or consult with the community for peer reviewing.

Topics