@scottalanmiller said in Script to Move and Decrypt Files in a Specified Directory:

@wirestyle22 said in Script to Move and Decrypt Files in a Specified Directory:

and place it in a specific directory that will be used by the load process

What's the reason for needing to move it, decrypt it, and move it again? Isn't that unnecessary steps? Or can it not be decrypted where it first gets put?

yes, it can't. someone else is dictating where the files and placed and then where they are moved to

@JaredBusch said in Script to Move and Decrypt Files in a Specified Directory:

@wirestyle22 said in Script to Move and Decrypt Files in a Specified Directory:

jaredisacuddlebear

I don’t do the furry scene. Sorry.

If you did, what animal would you be?

I am playing with PGP keys for a project I am working on and the next phase requires a script to be written. This is what the script needs to do:

• Move the encrypted file into an archive.
• Decrypt the file and place it in a specific directory that will be used by the load process which an application team will be creating.

Once the load process is complete, the decrypted file will be deleted outside of the script.

I found this in my search:

@ECHO off
mv /directory/*.gpg /home/service_account/directory
SET password=jaredisacuddlebear
PUSHD "/path/to/directory"
FOR /F "tokens=+" %%F IN ('DIR * .gpg /B') DO (
        gpg --output "&&~nF" --batch --yes --passphrase %password% --decrypt "%%F")
POPD

I haven't had the opportunity to test it yet, but does this look correct? There are parts of it I'm not sure about.

Outward has been very fun

@Grey said in What Are You Watching Now:

@scottalanmiller said in What Are You Watching Now:

Murder She Wrote

Why?

Excellent question

This is going to be a great weekend. I just finished 3 big projects today.

The below script finds the permissions for the directory, but goes all the way through the entire file structure.

$FolderPath = dir -Directory -Path "P:\Public" -Recurse -Force
$Report = @()
Foreach ($Folder in $FolderPath) {
    $Acl = Get-Acl -Path $Folder.FullName
    foreach ($Access in $acl.Access)
        {
            $Properties = [ordered]@{'FolderName'=$Folder.FullName;'AD
Group or
User'=$Access.IdentityReference;'Permissions'=$Access.FileSystemRights;'Inherited'=$Access.IsInherited}
            $Report += New-Object -TypeName PSObject -Property $Properties
        }
}
$Report | Export-Csv -path "C:\export\permissions.csv"

I need to go only two levels deep. I read that you can use Get-ChildItemToDepth but I am having trouble with the syntax if anyone can help.

@jt1001001 said in What Are You Doing Right Now:

More layoffs at my company today; who knows I may be one of them ugh

Hopefully not man. It's tough out there right now

@VoIP_n00b said in Jared - OBS:

@stacksofplates Are you @JaredBusch?

I'm @JaredBusch

When I buy a movie I should be able to do whatever I want with it. I go through this frustration every few years. It's so annoying when you try to watch content you can't get ahold of either due to the country you live in or it being out of print. DRM is stupid