Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lack of documentation about how to create a password rule #2

Open
shdf2 opened this issue Apr 8, 2019 · 18 comments
Open

lack of documentation about how to create a password rule #2

shdf2 opened this issue Apr 8, 2019 · 18 comments

Comments

@shdf2
Copy link

shdf2 commented Apr 8, 2019

Hello,
could you please make some documentation about how to create a password rule ?
let's say i want my passwords to be :
Minimum 8 characters
Maximum 32 characters
with Digits
with uppercase
with lowercase

how i do that ?

Thank you very much for your help

@openbullet
Copy link
Owner

openbullet commented Apr 8, 2019

Alright I'll see where to put more info about that, but anyways let's say your password slice is called PASSWORD. You will need to add rules like
PASSWORD MinLength 8
PASSWORD MaxLength 32
PASSWORD Contains Digit
PASSWORD Contains Lowercase
PASSWORD Contains Uppercase
If these are all verified then your password will be accepted as valid and it will be checked with the config, otherwise it will be immediately flagged as a FAIL and OB will move to the next one.

@shdf2
Copy link
Author

shdf2 commented Apr 9, 2019

Like this ?

@MeowBullet
Copy link

MeowBullet commented Apr 9, 2019

@shdf2 it depends what is your slice named in environment.ini?

example below

[WLTYPE]
Name=Credentials
Regex=^.*:.*$
Verify=True
Separator=:
Slices=USER,PASS

so if your slice is called Pass1 which would for example be

Slices=User1,Pass1

If it however was PASSWORD

Slices=USERNAME,PASSWORD

Then you would do it like this

PASSWORD MinLength 8
PASSWORD MaxLength 32
PASSWORD Contains Digit
PASSWORD Contains Lowercase
PASSWORD Contains Uppercase
```

@openbullet
Copy link
Owner

openbullet commented Apr 9, 2019

Thank you @MeowBullet for the explanation.

@openbullet
Copy link
Owner

Actually let me reopen so I remember to update the documentation with a section on this ^_^

@openbullet openbullet reopened this Apr 9, 2019
@shdf2
Copy link
Author

shdf2 commented Apr 9, 2019

i have to study that thing because i really don't understand what is that "Slice" thing and its meaning...

The way to do it in BB what very clear, i don't understand why it is made that way now ?

Thanks @MeowBullet i'll try to understand...

@MeowBullet
Copy link

Go to your settings folder, open it up locate the environment.ini file, edit It to change your slice under credential to whatever it is you desire. The default is USERNAME, PASSWORD, However others including me reverted to USER,PASS.

The reason it's like this is its opened a big door of possibilities. It's handy to have the environment file and many of us like it.

@shdf2
Copy link
Author

shdf2 commented Apr 9, 2019

OK ! After reading your explanation 36 times i understood !!
in my environnement.ini i have this :

[WLTYPE]
Name=Credentials
Regex=^.:.$
Verify=True
Separator=:
Slices=USERNAME,PASSWORD

i loaded a config made under BB 2.5.1 and converted to loli. and this is what i can see once loaded :
image

So i guess there is a probleme, the slice must be renamed to PASSWORD in the GUI above or the ini file modded with USER,PASS like you said, right ?

@MeowBullet
Copy link

MeowBullet commented Apr 9, 2019

Correct. Whichever you choose... I would probably convert to USER,PASS so all old configs work again without modification.

@shdf2
Copy link
Author

shdf2 commented Apr 9, 2019

i think USER,PASS must be the standard. if eveyone customize its environment.ini there will be many problems, because when you share your Configs you'll never remember that people have to change their ini file too...it will not work as expected and you'll never know why...

@MeowBullet
Copy link

MeowBullet commented Apr 9, 2019

I don't share them I sell mine, and I have Modified open bullet, in a version I call MeowBullet which is made specifically for my customers, so it will always be USER,PASS as default. But Yes I see your point.

@shdf2
Copy link
Author

shdf2 commented Apr 9, 2019

ok, but that's specific to you :) Anyway thank you very much because without any explanation it was (for me) impossible to understand what i was supposed to do...

@MeowBullet
Copy link

MeowBullet commented Apr 9, 2019

The point is I took measures for mine, you can do the same wether its having a modified version to go with the configs, your own modified environment file zipped with it, or you merely just add a readme to the folder. Lol. It's not hard to let someone know. But yes 99% of people have switched to USER,PASS and I actually do like that it's set as USERNAME,PASSWORD to begin with, kind of keeps the idiots at bay lol. And yes before I read the documentation and opened up the project I was too a bit like what at first.

@shdf2
Copy link
Author

shdf2 commented Apr 9, 2019

Well, so actually, all converted configs from .bbc to .loli uses the slice name : PASS
while the environment.ini file says : USERNAME,PASSWORD

Ruri maybe switch to USER,PASS then ? as @MeowBullet said 99% are switching to this. but that 99% is 99% of people aware about it, which is in fact probably only 1% of everyone :)

@MeowBullet
Copy link

But it's good.... It keeps the idiots a bay

@openbullet
Copy link
Owner

OpenBullet should not be used for credential stuffing so I will not put USER and PASS by default, in order to prevent people who don't know what they are doing to use it for malicious purposes. This was intended, it's not been overlooked.

@kiviniitty
Copy link

Hello ! anyone know what is my issue here if user:pass contains any symbol like # OB will stuck to just that combo it change just proxy nothing else? I already made some data rules but I dont know what I do wrong
Näyttökuva (5)
here

@ghost
Copy link

ghost commented Dec 8, 2020

Alright I'll see where to put more info about that, but anyways let's say your password slice is called PASSWORD. You will need to add rules like
PASSWORD MinLength 8
PASSWORD MaxLength 32
PASSWORD Contains Digit
PASSWORD Contains Lowercase
PASSWORD Contains Uppercase
If these are all verified then your password will be accepted as valid and it will be checked with the config, otherwise it will be immediately flagged as a FAIL and OB will move to the next one.

@ghost ghost mentioned this issue Dec 8, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants