-
Member
The issue is that it will sometimes create duplicate accounts with the same username, and it somehow works. I already have 2 "Acc16" 's in my accounts.txt files with 2 completely different passwords.
-
Corporal
Originally Posted by
V1ceC1ty
The issue is that it will sometimes create duplicate accounts with the same username, and it somehow works. I already have 2 "Acc16" 's in my accounts.txt files with 2 completely different passwords.
That's because there's no duplication check, it'll "think" it's created the same account twice, but only the first would actually work, I'm surprised it even gets so far in the sign up process with an invalid username.
Like I said, I'll work on adding a counting variable to a set username, see if I can call it upon each loop to the end of the username.
-
Post Thanks / Like - 1 Thanks
V1ceC1ty (1 members gave Thanks to JakeP for this useful post)
-
Member
know its been mentioned before - would be great if you could customize user/pass in UI
-
Member
Realized I needed to install the requires.. still spitting out a bunch of unknown keys. Will update when the iteration is done.
Last edited by billnyescifi; 08-01-2016 at 09:27 AM.
Reason: realized why i got errors
-
anyone got a compiled version that doesnt spit out random names?
-
Member
Originally Posted by
spodakek
All the accounts are automatically verified.
Yes thats true, it was a bug from NecroBot
With newest Update Necrobot its works with Created Accounts with the Tool here
-
Corporal
So far, I've added user input to the script to specify a starting username which adds an integer converted to a string onto the end of the input username, e.g. specified user is Jake, program generates Jake0 on first account, Jake1 on second account, Jake2 on third, etc.
The main issue I'm having now is with the actual sign up process, it hangs when I give the username a concatenated variable.
Once I figure out where and why it hangs, I'll see if I can get permission from JD to add this feature to his script.
EDIT
Added user input for the password too.
-
Post Thanks / Like - 1 Thanks
V1ceC1ty (1 members gave Thanks to JakeP for this useful post)
-
Member
Originally Posted by
JakeP
So far, I've added user input to the script to specify a starting username which adds an integer converted to a string onto the end of the input username, e.g. specified user is Jake, program generates Jake0 on first account, Jake1 on second account, Jake2 on third, etc.
The main issue I'm having now is with the actual sign up process, it hangs when I give the username a concatenated variable.
Once I figure out where and why it hangs, I'll see if I can get permission from JD to add this feature to his script.
EDIT
Added user input for the password too.
I would appreciate that
-
Member
All these accounts using same email service will stick out like a sore thumb. If they later require re-verification theres no way.
-
Corporal
Well, unless you want to specify your own domain with catch-all email services, it'd be VERY hard to sign up automatically.
I personally don't think they would do anything about having the same email service, lots of people may use them for all they know.
What will catch us out is the lack of diversity in usernames. I don't suggest going 1, 2, 3, 4, 5, etc. but people are asking for it.
Personally, I'm using "Username"#{3.times.map...}" to create my specified username with 3 random numbers trailing it from 1-9, which gives a possible 729 unique combinations, so the chances I hit a duplicate are pretty low, unless I create HUGE amounts of accounts, but then i'd just go to 4 trailing numbers to give over 6,500 combinations.
In my opinion, we're never going to be fully undetectable as there's always at least one constant variable in the whole thing, they could catch us if they wanted to, but chances are they won't bother.
EDIT
Infact, I change my mind on having incrementing numbers 1 up, it does seem rather simple to detect.
To the people requesting this, would you be satisfied with user input for the username, but 3 (or more) random numbers on the end? I'd like to meet somewhere in the middle between ease of use, and randomly generated data.
Password would also be user input without any random generation if requested, I'm not sure duplicate passwords would flag, otherwise everyone with the password "password" would be flagged haha..
Last edited by JakeP; 08-01-2016 at 10:33 AM.
-
Post Thanks / Like - 2 Thanks
-
-
Corporal
TL;DR for my edits,
User input through command line to set username+random 3 digits for login
User input for password, no randomization.
Yes, or no?
-
Post Thanks / Like - 1 Thanks
Synapse7 (1 members gave Thanks to JakeP for this useful post)
-
Member
Originally Posted by
JakeP
Password would also be user input without any random generation if requested, I'm not sure duplicate passwords would flag, otherwise everyone with the password "password" would be flagged haha..
I honestly like how the password is completely jumbled randomness atm. If I am giving the account to another user it entices them to go to PTC and change their password and feels more "secure". But do it as best as you see fit!
-
Member
Originally Posted by
JakeP
TL;DR for my edits,
User input through command line to set username+random 3 digits for login
User input for password, no randomization.
Yes, or no?
Yea please . Dang side you really adding to this effectively . I'd really appreciate a pm if you have th time to ask a some more questions
-
Program don't work anymore, any update ?
Thanks in Advanced