In the email I got from AT&T regarding this data breach was: "Protecting customer data is a top priority. We have confirmed the affected system has been secured. We hold ourselves to high privacy standards and are always looking for ways to improve our security practices."
This story reminds me of the time I accidentally/naively set up a ssh honeypot when I configured the router I was using at the time (this was a long time ago) to forward incoming SSH connections to a ReadyNAS (which was using a Sun SPARC processor) in my house. I did that so I could log into it while I was away from my house. One day, I ssh'ed in and notice that the ReadyNAS was running very slow which surprised me because I thought it was idle. I checked the CPU usage and the sshd was using 100%. First, I thought it was a bug but it occurred to me I should check my incoming ssh connection attempts in my router log. Turns out there were a ton of ssh connection attempts coming from an IP address assigned to China. In response I changed the router port forwarding for incoming ssh connections to use a non-standard port number, like 55,243, and after that my ReadyNAS was no longer bombarded with ssh connection attempts. Lesson: try to avoid forwarding standard port numbers.
I still remember when a co-worker told me that the biggest problem with C is that programmers are terrible at memory management. Given the number of memory corruption bugs I encountered in 27 years of working with C, I have to say that rings true.
I see the article mentions Solaris, an OS that I am very familiar with, which had me thinking about the memory corruption detection Solaris offerred. Among the development features Solaris supported were two memory corruption checking libraries (libumem, watchmalloc) that could easily be used without have to recompile binaries to link with them. Libumem had support for detecting memory leaks, buffer overruns, multiple frees, use of uninitialized data, use of freed data, etc... but it could not detect a read past an allocated buffer which is where watchmalloc came in handy. To use either with an executable binary was as easy as:
$ LD_PRELOAD=libumem.so.1 <executable filename>
I found a lot of memory corruption bugs using libumem in particular including some in MIT Kerberos that were severe enough to be considered security vulnerabilities. Sadly, Solaris is now in support mode thanks to Ellison and friends at Oracle.
I've been using OmniOutliner for a long time, mostly to take notes in an organized fashion and I'm pretty happy with its functionality, however one thing it doesn't provide is split editing windows on the same outline. This is something I've used with Vim and found it to be very handy when editing code because I frequently needed to look at code at one spot in a file while modifying/creating code in another place in that same file. Anyone know if there is a macOS outliner that can do this?
I'm not sad to see it go. What I vaguely remember about macOS Server was that macOS upgrades were fraught regarding whether the macOS Server would function normally afterward requiring me spending time trying to debug what was wrong. Since macOS eventually started offering some of those services, like Time Machine Server, natively I've been using those successfully. For the services macOS doesn't offer I now have the option of using Home Brew to install those services.
I've been using Firefox for a looong time. What convinced me to choose that over any other browser is the following:
A. It ran on macOS AND Solaris (which I worked on for a looong time).
B. It took awhile for the feature to arrive but eventually I was able to sync my bookmarks across both platforms (this made me so happy).
At this point, even though I'm not using Solaris anymore (sniff) I'm so used to it I don't feel the need to try anything else.
When I read "People don’t want to run their own servers, and never will." I thought, what an elitist (and libertarian) idea to assume people would be able to afford and manage a server in their home but also afford/have access to the required Internet bandwidth. Yuck.
I'm using Pushover (https://pushover.net/) to send notifications to my Apple devices. To make use of it easier on command line I wrote a simple Python script which I've found to be very useful for things like allowing Transmission to send notifications when a download is finished or in scripts that do backup jobs which take a long time, letting me know when my Mac has booted, etc... Reply to this comment if you're interested in my script (note that the pushover site has good examples of how to call their API).
On my Mac I use a utility called Quicksilver that has an option to record and recall copies I've done then shows me a list of the last 10 copies from which I can drag one of them into an input field. This works on input fields that don't allow normal copy/paste. Quicksilver does a number other things like app launching -- I'm a fan.
Good point. As a long time (lived here since 1979) Austin resident I can tell you that it's a lot of fun to live here, in particular for someone in their 20's or 30's. There are a bunch of live music clubs, several large music festivals, SXSW, lakes and the Hill Country for biking, rivers to tube on, etc... On top of this the University of Texas main campus (~50K students) is located here and there are other universities in addition. This city is a magnet in Texas and surrounding states for tech talent unlike say, Waco because people want to live here.
Creating and maintaining a large software project that "features" differing crypto strength depending on the country it's being shipped to is a HUGE PAIN IN THE ASS! I know because this was something I did for the Solaris implementation of Kerberos. What an excellent way to introduce bugs that never get tested. Crypto/security is hard enough to get right without added complications like this.
That may be the reason but I would point out that many companies that sell high end systems and OSes (IBM, Sun/Oracle, etc...) at some point require the customer pay for supporting older systems (even then there is an age cutoff). For Apple, supporting older Minis without the customer paying for this support doesn't seem to be in Apple's interest from a business standpoint.
Man, in the last couple of years I've been counting myself lucky in that I bought a late 2012 Mini with the fastest i7 offered. It appears to be downhill for the Mini from then on.
The problem, for me at least, is I don't want anyone smearing their greasy fingers on my display. I like seeing things on a clean display so I would never buy a laptop with this "feature".
Well, now I feel better. 8^)