** Information type changed from Private Security to Public

** Description changed:

- When nasty -f OUT 0-62 is resumed (with simple "nasty" command without
+ (nasty package 0.6-2)
+ 
+ When nasty -f OUT is resumed (with simple "nasty" command without
  parameters, the original being gathered from nasty.state) after Ctrl+C,
  it won't respect the -f directive:
  
  ~$ nasty -a 1 -b 8 -m incremental -f OUT -c .
  nasty v0.6, (C) 2005 by [email protected]
  
  # tried: 186 (62.000000 per second), last tried: n%
  # tried: 456 (76.000000 per second), last tried: t2
  ^C
  State saved to 'nasty.state'
  ~$ nasty
  nasty v0.6, (C) 2005 by [email protected]
  
  Using state from previous run
  # tried: 878 (292.666667 per second), last tried: E9
  # tried: 17441 (95.306011 per second), last tried: Bz&
  Passphrase is: C00
  
  ~$ cat OUT
  cat: OUT: No such file or folder

** Description changed:

  (nasty package 0.6-2)
  
  When nasty -f OUT is resumed (with simple "nasty" command without
  parameters, the original being gathered from nasty.state) after Ctrl+C,
  it won't respect the -f directive:
  
  ~$ nasty -a 1 -b 8 -m incremental -f OUT -c .
  nasty v0.6, (C) 2005 by [email protected]
  
  # tried: 186 (62.000000 per second), last tried: n%
  # tried: 456 (76.000000 per second), last tried: t2
  ^C
  State saved to 'nasty.state'
  ~$ nasty
  nasty v0.6, (C) 2005 by [email protected]
  
  Using state from previous run
  # tried: 878 (292.666667 per second), last tried: E9
  # tried: 17441 (95.306011 per second), last tried: Bz&
  Passphrase is: C00
  
  ~$ cat OUT
  cat: OUT: No such file or folder
+ 
+ nasty.state confirms, no outfile path/name:
+ cat nasty.state
+ # Do not edit this file (unless you're really sure what you're doing)!
+ 
+ mode=2
+ cur=3F02
+ charset=0020212223...
+ min_length=10
+ max_length=11
+ n_done=253

** Description changed:

  (nasty package 0.6-2)
  
  When nasty -f OUT is resumed (with simple "nasty" command without
  parameters, the original being gathered from nasty.state) after Ctrl+C,
  it won't respect the -f directive:
  
- ~$ nasty -a 1 -b 8 -m incremental -f OUT -c .
+ ~$ nasty -a 1 -b 8 -m incremental -f OUT
  nasty v0.6, (C) 2005 by [email protected]
  
- # tried: 186 (62.000000 per second), last tried: n%
- # tried: 456 (76.000000 per second), last tried: t2
+ # tried: 186 (62.000000 per second), last tried: ...
+ # tried: 456 (76.000000 per second), last tried: ...
  ^C
  State saved to 'nasty.state'
  ~$ nasty
  nasty v0.6, (C) 2005 by [email protected]
  
  Using state from previous run
- # tried: 878 (292.666667 per second), last tried: E9
- # tried: 17441 (95.306011 per second), last tried: Bz&
+ # tried: 878 (292.666667 per second), last tried: ...
+ # tried: 17441 (95.306011 per second), last tried: ...
  Passphrase is: C00
  
  ~$ cat OUT
  cat: OUT: No such file or folder
  
  nasty.state confirms, no outfile path/name:
  cat nasty.state
  # Do not edit this file (unless you're really sure what you're doing)!
  
  mode=2
  cur=3F02
  charset=0020212223...
  min_length=10
  max_length=11
  n_done=253

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301162

Title:
  nasty won't respect -f outfile on resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nasty/+bug/1301162/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to