Vice City Multiplayer
VC:MP 0.3 => mIRC/pawn Scripting => ShowRoom (pawn) => Topic started by: NE.Restricted on September 14, 2013, 12:21:22 pm
-
GUPS 1.17 Fixed version
FIXED:
!getcar,
!deposit,
!withdraw,
!givecash
IMPORTANT: You MUST use the pawno from the script or at least copy /pawno/include/ntsys.inc to /yourpawnodirectory/include/ to modify/edit the script. If you dont you will get this:
Fatal error (xx): Can not read from file ntsys.
I told you about an extra script in the title, right? Well, its a roleplay script. To use it, open pawno, look at the top and change new ROLEPLAY_MODE = 0; to new ROLEPLAY_MODE = 1;
(http://www.clker.com/cliparts/q/q/H/6/2/J/download-button.svg) (http://www.solidfiles.com/d/0c90b6d998/)
~Note: This script is untested~
~Note: The credit is not stolen, thus the credits to gups scripters is still there~
-
GUPS 1.17 Fixed version
FIXED:
!getcar,
!deposit,
!withdraw,
!givecash
IMPORTANT: You MUST use the pawno from the script or at least copy /pawno/include/ntsys.inc to /yourpawnodirectory/include/ to modify/edit the script. If you dont you will get this:
Fatal error (xx): Can not read from file ntsys.
I told you about an extra script in the title, right? Well, its a roleplay script. To use it, open pawno, look at the top and change new ROLEPLAY_MODE = 0; to new ROLEPLAY_MODE = 1;
(http://www.clker.com/cliparts/q/q/H/6/2/J/download-button.svg) (http://www.solidfiles.com/d/0c90b6d998/)
~Note: This script is untested~
~Note: The credit is not stolen, thus the credits to gups scripters is still there~
First... you only change the name of the inc of madara and added some things of madara... nothing else..
I know the inc of madara, you only change the name and you "roleplay mode 1" pff :P :P :o :o :o
-
GUPS 1.17 Fixed version
FIXED:
!getcar,
!deposit,
!withdraw,
!givecash
IMPORTANT: You MUST use the pawno from the script or at least copy /pawno/include/ntsys.inc to /yourpawnodirectory/include/ to modify/edit the script. If you dont you will get this:
Fatal error (xx): Can not read from file ntsys.
I told you about an extra script in the title, right? Well, its a roleplay script. To use it, open pawno, look at the top and change new ROLEPLAY_MODE = 0; to new ROLEPLAY_MODE = 1;
(http://www.clker.com/cliparts/q/q/H/6/2/J/download-button.svg) (http://www.solidfiles.com/d/0c90b6d998/)
~Note: This script is untested~
~Note: The credit is not stolen, thus the credits to gups scripters is still there~
First... you only change the name of the inc of madara and added some things of madara... nothing else..
I know the inc of madara, you only change the name and you "roleplay mode 1" pff :P :P :o :o :o
I found out that i should give the madara credit too late. It was after I posted it. Anyways, I am not a thief and I don't steal credits.
And now I have a better ntencrypt(i just didnt posted it yet) you just change stock ntencrypt(val[]) return hash(val); to stock ntencrypt(val[]) return hash(hash(hash(val)));
OFFTOPIC: You dont have to always reply with quotes
-
why hash 3 times? That's stupid, you will have a bigger rate of collisions when typing passwords, so you could be able to login with fsdghas when the password is bananas.
Use only one hash or none at all.
-
why hash 3 times? That's stupid, you will have a bigger rate of collisions when typing passwords, so you could be able to login with fsdghas when the password is bananas.
Use only one hash or none at all.
A different hash is not used on login.
-
you lack some brain cells, but that's fine.
THE thing is, hashing it 3 times is not safe as it can produce collisions
hashing a hash is as stupid as it sounds.
-
you lack some brain cells, but that's fine.
THE thing is, hashing it 3 times is not safe as it can produce collisions
hashing a hash is as stupid as it sounds.
return from ntencrypt("bananas"): 153616851
return from ntencrypt("fsdghas"): 155976153
You failed
-
you lack some brain cells, but that's fine.
THE thing is, hashing it 3 times is not safe as it can produce collisions
hashing a hash is as stupid as it sounds.
return from ntencrypt("bananas"): 153616851
return from ntencrypt("fsdghas"): 155976153
You failed
What heekzs presented was a theoretical example of what is known as a hash collision. Please read at least the first few paragraphs of this Wikipedia article, because what you posted is ignorant of it:
http://en.wikipedia.org/wiki/Collision_(computer_science)
That being said, using multiple iterations of a hashing method is not insecure in and of itself, and makes it more difficult to compute hashes since each hash iteration takes longer to calculate. The tradeoff is that this also slows down your server, which would not be necessary if your hashes were salted (http://en.wikipedia.org/wiki/Salt_(cryptography)) properly.
The only time collisions would become a concern, which is highly unlikely due to the extreme unlikelihood of a collision ever occurring, is that if, by chance, one of the hashes in your sequence has a collision, then all of the hashes generated from that hash will also collide.
See also:
Key stretching (http://en.wikipedia.org/wiki/Key_stretching)
-
you lack some brain cells, but that's fine.
THE thing is, hashing it 3 times is not safe as it can produce collisions
hashing a hash is as stupid as it sounds.
return from ntencrypt("bananas"): 153616851
return from ntencrypt("fsdghas"): 155976153
You failed
What heekzs presented was a theoretical example of what is known as a hash collision. Please read at least the first few paragraphs of this Wikipedia article, because what you posted is ignorant of it:
http://en.wikipedia.org/wiki/Collision_(computer_science)
That being said, using multiple iterations of a hashing method is not insecure in and of itself, and makes it more difficult to compute hashes since each hash iteration takes longer to calculate. The tradeoff is that this also slows down your server, which would not be necessary if your hashes were salted (http://en.wikipedia.org/wiki/Salt_(cryptography)) properly.
The only time collisions would become a concern, which is highly unlikely due to the extreme unlikelihood of a collision ever occurring, is that if, by chance, one of the hashes in your sequence has a collision, then all of the hashes generated from that hash will also collide.
See also:
Key stretching (http://en.wikipedia.org/wiki/Key_stretching)
I have read it but I dont understand that how do these 2 have the same hash value.
If it makes lag, I could use a timer, variable and a loop.
-
I have read it but I dont understand that how do these 2 have the same hash value.
If it makes lag, I could use a timer, variable and a loop.
Timers and loops are not a solution for lag as now your scripts will lag when the timer runs. The real solution would be to fix what makes it lag.
As for hash collisions, again, it was a theoretical example. Those two values will not actually produce the same hash. It's just an example of how two values can produce the same values. Hash algorithms ALWAYS have a small chance of two values having the same output, but it's miniscule; too small to worry about on an everyday basis, really.