-
Notifications
You must be signed in to change notification settings - Fork 220
Release steps
Romke van Dijk edited this page Apr 4, 2024
·
13 revisions
- update hash modes of hashcat (see below)
- adjust version number of agent (initialize.py, README.md, changelog.md)
- adjust agent release notes (changelog.md)
- release agent
- do agent ./build.sh and copy over to server into src/bin/
- update agent version in hashtopolis.sql and update script
- insert newest hashcat version (hashtopolis.sql)
- adjust update scripts (rename)
- adjust server release notes (changelog.md)
- rebuild doc pdfs,
pdflatex protocol.tex
andpdflatex user-api.tex
(if needed) - update src/inc/info.php to new version number
- Is dev in sync with the new master?
- release server
- Update version of web-ui in src/config/default/app/main.ts
- release web-ui
- docker release, see below
- communicate release
- add release commit to ci/HashtopolisTest.class.php
- clean up built entries on archive with wrong version numbers
- update the HEAD files of agent and server under the stable update track
export version=v0.14.1
docker pull hashtopolis/backend:$version
docker tag hashtopolis/backend:$version hashtopolis/backend:latest
docker push hashtopolis/backend:latest
docker pull hashtopolis/frontend:$version
docker tag hashtopolis/frontend:$version hashtopolis/frontend:latest
docker push hashtopolis/frontend:latest
Take the sql entries and put into dbmodes
. Take the hashcat wiki output and put it into hcmodes
.
cat dbmodes | grep -Eo '\([0-9]+,' | tr -d '(,' > dbmodes.num
cat hcmodes | cut -d'|' -f 1 | tr -d ' ' | sort -n > hcmodes.num
comm -32 hcmodes.num dbmodes.num | tee diff