kb is a text-oriented minimalist command line knowledge base manager. kb can be considered a quick note collection and access tool oriented toward software developers, penetration testers, hackers, students or whoever has to collect and organize notes in a clean way. Although kb is mainly targeted on text-based note collection, it supports non-text files as well (e.g., images, pdf, videos and others).
The project was born from the frustration of trying to find a good way to quickly access my notes, procedures, cheatsheets and lists (e.g., payloads) but at the same time, keeping them organized. This is particularly useful for any kind of student. I use it in the context of penetration testing to organize pentesting procedures, cheatsheets, payloads, guides and notes.
I found myself too frequently spending time trying to search for that particular payload list quickly, or spending too much time trying to find a specific guide/cheatsheet for a needed tool. kb tries to solve this problem by providing you a quick and intuitive way to access knowledge.
In few words kb allows a user to quickly and efficiently:
collect items containing notes,guides,procedures,cheatsheets into an organized knowledge base;
filter the knowledge base on different metadata: title, category, tags and others;
visualize items within the knowledge base with (or without) syntax highlighting;
grep through the knowledge base using regexes;
import/export an entire knowledge base;
Basically, kb provides a clean text-based way to organize your knowledge.
GitHub CLI brings GitHub to your terminal. It reduces context switching, helps you focus, and enables you to more easily script and create your own workflows. Earlier this year, we announced the beta of GitHub CLI. Since we released the beta, users have created over 250,000 pull requests, performed over 350,000 merges, and created over 20,000 issues with GitHub CLI. We’ve received so much thoughtful feedback, and today GitHub CLI is out of beta and available to download on Windows, macOS, and Linux.
With GitHub CLI 1.0, you can:
Run your entire GitHub workflow from the terminal, from issues through releases
Call the GitHub API to script nearly any action, and set a custom alias for any command
Connect to GitHub Enterprise Server in addition to GitHub.com
Endlessh is an SSH tarpit that very slowly sends an endless, random SSH banner. It keeps SSH clients locked up for hours or even days at a time. The purpose is to put your real SSH server on another port and then let the script kiddies get stuck in this tarpit instead of bothering a real server.
Since the tarpit is in the banner before any cryptographic exchange occurs, this program doesn't depend on any cryptographic libraries. It's a simple, single-threaded, standalone C program. It uses poll() to trap multiple clients at a time.
query-json is a faster and simpler re-implementation of the jq language in Reason Native and compiled to binary thanks to the OCaml compiler. query-json, allows you to write small programs to operate on top of json files in a cute syntax:
I wrote a post over the weekend which said a lot about libraries letting people down, and other people becoming overly dependent on them. There was an aside of sorts in there which mentioned teaching people about all of the things to look out for when you're writing to a file on a Unix-ish/POSIX-ish filesystem situation. A friend reached out asking if I had a post talking about that stuff, and near as I can tell, I do not.
That brings us to right now. I will attempt to lay down a few things that I keep in mind any time I'm creating files.
Linking-it-all-together asks: I came across this article about the benefits of static linking over dynamic linking. If dynamic linking is slower and doesn't offer practical benefits then why do most distros still dynamic link? Is this a hold over from the past or is there a reason I'm missing that make distros still use dynamic linking?
DistroWatch answers: I read through the article provided and it does share some interesting statistics on dynamically linked programs versus statically linked programs. The author appears to be making a case against dynamic linking and in favour of static linking, or at least presenting facts which would support such a case. For the sake of this discussion I am going to assume the observations the article's author makes are accurate and factually correct, at least for their own distribution.
The author addresses some interesting questions, such as how often are dynamically libraries used on the system, which indicates how many resources avoid duplication by sharing libraries. They also explore how quickly dynamic and static programs load and how much larger statically linked programs are compared to their dynamically linked counterparts. The author points out that many libraries on their distribution are not shared by many programs, that statically linked programs can load faster, and that not a lot of bandwidth is saved by using dynamically linked programs.
Reading through the page of observations the author shares, it's understandable we might wonder why developers continue to favour dynamically linked applications in most situations. Let's look at some of the specific arguments from the article.
There are quite a few things that set Zork and other Infocom games apart from the competition. For one, Infocom games had creative, addictive puzzles and mazes that drove players batty. Some gamers even wrote Infocom letters, asking for a hint to help them get past particularly tough brain teasers.
Crush is an attempt to make a traditional command line shell that is also a modern programming language. It has the features one would expect from a modern programming language like a type system, closures and lexical scoping, but with a syntax geared toward both batch and interactive shell usage.
What features of a traditional shell does Crush retain?
The basic structure of the Crush language resembles a regular shell like bash.
How to invoke commands, pass arguments and set up pipelines are unchanged, as is the central concept of a current working directory. This means that trivial invocations, like ls or find .. | count look the same, but under the hood they are quite different, and nearly everything beyond that is different.
Pywal is nifty Python-based command line tool that changes the terminal colors based on the colors of that wallpapers.
You can use it to set the wallpaper and you’ll see that the terminal colors change immediately.
This week’s events in Wall Street and the City of London mark this turning point – the historic moment that future historians will undoubtedly pick to say: It was in the summer of 2020 when financial capitalism finally broke with the world of real people, including capitalists antiquated enough to try to profit from producing goods and services.
from 2008 to 2020, the policies to re-float the banking sector from 2009 onwards resulted in the almost complete zombification of corporations. Covid-19 found capitalism in this zombified state. With consumption and production hit massively and at once, governments were forced to step into the void to replace all incomes to a gargantuan extent at a time the real capitalist economy has the least capacity to generate real wealth. The decoupling of the financial markets from the real economy, that was the trigger for this talk, is a sure sign that something we may defensibly label postcapitalism is already underway.
ytt (pronounced spelled out) is a templating tool that understands YAML structure. It helps you easily configure complex software via reusable templates and user provided values. Ytt includes the following features:
Structural templating: understands yaml structure so users can focus on their configuration instead of issues associated with text templating, such as YAML value quoting or manual template indentation
Built-in programming language: includes the "fully featured" Python-like programming language Starklark which helps ease the burden of configuring complex software through a richer set of functionality.
Reusable configuration: You can reuse the same configuration in different environments by applying environment-specific values.
Custom validations: coupled with the fast and deterministic execution, allows you to take advantage of faster feedback loops when creating and testing templates
Overlays: this advanced configuration helps users manage the customization required for complex software. For more, see this example in the online playground.
Sandboxing: provides a secure, deterministic environment for execution of templates
Archivy is a self-hosted knowledge repository that allows you to safely preserve useful content that contributes to your knowledge bank.
If you add bookmarks, their webpages contents' will be saved to ensure that you will always have access to it, in sync with the idea of digital preservation.
Allows you to sync up with Pocket to gather bookmarks from there too.
Everything is a file! For ease of access and editing, all the content is stored in markdown files with yaml front matter.
Extensible search with Elasticsearch and its Query DSL
I apologize to @natoscott and @fasterit who tried to contact me; I understand that forking the project must not have been an easy decision to make, and any response of mine might have made it a little easier.
I want to thank you all of you for taking on this initiative, starting from @afontenot for opening up this topic. I am extremely grateful for all the amazing feedback I've received for htop over the years. This has been by far my most successful project, it has brought me many many great things, and I think it's indeed flattering to see it forked
OWNLOAD OPENWRT FIRMWARE
Firmware for Mikrotik
DOWNLOAD TINY PXE SERVER
Link to PXE Server
FLASH THE ROUTER USING THE TOOTHPICK METHOD
Start and configure the PXE Server (192.168.1.10/24, * -initramfs-kernel.bin). Turn off the Mikroitk power, hold down reset, turn on the power and release the toothpick after 20 seconds.
UPGRADE FIRMWARE TO FULL VERSION
After booting the router via PXE, go to the router and update the firmware to the full version (* -squashfs-sysupgrade.bin)
ead this document first, expecially licence key part
first attach your device ethernet to port 5
then power your mikrotik.
open 192.168.88.1 and
System → Routerboard → Settings → Boot device: Try ethernet once then NAND
System → Routerboard → Settings → Boot protocol: DHCP
System → Routerboard → Settings → Force Backup Booter: Checked (if supported by your routerboard - !IMPORTANT)
attach ethernet to port 1
form this url
create a script file, and change interfaces and tftp-root
ifconfig eno1(your interface) 192.168.1.10 up
dnsmasq -i eno1(your interface) --dhcp-range=192.168.1.100,192.168.1.200
--enable-tftp --tftp-root=/where is files/ -d -u dnsmasq -p0 -K --log-dhcp --bootp-dynamic
then run script,(you can download dnsmasq and compile from source for use,also kill all your tftp and dhcp servers. google)
hold reset button
wait about 20 seconds(you can watch progress from script screen,after you see send ***.initramfs.bin unhold reset button)
wait 20 seconds again
detach ethernet from mikrotik
attach ethernet to port 5 again
wait 15 seconds
if your computer ethernet does not have an ipv4
set your computer ethernet
ifconfig eno1 192.168.1.55
if got responses
if you see luci, kernel and ramfs is working.
open upgrade section and select your
RouterBoards can netboot OpenWrt initramfs .elf (.bin in some instances) images via TFTP. This RAM-based initramfs OpenWrt image is first used to validate the desired OpenWrt version operates properly without overwriting any existing image in the NAND or NOR flash of the RouterBoard.
Once you have verified OpenWrt is working on your MikroTik hardware, use the LuCI web interface to permanently flash the appropriate sysupgrade .bin image into the flash of the RouterBoard. In this way, an initial installation is treated exactly the same as a subsequent OpenWrt upgrade. Prior versions of OpenWrt required a subsequent upgrade to once again boot OpenWrt using initramfs: with the current version of OpenWrt that now uses Unsorted Block images (UBI), the initial flash and subsequent upgrades can be performed directly in-place from the LuCI web interface.
After OpenWrt is installed to Flash, depending on the model, some platform configuration may be needed. This is explained in the model specific wiki pages.
First Things First: Don't Lose Your RouterOS License
Before you start installing OpenWrt, save your RouterOS License .key file. This will allow you to use Mikrotik's NetInstall to re-install RouterOS.
Save your license by using Mikrotik WinBox: it's under System→License→Export Key. The Mikrotik WebFig web interface does not export license files, you must use WinBox.
See below for other methods to export your license file.
At least it is supported on the deprecated ar71xx target...
Deprecated means that 19.07 will be the latest stable release for this device as long as anyone port this device to the device tree based ath79 target.
Apparently, 5 GHz wireless hardware in this device is QCA9887, which is driven by ath10k, and it requires non-free firmware, so basically we shouldn't count on 5 GHz even if everything else works. Is my understanding correct?
Probably you only need to install the required driver/firmware packages like:
kmod-ath10k-ct-smallbuffers ath10k-firmware-qca988x-ct ath10k-firmware-qca9887-ct
MikroTik RB952Ui-5ac2nD (hAP ac lite)