Password generator and password limitations

I would like suggestions for a good strategy for dealing with web sites that have arcane rules about what must or must not appear in a password.

My ideal are the sites that allow a good range of characters, a relatively long password length, and no special rules. In those cases, my password is chosen by a password generator from e.g. 6820 equally probable possibilities. Nice and easy.

Even if there are rules, with a reasonably long length, I can often get an acceptable password by spinning the generator a few times.

The worst case are short passwords with rules like at least one character from each of two or three classes. My current strategy is to edit a generated password making as few changes as possible to make it acceptable. I don’t like this, because it depends on my own ability to make random choices, which is not good.

Is there a better strategy, or even a known best strategy? – Most secure password generator.


Why are you selling this site?

Two years ago I coded this ultra-secure password generator with multiple settings that allow users to create passwords as safe as possible.
I'm a full-time programmer and I did not have time to do SEO, social or other kinds of promotion.
How is it monetized?
This site can be monetized with Adsense or other similar platforms and niche affiliate programs such as a paid password… – Most secure password generator.

Any plan for custom engine generator Or standalone Engine Generator??

Hello sven or GSA staff
once im hiring a coder to write custom engine for me for private use but end up being spammed (it seems he use the web platform for him self ) ..Yes there a instructions in manual pages but for non tech person it seems not doable to do it by my self . there’s also post from GSA forum use he but it need 3rd party apps (zenoposter) which i don’t have
Is it possible or may be a suggestion for GSA Dev Adding Feature to generate .ini For custom web platform? or standalone program just like captcha breaker or platform identifier ..i don’t mind to buy the tools If the dev Planning to create one
Links generated by GSA nowdays is not good enough

Is it possible to transfer data with a really unique seed of a psudo random number generator

I have thinking about this idea for over 5 years and i don’t have the complete technical knowledge to fully grasp the idea I’m having.

The premise of the idea is to have an extremely high base number system like base 85 / Ascii85.

Then use that high base number to express an extremely verbose seed for a pseudo random data generator.

Then using your data generator, generate out data to a specified length of characters.

The business case for this would hopefully be a way of transferring data in an extremely compressed format that is actually just a function expression of how to calculate out your large set of data.

So for example if you want to move 10 gigabytes of data, you somehow serialize that 10 gigabytes down into a random seed that propagates back out into the same 10 gigabytes again.

The reason for something like Ascii85 is so that you could express a high amount of unique permutations.

This idea is probably completely crazy and or incorrect, but i have wondered about it for so long i really wanted some advice on it.

Should a password generator validate it’s output against a dictionary?

If I were to design a password generator is it best to leave it truly random or validate it’s output to avoid certain passwords?

For example if my password generator was truly random, it’s possible it’s output could be “password”.

Where do you draw the line, should it just scan for common passwords, or ensure nothing in the entire string matches a know word? E.g. “fg3~nfpasswordh&tr”.

Does doing this reduce the security of my password generator because the possibility space is reduced?

Excessive Vulnerability Count in Yeoman SharePoint Generator

When I run

yo @microsoft/sharepoint

and pick standard options for a SharePoint Online WebPart with No JavaScript framework, NPM shows 1956 vulnerabilities with 140 of them being high priority.

I don’t understand why a fresh out of the box project would contain this many “issues”.

I searched the internet and a few of the blogs I ran across seemed to imply these “vulnerabilities” were actually just with the build environment and would not be deployed to the server or client machines [1][2]. Indeed, I think many people have been ignoring these vulnerabilities for quite some time since today’s vulnerability count seems much higher than the counts the authors were getting back when they originally published their posts.

To make matters even more confusing, while I think [2] does seem to indicate the problems are not going to be deployed, it still seems to indicate the “vulnerabilities” should be addressed. Also, [2] appears to be selling something so the author may be a little biased.

Running “npm audit” and checking the “Dependency Of” flag per [1] does seem imply that the vast majority of these vulnerabilities are specific to the development environment. It does in fact, seem to me that these problems will never make it into the SharePoint Online server or onto the machines of our end users.

Given the above, what should I do about this massive list of “vulnerabilities”?

[1] –
[2] –

Prime Number Generator (6n + 1 or 6n – 1)

This generator is like most where it brute forces an integer: it see whether the integer is divisible by any of the primes; if so, then it’s not a prime and vice versa. This though only compares values 6n + 1 and 6n - 1 starting with n as 1 as all primes larger than 3 can be written as 6n + 1 or 6n - 1 where n is a positive integer.

Examples: 7 is 6(1) + 1 (n = 1) and 17 is 6(3) - 1 (n = 3).


primes = [2, 3] limit = 0 n = 1 is_prime = True  while True:     try:         limit = int(raw_input("Enter a positive integer larger than 3: "))     except ValueError:         print "Please enter a positive integer larger than 3!"     else:         if limit <= 3:             print "Please enter a positive integer larger than 3!"         else:             break  while True:     minus_prime = 6*n - 1     plus_prime = 6*n + 1      if minus_prime < limit:         for x in primes:             if minus_prime % x == 0:                 is_prime = False                 break         if is_prime:             primes.append(minus_prime)         is_prime = True     elif minus_prime > limit:         print primes         break      if plus_prime < limit:         for x in primes:             if plus_prime % x == 0:                 is_prime = False                 break         if is_prime:             primes.append(plus_prime)         is_prime = True     elif plus_prime > limit:         print primes         break      n += 1 

Basically, given preset primes 2 and 3, find all primes that are less than limit by producing numbers with 6*n + 1 and 6*n - 1 (n increases by one every loop) and checking first if they are over the limit. If so, stop the loop and print out the primes (as a list). If not, brute force through primes to see if the number is prime. If so, add to primes. Else, continue. limit is checked in the first while loop to ensure validity.

I am wondering how to improve the performance of my program, improve its structure, and make it more Pythonic. Try it here

Invalid argument supplied for foreach() – Crud Generator

estoy usando Laravel Crud Generator y al momento de querer insertar un registro me aparece el siguiente error se que esta en el foreach pero no se como corregirlo

Invalid argument supplied for foreach() (View: C:\laragon\www\sistema\resources\views\admin\perfil\form.blade.php) 

el codigo de mi vista es:

<div class="form-group {{ $  errors->has('category') ? 'has-error' : ''}}">     <label for="category" class="control-label">{{ 'Category' }}</label>     <select name="category" class="form-control" id="category" >     @foreach (json_decode('[multi-empresa: Multi-empresa, empresa: Empresa]', true) as $  optionKey => $  optionValue)         <option value="{{ $  optionKey }}" {{ (isset($  perfil->category) && $  perfil->category == $  optionKey) ? 'selected' : ''}}>{{ $  optionValue }}</option>     @endforeach </select>     {!! $  errors->first('category', '<p class="help-block">:message</p>') !!} </div>