« on: September 09, 2018, 01:13 PM »
I humbly propose my TrID tool.
Your example could be a GUI interface for it.
Your example could be a GUI interface for it.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
The purpose of BlockHashLoc is to enable the recovery of files after total loss of File System structure, or without even knowing what FS was used in the first place.
The way it can recover a given file is by keeping a (small) parallel BHL file with a list of crypto-hashes of all the blocks (of selectable size) that compose it. So it's then possible to read blocks from a disk image/volume, calculate their hashes, compare them with the saved ones and rebuild the original file.
With adequately sized blocks (512 bytes, 4KB, etc. depending on the media and File System), this let one recover a file regardless of the FS used, or the FS integrity, or the fragmentation level.
This project is related to SeqBox. The main differences are:
- SeqBox create a stand-alone file container with the above listed recovery characteristics.
- BHL realize the same effect with a (small) parallel file, that can be stored separately (in other media, or in the cloud), or along the original as a SeqBox file (so that it can be recovered too, as the first step), so it can be used to add a degree of recoverability to existing files.
@Mark0: Thanks. The version 3 is necessary only because that is the version my daughter is being taught with at school.-IainB (April 06, 2017, 05:25 PM)
but this really does sound like something everyone SHOULD be using-solaris65 (April 05, 2017, 06:51 AM)
Seqbox recoverability have been practically tested with a number of File Systems. The procedure involved using a Virtual Machine to format a small (about 100MB) disk image with a certain FS, filling it with a number of small files, then deleting some randomly to free enough space to copy a serie of SBX files. This way every SBX file results fragmented in a lot of smaller pieces. Then the image was quick-formatted, wipefs-ed and the VM shutdown.
After that, from the host OS, recovery of the SBX files was attempted using SBXScan & SBXReco on the disk image.
- Working: BeFS, BTRFS, EXT2/3/4, FATnn/VFAT/exFAT, AFFS, HFS+, JFS, MINIX FS, NTFS, ProDOS, ReiserFS, XFS, ZFS.
- Not working: OFS (due to 488 bytes blocks)
Being written in Python 3, SeqBox tools are naturally multi-platform and have been tested successfully on various versions of Windows, on some Linux distros either on x86 or ARM, and on Android (via QPython). No test was done on OS X but it should works there as well (feedback welcome).
Pretty nightmarish! Now on to SBXScan to search for pieces of SBX files around, and SBXReco to get a report of the collected data:
A SeqBox container have a blocksize sub/equal to that of a sector, so can survive any level of fragmentation. Each block have a minimal header that include a unique file identifier, block sequence number, checksum, version. Additional, non critical info/metadata are contained in block 0 (like name, file size, crypto-hash, other attributes, etc.).
If disaster strikes, recovery can be performed simply scanning a volume/image, reading sector sized slices and checking blocks signatures and then CRCs to detect valid SBX blocks. Then the blocks can be grouped by UIDs, sorted by sequence number and reassembled to form the original SeqBox containers.
Set up a 21 profile to receive paid messages from people outside your network. Keep the money, or donate it to charities like Black Girls Code.21.co
It's like LinkedIn InMail, except you get paid!
It's bigger than your address book
At Keybase we collectively use and love WhatsApp, Signal, Slack, and iMessage, to name a few. However, in all those apps: recipients are looked up by phone number or email.
That works ok with friends and coworkers.
But it sucks with people you know on the Internet. First off, they have to give you their phone number in a preliminary back and forth. That takes time and prevents you from sending your message until you hear back.
Then, to make sure you're really secure, you're supposed to compare special codes by meeting in person. That's impossible in most cases.
Keybase is different. For example, in Keybase chat, I can simply use my Hacker News name, malgorithms, as my secure address; no phone number or email needed. My Twitter username would work, too. Or even my Reddit username.
At GDC 2016, Provinciano elaborated on exactly how he did it, and in the process shed light on how he reduced memory usage down to 4MB, increased performance to run on a 486 PC, reduced disk space to fit on a single 1.44MB floppy, and finally ported the game to MS-DOS itself.
Why I’m writing a Windows 3 Emulator
I’ve decided to write a 16-bit Windows emulator. It’s a bit of crazy idea, but hear me out…
- It’s like DosBox in that it’s emulating the CPU — but unlike DosBox in that it’s not emulating other low level hardware.
- It’s like Wine in that it’s emulating the Windows API — but unlike Wine in that the CPU is emulated instead of running on a physical processor (remember Wine stands for “Wine Is Not an Emulator”).
- It’s not like VirtualBox or VMWare or other virtualization software as it’s not emulating or virtualizing low level hardware.