Management for Vouchers
-
HI all
Is there a Captive Portal background management Vouchers function?
instead of exporting csv file
Similar to sophosIn addition, is it possible to provide settings for generating Voucher length on the GUI?
Thanks
-
@skveen said in Management for Vouchers:
In addition, is it possible to provide settings for generating Voucher length on the GUI?
Yes. There is a forum thread explaining how to minimize the generated voucher length.
For example : pfsense generate minimal voucher length@skveen said in Management for Vouchers:
Is there a Captive Portal background management Vouchers function?
instead of exporting csv fileThe csv exists as it is easy to use.
Some print them out on cards
Other mail or sms them to the portal user.
Others just spell them out to the client.
Etc.Up to you to build a 'front end'
-
Sorry, maybe I expressed it incorrectly
For example, directly select the required length for the user to generate
🔒 Log in to viewAnd I believe that more than 90% of people don’t care what the following values are
of Roll bits
of Ticket bits
of Checksum bits
Just need an available Voucher。
Thanks
-
openssl genrsa 31 > key.private
openssl rsa -pubout < key.private >key.publicWhen I try to generate a new key,
Cannot output -
@skveen said in Management for Vouchers:
openssl genrsa 31 > key.private
Execute command like that on the 'real' command line, not the 'fake' GUI counterpart.
[23.09.1-RELEASE][root@pfSense.bhf.tld]/root: openssl genrsa 512 > key.private [23.09.1-RELEASE][root@pfSense.bhf.tld]/root: openssl genrsa 511 > key.private Error setting RSA length 0020A11B3E330000:error:1C8000AB:Provider routines:rsa_gen_set_params:key size too small:/var/jenkins/workspace/pfSense-Plus-snapshots-23_09_1-main/sources/FreeBSD-src-plus-RELENG_23_09_1/crypto/openssl/providers/implementations/keymgmt/rsa_kmgmt.c:515:
512 is the minimum.
Lower, and it fails => "key size too small".I guess the good old "create really small vouchers" time is over.
@skveen said in Management for Vouchers:
Just need an available Voucher。
The pfSense Voucher GUI page handles this just fine for me. It doesn't work for you ?
-
I guess the good old "create really small vouchers" time is over.
The pfSense Voucher GUI page handles this just fine for me. It doesn't work for you ?
It is work , but it’s too long and bad experience for guest
Operating system passwords with more than 8 characters are difficult to crack.
There is absolutely no need to crack this password
It is correct to at least provide users with different choices in different places.
For example, in a restaurant, there is no need to use the 11-digit length.this is what i think
-
@skveen said in Management for Vouchers:
For example, in a restaurant, there is no need to use the 11-digit length.
I agree.
Restaurant users don't tend to stay very long time, as they come, eat, and leave.
That's why I'm using hyper short passwords for them, like "1234", also easy to enter.
No need to create or regenerate or maintain these 'restaurant' captive portal accounts, as I give clients the access for free, I tend to keeps things as simple as possible on my side also. -
I agree.
Restaurant users don't tend to stay very long time, as they come, eat, and leave.
That's why I'm using hyper short passwords for them, like "1234", also easy to enter.Yes, but I don’t want to use psk
It is a good idea to use one Voucher per day or per table -
In the end I chose the version pfSense-CE-2.7.0-RELEASE
-
@skveen said in Management for Vouchers:
Yes, but I don’t want to use psk
What is psk ?
@skveen said in Management for Vouchers:
It is a good idea to use one Voucher per day or per table
Look in the future.
For some reason, you've decide to use a version that is severally depreciated :@skveen said in Management for Vouchers:
In the end I chose the version pfSense-CE-2.7.0-RELEASE
With the now declared "zero day OpenSSL ready" version 1 ?
You've missed : Netgate Will Migrate to OpenSSL 3 in pfSense Plus Software Version 23.09 to name just one.
Euh ... ok. Good luck.
Normally, a firewall is about security. "Confort" shouldn't come first.