I tried to reproduce the error and found out that with the new package
of john the issue doesn't occur anymore. Because of this I marked this
bug as invalid.
** Changed in: john (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Sorry, I meant fix released
** Changed in: john (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such
why Ubuntu version are you using ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about this bug go
sorry...
WHICH Ubuntu version are yoou using
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about th
running
$ touch john
worked for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about this bug g
Even if I manually create ~/john.ini (ln -s /etc/john/john.conf
john.ini) john won't work as usual.
This occurs because var $JOHN is not defined. (echo $JOHN) should be
"/usr/share/john/", and it's used in john.conf (cat /etc/john/john.conf
| grep \$JOHN)
--
You received this bug notification be
** Changed in: john (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage n
After doing what Henry Barker (orionsbelt152) suggested, worked for me
in Saucy!
In home directory, execute:
ln -s /etc/john/john.conf john.ini
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I got this in saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about this bug go to:
https://bu
What worked for me in 13.04 is, in my home directory:
ln -s /etc/john/john.conf john.ini
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or
** Tags added: broken bug install-package john
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about
I don't use Ubuntu. I maintain the package in Debian.AFAIK the package is
still working in Debian. A couple of months ago I prepared a package for
v1.8.0 just in case someone want to try it and check if this solves the
problem in Ubuntu.
And here is it: http://mentors.debian.net/package/john
Ruben
Any chance this might get fixed sometime this century? Like nmap, this
tool is a required part of any security professional's toolbox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
j
Still present in 13.04 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about this bug go to:
https:
You can add the following line to ~/.bashrc
JOHN=/etc/john
or if you prefer your own configuration file,
JOHN=~/.john
then make sure to `mkdir ~/.john` and then `cp /etc/john/john.conf $JOHN`
This is a little ridiculous, its been almost 7 months since this was reported?
--
You received this bug n
Using Ubuntu 13.04. Although not a solution, creating a john.ini file in
whichever folder I want to run JTR from, seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john ou
I would also add that using 10.04 LTS is not a workaround either,
because the John version included in it does not know its passwd hash
format.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Ti
Neither workaround worked for me.
The one recommended by Francesco Muriana results in: No "single crack" mode
rules found in john.ini
Pali: open: john.log: Permission denied
Pali - with sudo: fopen: password.lst: No such file or directory
--
You received this bug notification because you are a
None of the above solutions worked for me in 12.10
Ths works, but it is not a solution:
$ cd /etc/john
$ john
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.
Try: "cd /etc/john"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notifications about this bug go to:
https://bug
The same on Linux Mint 14 (based on Ubuntu 12.10). I tried to solve with
these commands:
"cd /usr/share/john
sudo touch john.ini"
and it seems to work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10
same here with the 12.10x64 install after install john
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notification
same here with a new 12.10 install after apt-get install john
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
To manage notif
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: john (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john
Could it be a possible problem setting the PATH for the process
environment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071718
Title:
john outputs " fopen: john.ini: No such file or directory"
25 matches
Mail list logo
