Positronikal.github.io
The home page of Positronikal projekts
Project maintained by Positronikal Hosted on GitHub Pages — Theme by mattgraham
Welcome to Positronikal on GitHub!
My real name is Hoyt Harness, but Positronikal is the moniker I've used for several years for my digital projects. The majority of projects I intend to park here pertain to digital forensics and cyber investigation. That said, there will likely also be projects that don't directly pertain to these subject matter areas. I'll continue to host public forks of other projects from my personal account at https://github.com/hoyt-harness.
Projects:
I forked the libyal/libewf-legacy repo, made all the necessary adjustments for a Windows AMD64 build using the included PowerShell scripts, upgraded the prerequisite files for Visual Studio 2022, built the supporting libraries and ewf-tools, then pushed the whole thing here. The README explains where the binaries are located and the original documentation details how to configure everything to build it yourself if you don't want to use the pre-builts. Otherwise, you can clone it or download the ZIP, add the appropriate path to your envars, and run the tools from any directory.
This repository has been deprecated as of December 31, 2020 and exists as a placeholder only. All Carnivore code released prior to this date pertaining specifically to CarnivoreLE or any other part of the larger project will continue to be licensed under GPLv3. No new changes or pull requests will be accepted.
This is just as the name implies - a simple backup utility for Debian-based distros. It's written in bash and makes use of rsync and dialog. rsync is a fast, versatile, remote (and local) file copying tool. dialog displays dialog boxes from shell scripts. There is plenty of room to expand this project, add new dialog boxes, and make much more of rsync's capabilities. See the section below titled Contributing.
This project was formerly known as "montereyMacports". That project has been deprecated due to being specific to macOS Monterey. macportsAssistant is macOS version agnostic and it should work for earlier versions of macOS to some extent and will be easier to maintain support for new versions as they are released. It has only been tested on macOS Ventura however, so bear this in mind regarding your testing on any previous macOS version. macportsAssistant automates macPorts installation or upgrade if an earlier version exists. Both the installation and upgrade utilities must be ran as root and will create a ~/bin/MacPorts directory to work from. In addition, they install a third utility in ~/bin to automate MacPorts updating (macports_updater.sh) which must also be ran as root. The install/upgrade utilities add ~/bin to your path envar, so the updater can simply be called from a terminal. Both the install/upgrade utilities can be further improved by combining them into a single script that determines at runtime if MacPorts is (1) installed and already the current version, (2) is installed, but not the current version, or (3) is not installed, then calling the appropriate functionality from there. Contributors/testers may find other areas of improvement. See the section below titled Contributing.
Contributing:
If you're new and not sure where to begin, GitHub's Help pages are a good place to start. There are also quick start and setup information pages located in Bootcamp and Setup.
All commits in pull requests must be GPG signed. I know, I know... Positronikal is nobody. You're right, but better to start off the right way than to try and backtrack something months or years down the road. It's not as much of a pain as it sounds like and you know this if you're doing it already. If not, see the page on signing commits. Use of a keyserver is highly recommended, as is having your public key signed by others who can vouch for you. Instructions on this are here. My public key (Hoyt Harness) can be retrieved from MIT's keyserver here.
All contributors must have a signed Developer Certificate of Origin on file with Positronikal before any code is accepted or reviewed. This is related to the above paragraph and for the same reasons. If the code you submitted was written as a result of your job or you coded a significant portion during work hours or if any other circumstances exist that might give rise to your employer exercising a right to ownership at any time in the future, a DCO must be on file for them as well and signed by a competent authority within the organization (not yourself). Posi_DCO.md is available in this repository. Click the "View On GitHub" button at the top of the page to find it or click here.
Positronikal coding tends to follow GNU coding standards. Software development tends to follow the UNIX philosphy. Information contained at both of those links are invaluable to new coders and should still contain worthy nuggets of wisdom for even the most experienced. In any case, all disputes regarding form or function will ultimately be resolved based on one of those references.
This work is licensed under a Creative Commons Attribution 4.0 International License.