deadfece

Office 365 has also offered Focus Time scheduling for 18mos+

https://docs.microsoft.com/en-us/viva/insights/personal/use/...

reminds me of this article from 07:

https://web.archive.org/web/20070901234027/https://lightning...

On a vastly more practical note, check out JDM_WAAAT's site https://www.serverbuilds.net/ . They're more piecemeal parts list, but he has a very reasoned approach to select parts that deliver value/performance at their price point, and are available at the selected price in sufficient quantities.

When I joined, the ToS explicitly allowed users between 16 and 18.

http://www.screw-paypal.com/tos_exposed_section/tos_june_200...

It looks like their ToS changed in February 2003 to enforce an 18-only model.

I think the best news out of this is hopefully that it seems you (as Canonical) have shifted away from "This is not a democracy. [...] we are not voting on design decisions." and the (paraphrased) "This is good because we [Canonical] made it!"

You could help open source projects get their code into Coverity, a static analysis tool. It helps if they have a github repo, and it's even better if they use Travis-CI. Using Coverity will help identify some security issues that can be mitigated right away.

Secondly, you can fuzz FLOSS software, using something like afl-fuzz, American Fuzzy Lop. The following tutorial has some pointers to get started, and obviously software written in C is easier to get started with. If you need help with something, feel free to ask on the afl-users mailing list. You can fuzz on a CPU-heavy VM somewhere, like DigitalOcean, an Amazon spot instance, or a Google preemptible instance.

https://fuzzing-project.org/tutorials.html

In fuzzing, once you get the hang of it, you'll find that your keyboard time is the limiting factor. You'll set up a test case in 15-20 minutes, leave it fuzzing for a day, and come back to spend at least 1-2 hours working through crashes and reporting the bugs through their channels.

You may be saying "Wait I don't know anything about C," but honestly, I don't know anything about C either, and I've found hundreds of bugs with fuzzing. There are some crash dump investigation tools that give you an idea of the nature of the crash (gdb's exploitable.py) and that's usually enough to report to the maintainer. When the maintainer has a fix released, you can send an email to the oss-security mailing list detailing what you know about it. MITRE can assign a CVE on the mailing list if you describe the bug appropriately when you ask for one.

Ten years later, they made a handheld version of this.

In the present day, civilians own tanks, cannons, rocket launchers, grenades, machine guns, explosives, etc. This has largely been the case for 200 plus years. If we ignore the some 200 years of jurisprudence supporting that ownership, then what?

"Computer" used to be an occupation for humans.

In The New York Times was February 3, 1853, an obituary stated: "Mr. Walker was widely known as an accomplished Astronomer and a skillful Computer."

So to claim that the very thing which enables us to be a computer, is not a computer, might simply be short-sighted or trying to be absurd.

At one point I set out to cook up something like this for my home network. It pleases me to see it already done and to a level far beyond my capabilities.

Thanks!

Some systems allow keys, but still expire account passwords.

Some systems also do not have NOPASSWD: for every group in sudoers. On those systems you are likely to have to use a password with sudo to elevate privileges.

Changing via SSH also updates shadow entries that are often used many other places, like console logons or local user references implemented in software.

Temporary passwords for firecalls.

There appears to be some recent development on https://github.com/CESNET/pakiti3

Pakiti (http://pakiti.sourceforge.net/) is another useful tool in this space.

In many instructional and self-help books, I find that the author's attempt to hit appropriate word-count for the book format bores me to no end. Even worse, it wastes my time. I bought your book, please don't waste 10% of your page count in selling me the book.

I think notable exceptions to this are found in 'The Practice of System and Network Administration' and 'Time Management for System Administrators.'

Fiction, I can read at times. For the last book I read, 'The Mote in God's Eye', I read the first four chapters or so, then put it off for 5 months, and then finished it in a week. That one does start off pretty slowly.

You don't see many of the RFC2142 addresses at all.

https://www.ietf.org/rfc/rfc2142.txt

Some of Seagate's drives require signed firmware.

http://www.seagate.com/www-content/product-content/savvio-fa...

8.7 AUTHENTICATED FIRMWARE DOWNLOAD In addition to providing a locking mechanism to prevent unwanted firmware download attempts, the drive also only accepts download files which have been cryptographically signed by the appropriate Seagate Design Center. Three conditions must be met before the drive will allow the download operation: 1. The download must be an SED file. A standard (base) drive (non-SED) file will be rejected. 2. The download file must be signed and authenticated. 3. As with a non-SED drive, the download file must pass the acceptance criteria for the drive. For example it must be applicable to the correct drive model, and have compatible revision and customer status.

Just an FYI here, but UltraVNC and RealVNC Enterprise do support VNC encryption.

http://adamwalling.com/SecureVNC/

https://www.realvnc.com/products/vnc/documentation/5.0/guide...

I found a lot of improvement in my guitar practicing by reading "Fundamentals of Piano Practice."

The author made it available for free at http://pianopractice.org/

As I play fingerstyle I study hands separated by separating the bass and melody as thumb and fingers, then move to hands together.

I also analyze the piece to find the hardest as well as the most repetitive measures, work those out and pick up the rest of the piece. You also work these measures with transitions, by playing the preceding measure or half measure leading in and out of the measure you're practicing.

I typically don't get a lot of time to practice so I will pick up my guitar at random and play measures that I'm working on.

I'm glad I kept reading past the product plug.