Hiddeneye-legacy: Unexpected close after the first credentials capture

Created on 14 Jul 2019  路  9Comments  路  Source: DarkSecDevelopers/HiddenEye-Legacy

This error occurs after having first captured the user's credentials.

[*] Waiting For Victim Interaction. Keep Eyes On Requests Coming From Victim ...

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

..................................................................
..................................................................
Traceback (most recent call last):
File "./HiddenEye.py", line 38, in
getCredentials()
File "/root/Escritorio/HiddenEye/Defs/Actions.py", line 572, in getCredentials
log('..................................................................'.format(MAIN0, MAIN4))
NameError: name 'log' is not defined

Someone will know why this error occurs. (The script has root user permissions)

NOTE: Note that this error occurs in Localhost URL.

Most helpful comment

Sometimes it's working and sometimes it isn't......I can't understand why........
.
.
.
........................................................
Traceback (most recent call last):
File "./HiddenEye.py", line 38, in
getCredentials()
File "/root/Escritorio/HiddenEye/Defs/Actions.py", line 558, in getCredentials
.
Etc....,
.

All 9 comments

Check these closed issue #204 #207 ...
If these do not resolve your problem.
Then try to update & relaunch script.
Use command
git pull
to merge latest commits.

Let me know if it helps or not.

Sometimes it's working and sometimes it isn't......I can't understand why........
.
.
.
........................................................
Traceback (most recent call last):
File "./HiddenEye.py", line 38, in
getCredentials()
File "/root/Escritorio/HiddenEye/Defs/Actions.py", line 558, in getCredentials
.
Etc....,
.

@Mageshwar01 do chmod 777 HiddenEye to the whole directory

@usama7628674 I did that when I installed HiddenEye...... should I do that once again?

Fixed in #401

That was our mistake guys, wait until it's merged and you'll be fine and ready!

Why custok domain in serveo is not working??

@Hunter310 how you may reproduce the error?

Tested and already been fixed.

Red first request
Blue second request

image

Was this page helpful?
0 / 5 - 0 ratings