[HC Official] T0rn - Hash Cracker V.2

[HC Official] T0rn - Hash Cracker V.2 - Printable Version

+- Sinisterly (https://sinister.li)
+-- Forum: Hacking (https://sinister.li/Forum-Hacking)
+--- Forum: Hacking Tools (https://sinister.li/Forum-Hacking-Tools)
+--- Thread: [HC Official] T0rn - Hash Cracker V.2 (/Thread-HC-Official-T0rn-Hash-Cracker-V-2)

Pages: 1 2 3

RE: [HC Official] T0rn - Hash Cracker V.2 - chmod - 04-08-2014

(04-08-2014, 04:58 PM)Ligeti Wrote:
(04-08-2014, 12:11 PM)chmod Wrote: @Ligeti I'm not a c++ coder so the solution I found was provided by searching, I would think there is more than likely a better way of doing it. It was just a workaround to try and get it to compile.

Thanks my friend... but your solution didn't solve the problem (I tested it)... what distro are you using?

I think I can solve this problem if I put more effort in it, but I wanted to make sure that I am not the only one facing these issues... according to Ex094 I am right (I am not the only one).

@shp0ngl3 did you test the code? (you are using Mint as far as I know)

Thanks

I didn't solve all the issues and have been working towards the rest over the course of today, but no luck with those yet unfortunately.

I'm running fedora

I would think we will all be having the same issues though

EDIT:

Thought I'd post the errors I'm getting now (was the same as Ligeti's before)

Code:
In file included from main.cpp:23:0:
clearscreenl.h: In function ‘void ClearScreen()’:
clearscreenl.h:13:27: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
   putp( tigetstr( "clear" ) );
                           ^
main.cpp: In function ‘void verifyHash(std::string)’:
main.cpp:165:38: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings]
     int count = count_file("pass.txt");
                                      ^
main.cpp: In function ‘void pause()’:
main.cpp:287:12: error: new declaration ‘void pause()’
 void pause() {
            ^
main.cpp:43:5: error: ambiguates old declaration ‘int pause()’
 int pause();
     ^

RE: [HC Official] T0rn - Hash Cracker V.2 - Ex094 - 04-08-2014

@chmod @Ligeti Sorry for this trouble guys, for the time being it seems that it's functional on Windows systems unless I discover what is the problem with all these debug errors in Linux compilation.

RE: [HC Official] T0rn - Hash Cracker V.2 - chmod - 04-08-2014

(04-08-2014, 06:08 PM)Ex094 Wrote: @chmod @Ligeti Sorry for this trouble guys, for the time being it seems that it's functional on Windows systems unless I discover what is the problem with all these debug errors in Linux compilation.

Don't worry about it I'm kinda having fun trying to get it to compile so thank you Biggrin

If I come up with something I'll share it here but it will most likely not be pretty so may need improving by someone who actually knows what they're doing

RE: [HC Official] T0rn - Hash Cracker V.2 - minial90000 - 05-25-2014

Its a very nice tool and thank you for sharing but why did you keep using std:: when you could simply add using namespace std; ? Im not saying you should but I was wondering if there was a reason you did it like you did.

RE: [HC Official] T0rn - Hash Cracker V.2 - Ex094 - 05-25-2014

(05-25-2014, 06:50 PM)minial90000 Wrote: Its a very nice tool and thank you for sharing but why did you keep using std:: when you could simply add using namespace std; ? Im not saying you should but I was wondering if there was a reason you did it like you did.

Using std:: is considered to be a good practice.

1st Reason is that I've never used using namespace std; much so my practice had always involved using std:: so em kinda stuck with it Tongue

2nd Reason, It prevents conflict between 2 libraries, have a look at here http://stackoverflow.com/questions/1452721/why-is-using-namespace-std-considered-bad-practice

Regards Smile

RE: [HC Official] T0rn - Hash Cracker V.2 - minial90000 - 05-26-2014

(05-25-2014, 07:03 PM)Ex094 Wrote:
(05-25-2014, 06:50 PM)minial90000 Wrote: Its a very nice tool and thank you for sharing but why did you keep using std:: when you could simply add using namespace std; ? Im not saying you should but I was wondering if there was a reason you did it like you did.

Using std:: is considered to be a good practice.

1st Reason is that I've never used using namespace std; much so my practice had always involved using std:: so em kinda stuck with it

2nd Reason, It prevents conflict between 2 libraries, have a look at here http://stackoverflow.com/questions/1452721/why-is-using-namespace-std-considered-bad-practice

Regards

Thank you this was helpful!