ts_block
Chocolatey
ts_block | Chocolatey | |
---|---|---|
4 | 394 | |
175 | 9,894 | |
- | 1.1% | |
0.0 | 8.9 | |
over 2 years ago | 6 days ago | |
Visual Basic | C# | |
Artistic License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ts_block
-
Learning Lessons From The Cyber-Attack: British Library cyber incident review [pdf]
> Is there something inherently insecure about remote desktops, or is MS software here known to be particularly insecure...
Exposing RDP to the Internet directly has been frowned-upon because of the attack surface being presented, there's no two factor "story" out-of-the-box, and you're opened up to brute force attempts on cruddy user passwords.
Older versions of the Microsoft Remote Desktop Protocol had a much larger attack surface than current versions. The current versions with Network Level Authentication (starting in Windows Vista/Server 2008) present a smaller attacks surface. Older versions used "homegrown" Microsoft crypto, whereas current versions use TLS.
Disclosure: I made a FLOSS fail2ban-like tool for RDP many years ago[0]. I had a situation where I was forced to expose RDP to the Internet and I didn't like having it open w/o some protection against brute force attacks. This tool happens to still works in Server 2022 and will slow the velocity of brute force attacks. I still highly recommend not exposing RDP directly to the Internet anyway.
(The ts_block tool is missing some fairly essential functionality that I never got around to implementing. It works fine and is really easy to install but some things are sub-optimal.)
[0] https://github.com/EvanAnderson/ts_block
- Fail2Ban – Daemon to ban hosts that cause multiple authentication errors
-
Analysis of a large brute force attack campaign against Windows Remote Desktop
My old ts_block[0] project does something similar to yours, albeit for RDP only and with much less sophisticated customization.
I opted to go with a WMI Event Sink rather than polling the Event Log. I've never done a benchmark to see which architecture would use less CPU, but I can say the WMI event sink causes nearly instantaneous reaction.
As an aside: I'd love to hear if somebody tries ts_block on Windows Server 2022. It works fine on 2012 R2 thru 2019 but I've never tried it on 2022.
[0] https://github.com/EvanAnderson/ts_block
-
WinGet is terrible. I want AppGet back
The perspectives in the comments on this article re: WiX XML source and Windows Installer being difficult are interesting to me. Like I said elsewhere, I overcame that learning curve so long ago that I can't put myself in a position where it seems daunting now.
To be fair, though, an MSI to install a 10 files in "C:\Program Files\AppName", register a couple .NET assemblies, create a couple of shortcuts, and throw a few values into the registry would amount to <100 lines of XML.
Here's a years-old WiX 2.0 syntax source file to install 4 files in "C:\Program Files\appname" and run an EXE embedded in the MSI to install a service: https://github.com/EvanAnderson/ts_block/blob/master/MSI/ts_...
I've only seen "thousands of lines" of WiX source when dealing programs that install a ton of files, or put scads of entries in the registry.
Most of the MSIs with WiX are based on a simple skeleton generated from a template, and using "includes" generated by the "candle" tool.
Understanding the Windows Installer and the WiX source feels analogous to what I see in "modern" web development-- a bunch of tools that developers use, seemingly without understanding what they do, to create a massive pile of edifice into which original code is finally placed.
Chocolatey
-
Let’s build AI-tools with the help of AI and Typescript!
Chocolatey Windows software management solution, we use this for installing Python and Deno
-
Giving Kyma a little spin ... a SpinKube
Authenticating with Kyma is a (in my opinion) unnecessary challenge as it leverages the OIDC-login plugin for kubectl. You find a description of the setup here. This works fine when on a Mac but can give you some headaches on a Windows and on Linux machine especially when combined with restrictive setups in corporate environments. For Windows I can only recommend installing krew via chocolatey and then install the OIDC plugin via kubectl krew install oidc-login. At least for me that was the only way to get this working on Windows.
-
Effective Neovim Setup. A Beginner’s Guide
On a Windows machine, you can use Chocolatey by running the command.
- PC MHz fluctuating
-
Need Help with getting Haskell onto my Windows Laptop
I've used WSL2 and GHC/Nix--worked without any issues. However, there is Chocolatey: https://chocolatey.org/
-
Python Versions and Release Cycles
For OSX there is homebrew or pyenv (pyenv is another solution on Linux). As pyenv compiles from source it will require setting up XCode (the Apple IDE) tools to support this which can be pretty bulky. Windows users have chocolatey but the issue there is it works off the binaries. That means it won't have the latest security release available since those are source only. Conda is also another solution which can be picked up by Visual Studio Code as available versions of Python making development easier. In the end it might be best to consider using WSL on Windows for installing a Linux version and using that instead.
-
Helm Charts: An Organised Way to Install Apps on a Kubernetes Cluster
Type the following commands on the Windows terminal to install helm. You can use either Scoop a command-line installer for Windows or Chocolatey which is a Package Manager for Windows to install helm.
-
Was für Tools nutzt ihr zum Einrichten und Daten übertragen auf einen neuen PC?
Für Software ninite.com und chocolatey.org
- Criando ambiente de desenvolvimento Java no Windows - sem wsl
-
OpenAI Whisper: Transcribe in the Terminal for free
While you can install it in many ways, the easiest is using a package manager like Homebrew for macOS or chocolatey for Windows.
What are some alternatives?
Versions - 📦 A Scoop bucket for alternative versions of apps.
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Shovel-Ash258 - Personal Shovel bucket with a wide variety of applications of all kinds.
Scoop - A command-line installer for Windows.
oneget - PackageManagement (aka OneGet) is a package manager for Windows
Squirrel - An installation and update framework for Windows desktop apps
ts_block - Blocks IP addresses generating invalid Terminal Services logons
Wix Toolset
wix3 - WiX Toolset v3.x
HomeBrew - 🍺 The missing package manager for macOS (or Linux)
Main - 📦 The default bucket for Scoop.
video2x - A lossless video/GIF/image upscaler achieved with waifu2x, Anime4K, SRMD and RealSR. Started in Hack the Valley II, 2018.