Categories

  • 12.2k
    Topics
    113.1k
    Posts

    J

    Hello @JJ-Fullmer , hope all is well.
    First of all, thanks for creating that Powershell module for FOG to be used via Powershell.
    I have a question in regards to the script I’ve been using for a while. In it has the API for both the user and the FOG server.

    I want to be more secure in the sense of not putting the API in the script. I tried Microsoft’s module Secret Management and I can store both api keys under 2 different secrets. Here is the link from Microsoft: https://learn.microsoft.com/en-us/powershell/utility-modules/secretmanagement/get-started/using-secretstore?view=ps-modules

    But when I try to retrieve the secrets, I get the 403 forbidden message.

    Powershell variables for the both api keys for example: f8dcc28c-aef3-45c7-a765-1719c30df353-image.png

    Error message: 3cce1c57-e18b-4b3b-965b-aed75980c21c-image.png

    It will only work if I add -asplaintext for example:

    94f64f07-9835-4fac-8265-cda63d9de679-image.png

    It won’t take the System.Security.SecureString

    I double checked to make sure I’m using the correct fog and user api keys, but no dice.
    Is there a way to secure these API keys instead of putting them directly in the Powershell script and also not doing the command -asplaintext?

    If anyone has suggestions, please let me know.

  • Get the latest news on what's happening.
    Security Advisories
    184
    Topics
    825
    Posts

    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    General Tutorials
    2.4k
    Topics
    18.5k
    Posts

    J

    Do you think writing this in fog.man.reg after line

    [[ $exists != "#!ok" ]] && handleError "Unable to register host: $exists ($0)\n Args Passed: $*"

    could do it :

    host="" imageid="999" blDoAD="Y" realdoimage=$(echo -n 1 | base64) res="" user64=$(echo "fog" | tr -d '\012' | base64) pass64=$(echo "password" | tr -d '\012' | base64) while [[ $res != "#!ok" ]]; do echo -n " * Enter hostname for this computer: " read host if [[ ${#host} -gt 15 ]]; then host=${host:0:15} echo " | Truncated to 15 characters: $host" usleep 2000000 fi host=$(echo $host | base64) res=$(curl -Lks --data "host=$host" ${web}service/hostnameloop.php 2>/dev/null) [[ $res != "#!ok" ]] && echo "$res" done dots "Attempting to register host" res="" while [[ -z $res ]]; do res=$(curl -Lks --data "sysuuid=${sysuuid}&mac=$mac&advanced=$(echo -n 1 | base64)&host=$host&imageid=$imageid&doimage=$realdoimage&doad=$blDoAD&username=$user64&password=$pass64" ${web}service/auto.register.php 2>/dev/null) echo "$res" usleep 2000000 done . /bin/fog.inventory usleep 2000000

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2.3k
    Topics
    20.9k
    Posts

    R

    Requesting a feature addition in the “FOG Settings > FOG Email Settings” section that would allow an admin to test whether or not email is working. This would be similar to other programs that have a “test email” button with a box of who to send the test email to.

    Or perhaps some built in logic to test if postfix or other email prereqs that FOG needs to send email post image deployment.

135

Online

11.9k

Users

17.2k

Topics

155.0k

Posts