little foxes at the keyboards little foxes making clicky-clacky little foxes on the servers little foxes all untame there's a black hat and a white hat and a grey one and fun for everyone! and they're all making clicky-clacky and they're all in your mainframe
If your XFCE panel (taskbar) disappears during your session - barring any severe persistent issues - you can revive it by either leveraging an open terminal session or, where none exists, you can launch the graphical command line by pressing Alt+F2 and running xfce4-panel.
To always run a shortcut's target under the Administrator account one will typically:
Right-click on the shortcut file in File Explorer
Click the Properties item in the context menu
Click the Advanced button
Check the Run as administrator checkbox
However, what is one to do when presented with a large batch of such files? Group-selecting them will reveal a Properties window of limited options, excluding the ability to mass-apply the Run as administrator option to the group.
To always run an executable under the Administrator account one will typically:
Right-click on the application file in File Explorer
Click the Properties item in the context menu
Navigate to the Compatibility tab
Check the Run this program as an administrator checkbox
Click the Apply button at the bottom of the Properties window
However, what is one to do when presented with a large batch of such files? Group-selecting them will reveal a Properties window of limited options, excluding the ability to mass-apply the Run this program as an administrator option to the group.
Counterintuitively, this property is not actually attached to the file itself. It is in fact set in the Windows Registry under the path HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers by making a new value for each path to an individual executable file and assigning it the String value RUNASADMIN
We can perform this action in bulk with a very terse little PowerShell scriptlet which you can paste directly into your session (running as Administrator), simply chdir (cd) to the desired directory to use unmodified:
The venerable Windows SysInternals Suite is perennially provided in an equally unflattering and flat zip file indiscriminately littered with executable tools and ersatz Compiled HTML HelpFiles (that's your handy-dandy *.chm for the uninitiated). One is left to install them as one sees fit, with no recommendations. I think there are reasonable guidelines we should expect and today I'll show you how I like to pack the pipe:
Most of the SysInternals tools require Administrator rights to start or function properly. We should avoid having to right-click and hit Run As Administrator every time we go to use one.
The executables should be stored in a sensible place
The tools should be easy to access, by GUI and CLI
My solutions are as follows:
Permanently install the SysInternals Suite applications and documentation to C:\Program Files\SysInternals\
Update the Windows PathEnvironment Variable to contain C:\Program Files\SysInternals\ so they may be called from the cmd.exe or PowerShell command line directly
To these ends, my installation recipe simmers thus:
Open PowerShell as Administrator (right-click, Run as Administrator). Run the following: mkdir "C:\Program Files\SysInternals"mkdir "C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SysInternals"
Extract the SysInternalsSuite.zip to C:\Program Files\SysInternals
Open C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SysInternals in File Explorer
In another File Explorer window open C:\Program Files\SysInternals in Details View
Sort the folder's contents by File Type. Select all Application files (all files ending in *.exe)
Using your right mouse button, drag the selected files over to the Start Menu entry's window. Choose Create Shortcuts from the context menu that opens when you release the right button.
Click the Environment Variables... button at the bottom of the System Properties window
Click on the PATH variable, then the Edit... button
Click the New button on the Edit environment variable window
Paste the path C:\Program Files\SysInternals into the new line that was created then click OK on each of the three open settings window to return to the Settings control panel, which you may now close
Return to your existing - or open a new - Administrator session of PowerShell (right-click and select Run as Administrator) and run the following commands and scriptlets to finalize your installation PS C:\Windows\system32> cd "C:\Program Files\SysInternals"
PS C:\Program Files\SysInternals> $files = Get-ChildItem ./ -Include *.exe; foreach ($f in $files)
{
$filename = $f.FullName
reg.exe ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" /v $filename /t REG_SZ /d "RUNASADMIN" /f
}
PS C:\Program Files\SysInternals> cd "C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SysInternals"
PS C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\SysInternals> $files = Get-ChildItem ./ -Include *.lnk; foreach ($f in $files)
{
$filename = $f.FullName
shortcutJS.bat -edit $filename -adminpermissions yes
}
The official Fedora guide (c. 2018) to installing the ever-popular ruby-based Metasploit automated scan-and-exploit framework is slightly outdated and indecisive. Please find below an updated quick installation recipe for your pleasure and leisure:
# RedHat Metasploit-Framework Installer
# https://foxpa.ws/install-metasploit-framework-on-redhat
# ---
# Obtain the latest release from GitHub
# You can git clone git://github.com/rapid7/metasploit-framework.git
# however I've had problems syncing on Qubes and the master .zip will always work.
# Consider using git for future updates. You may wish to add such to your crontab.
# Alternatively, use the Metasploit-hosted tarball at
# http://downloads.metasploit.com/data/releases/framework-latest.tar.bz2sudo bashcd /optwget https://github.com/rapid7/metasploit-framework/archive/refs/heads/master.zipunzip master.zipmv metasploit-framework-master metasploit
# Install Ruby dependencies
dnf -y install ruby-irb rubygems rubygem-bigdecimal rubygem-rake rubygem-i18n rubygem-bundlerdnf builddep -y rubydnf -y install ruby-devel libpcap-develgem install rake
# Install PostgreSQL (SQLite is no longer supported)
dnf -y install postgresql-server postgresql-develgem install pg
# Symlink the Metasploit tools to a PATH'd location:
ln -sf /opt/metasploit/msf* /usr/local/bin/
# Enable raw socket modules:
gem install pcaprub
# Install additional dependent Gems
bundle install --gemfile /opt/metasploit/Gemfile
You can download this script from https://foxpa.ws/files/install-metasploit.sh, simply chmod +x it executable and ./ it. In a few minutes you should be returned to a prompt with no user intervention necessary and a working installation of Metasploit.