{"action":"created","issue":{"url":"https://api.github.com/repos/magnumripper/JohnTheRipper/issues/1638","labels_url":"https://api.github.com/repos/magnumripper/JohnTheRipper/issues/1638/labels{/name}","comments_url":"https://api.github.com/repos/magnumripper/JohnTheRipper/issues/1638/comments","events_url":"https://api.github.com/repos/magnumripper/JohnTheRipper/issues/1638/events","html_url":"https://github.com/magnumripper/JohnTheRipper/issues/1638","id":100099706,"number":1638,"title":"Add a new --max-blocks(?) option","user":{"login":"frank-dittrich","id":2026819,"avatar_url":"https://avatars.githubusercontent.com/u/2026819?v=3","gravatar_id":"","url":"https://api.github.com/users/frank-dittrich","html_url":"https://github.com/frank-dittrich","followers_url":"https://api.github.com/users/frank-dittrich/followers","following_url":"https://api.github.com/users/frank-dittrich/following{/other_user}","gists_url":"https://api.github.com/users/frank-dittrich/gists{/gist_id}","starred_url":"https://api.github.com/users/frank-dittrich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/frank-dittrich/subscriptions","organizations_url":"https://api.github.com/users/frank-dittrich/orgs","repos_url":"https://api.github.com/users/frank-dittrich/repos","events_url":"https://api.github.com/users/frank-dittrich/events{/privacy}","received_events_url":"https://api.github.com/users/frank-dittrich/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/magnumripper/JohnTheRipper/labels/enhancement","name":"enhancement","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-08-10T15:51:19Z","updated_at":"2015-08-11T14:14:15Z","closed_at":null,"body":"I think it is a good thing to have for GPU formats where a single call to crypt_all takes very long, and you want to make sure you interrupt the session when you don't loose much work.\r\nFor CPU formats, --max-run-time will be OK in most cases, but for OpenCL formats which process a huge number of candidates per crypt_all() call, you risk wasting much time if you interrupt at the wrong time.\r\nWith that option, you could try several attacks, and then (in a loop) restore the most successful sessions..."},"comment":{"url":"https://api.github.com/repos/magnumripper/JohnTheRipper/issues/comments/129897306","html_url":"https://github.com/magnumripper/JohnTheRipper/issues/1638#issuecomment-129897306","issue_url":"https://api.github.com/repos/magnumripper/JohnTheRipper/issues/1638","id":129897306,"user":{"login":"frank-dittrich","id":2026819,"avatar_url":"https://avatars.githubusercontent.com/u/2026819?v=3","gravatar_id":"","url":"https://api.github.com/users/frank-dittrich","html_url":"https://github.com/frank-dittrich","followers_url":"https://api.github.com/users/frank-dittrich/followers","following_url":"https://api.github.com/users/frank-dittrich/following{/other_user}","gists_url":"https://api.github.com/users/frank-dittrich/gists{/gist_id}","starred_url":"https://api.github.com/users/frank-dittrich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/frank-dittrich/subscriptions","organizations_url":"https://api.github.com/users/frank-dittrich/orgs","repos_url":"https://api.github.com/users/frank-dittrich/repos","events_url":"https://api.github.com/users/frank-dittrich/events{/privacy}","received_events_url":"https://api.github.com/users/frank-dittrich/received_events","type":"User","site_admin":false},"created_at":"2015-08-11T14:14:15Z","updated_at":"2015-08-11T14:14:15Z","body":"I guess that for a hybrid --mask session, not all duplicate effort can be avoided, because the .rec file only records progress of the main cracking mode, is that right?\r\n"}}