digitalohm
commented
4 years ago google for the win. here is the answer that fixed this on my system. I'll document all the steps in one spot for reference
Closed digitalohm closed 4 years ago
digitalohm
commented
4 years ago google for the win. here is the answer that fixed this on my system. I'll document all the steps in one spot for reference
digitalohm
commented
4 years ago Here is some rudimentary powershell that can take care of single file permissions. I'd probably update this later to take a filename as a parameter and get the user that is running the command. Also setting it as an aliased function so that it becomes a single command
Get-Acl "C:\Tools\Test\testfile" | Format-List
$acl = Get-Acl "C:\Tools\Test\testfile"
$AccessRule = New-Object System.Security.AccessControl.FileSystemAccessRule("COMMANDO\digitalohm","FullControl","Allow")
$acl.SetAccessRule($AccessRule)
$acl.SetAccessRuleProtection($true,$false)
$acl | Set-Acl "C:\Tools\Test\testfile"
Get-Acl "C:\Tools\Test\testfile" | Format-List
day1player
commented
4 years ago Thank you very much for posting the solution! The internet doesn't deserve you!
I'm trying to configure ssh so that I can use the predictable prng process as described here:
https://github.com/weaknetlabs/Penetration-Testing-Grimoire/blob/master/Vulnerabilities/SSH/key-exploit.md
I've created a ssh_config file located at: C:\ProgramData\ssh_config and added the lines below
The contents are:
This seems to be working however I get to the next error:
the specific error I'm targeting is:
on linux the fix here is a
chmod 600 f1fb2162a02f0f7c40c210e6167f05ca-16858and ssh will connect (tested successfully in kali, and kali container in docker)however, I've tried this on commando with
ls.exe chmod 600 f1fb2162a02f0f7c40c210e6167f05ca-16858and no diceI've been trying various folder level security combinations to get it working, however I'm not finding a way. Does anyone have any ideas on this one? Any help is appreciated