Re: permit-access wildcards?

--===============1957951393014643565==
Content-Type: multipart/signed; boundary="Sig_/qW_PAK/ijA2KCdgU7/.DoGV";
 protocol="application/pgp-signature"; micalg=pgp-sha256

--Sig_/qW_PAK/ijA2KCdgU7/.DoGV
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Richard Glaser <[email protected]> wrote on 2023-08-23 at 20:55:40:

> Basically, we are blocking all other domains, except...
>=20
>=20
> *.lib.utah.edu
> *.utah.edu
> *.duosecurity.com
> *.apple.com
>=20
> And some miscellaneous other that are needed for the above website needs.
>=20
> If permit and deny supported regular expression it would make it much
> easier to implement, but currently need to do allow ever hostname per
> domain and some because the require wildard support are an option.
>=20
> Any other suggestions on accomplishing this with our wildcard or regular
> expression support for permit deny access?

If you want to treat all clients the same anyway you should be able
to use the +block{} action [0] with enforce-blocks [1] enabled.

Just block everything ("/") and then make exceptions for the
hosts that should be accessible.

Quoting the documentation [2]:
| When compiled with FEATURE_PCRE_HOST_PATTERNS patterns can be
| prefixed with "PCRE-HOST-PATTERN:" in which case full regular
| expression (PCRE) can be used for the host pattern as well.

For your example patterns you shouldn't need this feature, though.

Fabian

[0] <https://www.privoxy.org/user-manual/actions-file.html#BLOCK>
[1] <https://www.privoxy.org/user-manual/config.html#ENFORCE-BLOCKS>
[2] <https://www.privoxy.org/user-manual/actions-file.html#HOST-PATTERN>

--Sig_/qW_PAK/ijA2KCdgU7/.DoGV
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEETzbBfzgWkTZUoehQaRgikYuiNxwFAmTrLtcACgkQaRgikYui
NxwKbg/6AxAwSIN4ncqxputftODVGpXY53aKvL8hsr+A0dGeXjtFOi3+5QDkPrdt
/HPW/N2dYcywkTZ7CuToZVyh4jBqIOV09eTD8hI+4yjhnlu1mPMP7309clOhS463
K4EmIu9tj+XxrxLdvRpJyIU3jBrzUow0kDTuoCDD7j8Xd4pZ1HXDBywAhll6WuJt
2J6eqg1Qq3uHaRu4XnmSl6sZNNBNYcr7kJrmF+kUQmTF7e/aAIWlaa5DAmauiICk
r0ymZrtbCbYeqWWOmNsIw3YYJgOG8jeY8PNTzy+IadDmbnSywdeEsvNz48FACuLr
cmDk8XzlSyrclZa+BYHLEoQrVDzy46Sl2zV1tiA/DHOr0WgyvnZIQCApSXecmXJC
stJGcBCC6Pz9QhQOYAAuH520TZKGgJMu7LR4MWmH7MgxZHDd88yS2KYNYkaaCkIW
0aWexjXjcA1+DaZymU5VWDBvSLxAzbelAc/QPehYpqPec1JH9uWeiGOXBhmNAMzM
lZ9+UMuxQwS6mE1KrtVeOQYMELIr0ttDfFx0+vMjY1W41NMkE93PU48v4a1ACik1
1wqnTpz/HScQOOQ+PeHBG6t8iW3eJKabhWJKoJtiWWhDe579RJY6vpYgwSiAqXuq
LxLri+AlSKOlqxII1bHWVej8yLrI42vyzpaF8su2ZwcR2ImtLJc=
=IDWU
-----END PGP SIGNATURE-----

--Sig_/qW_PAK/ijA2KCdgU7/.DoGV--

--===============1957951393014643565==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Privoxy-users mailing list
[email protected]
https://lists.privoxy.org/mailman/listinfo/privoxy-users

--===============1957951393014643565==--