v0.5.2

Changes from v0.4

Features

• Username support in hashlists
• UI to append hashes to existing hashlists
• Agents use a lockfile, allowing multiple machines to use network storage
• Simplified Listfiles UI and improved API listfiles endpoints
• Admins can edit existing users
• General UI improvements

WIP Features (not exposed in UI yet):

• Agent Registration Keys
• Aibility to associated uploaded listfiles to a project

Fix

• Unrecognized cracked hashes are automatically appended to the hashlist
• General UI fixups, reduced styling inconsistencies
• Searching inside a hashlist is now correctly case insensitive
• Removed excessive server database logging from GORM
• The list of target_hashes is no longer unnecessarily returned in API responses for job details, drastically improving UI performance on large (50k+) hashlists

v0.5.1

Release

v0.5.0

Release

v0.4.0

Release

v0.3.0

Breaking Change

This version contains several fixes to the db schema.

Immediately before upgrading to this release, run the following (docker exec -it -u postgres phatcrack-db-1 psql -U phatcrack):

# Remove the project_share constraint
# Gorm will re-create it with the appropriate ondelete
alter table project_shares drop constraint fk_projects_project_share;

# Remove the unique index used by the last potfile
# If this failed to create on the most recent version for you, this will likely error, but thats fine
drop index idx_uniq;

If migrating to 0.2.x failed (i.e. idx_uniq couldn't be made), you will likely need to de-duplicate your potfile table again:

BEGIN;

-- Create temporary table with unique rows
CREATE TEMP TABLE unique_temp_potfile AS
SELECT DISTINCT ON (hash, plaintext_hex, hash_type) *
FROM potfile_entries
ORDER BY hash, plaintext_hex, hash_type, id;

-- Delete original rows
DELETE FROM potfile_entries;

-- Copy the rows back
INSERT INTO potfile_entries SELECT * FROM unique_temp_potfile;

DROP TABLE unique_temp_potfile;

COMMIT;

Fixes

DB Schema Fixes:

• the project_share table foreign key constraint did not properly cascade project deletions. This caused project deletions to fail (#37)
• the potfile_entries unique index would not build correctly (or instead prevent certain insertions) due to postgres limitations in key length (#35)

Other fixes:

• #37 was also addressed by fixing a typo in a query (83c8b64)

v0.2.1

Breaking Change

This version contains a bug fix where duplicate Potfile entries were created. This bug fix adds new database constraints, this will fail if you don't de-duplicate the database first.

Before upgrading to this version, you must run the following query (docker exec -it -u postgres phatcrack-db-1 psql -U phatcrack):

BEGIN;

-- Create temporary table with unique rows
CREATE TEMP TABLE unique_temp_potfile AS
SELECT DISTINCT ON (hash, plaintext_hex, hash_type) *
FROM potfile_entries
ORDER BY hash, plaintext_hex, hash_type, id;

-- Delete original rows
DELETE FROM potfile_entries;

-- Copy the rows back
INSERT INTO potfile_entries SELECT * FROM unique_temp_potfile;

DROP TABLE unique_temp_potfile;

COMMIT;

Please strongly consider making a database backup before running this query.

v0.2.0

Breaking Change

This version contains a bug fix where duplicate Potfile entries were created. This bug fix adds new database constraints, this will fail if you don't de-duplicate the database first.

Before upgrading to this version, you must run the following query (docker exec -it -u postgres phatcrack-db-1 psql -U phatcrack):

BEGIN;

-- Create temporary table with unique rows
CREATE TEMP TABLE unique_temp_potfile AS
SELECT DISTINCT ON (hash, plaintext_hex, hash_type) *
FROM potfile_entries
ORDER BY hash, plaintext_hex, hash_type, id;

-- Delete original rows
DELETE FROM potfile_entries;

-- Copy the rows back
INSERT INTO potfile_entries SELECT * FROM unique_temp_potfile;

DROP TABLE unique_temp_potfile;

COMMIT;

Please strongly consider making a database backup before running this query.

v0.1.6

Fixes:

• Only show hashrate of jobs that are running in sum, per #34
• Gracefully handle ErrProcessDone, per #33
• Users that are MFA exempt will no-longer be prompted to enroll MFA

v0.1.5

New features:

• Administrators can elect to randomly generate passwords when creating user accounts.
• Improved UI for jobs that are in the process of distributing

v0.1.4

Release