Epiphany Toolset

Total Queue Size: 36,374
Total Reversed: 24,254
Total Retired: 120,648

Epiphany Process Monitor
Notice Process monitor information is not real-time, it is updated daily at midnight (UTC-08:00) Pacific Time (US & Canada).

Process Start Timestamp: 2010-07-25 00:05:29

Current Process Progress: 85.68% - Running...


Hashes Being Processed: 22,647 of 36,374
Hashes Reversed Since Current Process Start: -5

Cluster Node Health Monitor
Notice Health monitor information is not real-time, it is updated hourly.

Cluster-00: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Cluster-01: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Cluster-02: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Cluster-03: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Cluster-04: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Cluster-05: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Cluster-06: Xeon @ 2.8GHz (Quad-Core) Online
CPU Utilization: 
 100%

Epiphany FAQ
What is Epiphany? Epiphany is a toolset that captures the "Not Found" (nearly 85%) results, and queues them into a database. Every Sunday at 12:05AM, the hashes are exported from the queue database and stored on a 7 node cluster. Seconds later an OpenMPI job is started, launching a distributed (MPI) version of "John the Ripper" (JtR). JtR then begins reversing hashes utilizing the cumulative CPU speed of all 7 nodes. This job runs for 7 days and is then terminated. The successfully reversed hashes are then exported from the cluster and imported back into the database with their clear text. Hashes that have been in the queue for 20 days or longer are set to "Retired" and are not included in the next OpenMPI job. The process then starts from the beginning with a new set of "Not Found" results that were queued during the 7 days JtR was running.
What algorithms are supported by Epiphany? At this time Epiphany only queues MD5 "Not Found" results. I hope to add the ability to include SHA-1, LM, and NTLM "Not Found" results in the queue in the future. This feature must be well thought out and coded with care. It will not be something that happens in the short term.
Show Project History Hide Project History | Page Created: Jan. 3rd, 2010; Page Last Edited: Mar. 11th, 2010
  • ∞ / Concept and Design Review (Private), Dec. 11th, 2009 - Dec. 13th, 2009
  • ∞ / Proof of Concept Release (Private), Dec. 15th, 2009 - Jan. 2nd, 2010
    • 2 cluster nodes
    • 24 hour process length
  • α / Alpha Release (Public), Jan. 3rd, 2010 - Feb. 9th, 2010
    • 4 cluster nodes
    • 7 day process length
    • Node health monitor
    • Process monitor
  • β / Beta Release (Public), Feb. 10th, 2010 - Mar. 3rd, 2010
    • 5 cluster nodes
    • Hashes are retired from queue after 20 days
  • β / Beta Release (Public), Mar. 3rd, 2010 - Mar. 11th, 2010
    • 6 cluster nodes
  • β / Beta Release (Public), Mar. 11th, 2010 - Present
    • 7 cluster nodes