New feature: IP whitelisting
We've just deployed a feature update for Yetti, which adds support for IP whitelisting. Whilst not a feature you'd want to use on a public site, it's great for private sites and intranets.
By default (with a blank whitelist), a site is open and accessible to all visitors. However, if you set one or more IPs in the whitelist, it'll become accessible only to visitors with a valid IP.
You can allow individual IPs and ranges or use wildcards, subnet masks or CIDR notation and, of course, any combination of these.
Be careful before making use of this feature - remember that it's use will block your site from everyone else - it's not a blacklist. But it's great for when you really are running a private site that's not accessible to the general public.
Anyone who isn't permitted access will receive a 403 Forbidden header and will be shown your site's 403 error template so you can customise the design and message as you see fit.
And as a final note, this feature only locks a site front-end, so if you forget to put your own IP in there, don't worry as you'll still be able to get to the admin to add it.