Microsoft is "suspending" emails (because of the Canadian SPAM law effective 7/1). I found these REALLY useful. I’m sure others did as well.
Notice to IT professionals:
As of July 1, 2014, due to changing governmental policies concerning
the issuance of automated electronic messaging, Microsoft is
suspending the use of email notifications that announce the
* Security bulletin advance notifications
* Security bulletin summaries
* New security advisories and bulletins
* Major and minor revisions to security advisories and bulletins
In lieu of email notifications, you can subscribe to one or more of
the RSS feeds described on the Security TechCenter website.
For more information, or to sign up for an RSS feed, visit the
Microsoft Technical Security Notifications webpage at
So then I looked at the page referenced above. My "quick and dirty" very basic ‘Security Notifications from Microsoft Feed Reader’ app is now available in the Windows Store. http://apps.microsoft.com/windows/app/security-notifications-from/f5459c09-6233-4100-bfe1-d198111fc30b
I hope that Microsoft reinstates the emails after they figure out how to exclude Canadian customers who don’t want to receive this important information.
A few days ago, I started receiving all kinds of strange notifications and friend requests in an account that I don’t use for Facebook. I started getting concerned because of the volume of requests. I wasn’t sure if this was a phishing scam or malware, but I was getting annoyed at the number of pieces of mail being generated. The owner had signed up as Why-do U-Care. The name alone made be wonder what kind of scam was about to happen.
Of course each of these had a link to whatever I was being notified about. So, first in a VM to be safer, I clicked one of the links (the source of the email message actually was a legit Facebook non spoofed header, but just to be safe…) and without any trouble at all, I was able to reset the password to this phantom account.
.Here is the password change email I received.
Now how this person signed up with one of my email addresses and was able to use the account for a few days without verifying that email address is troublesome indeed.
Anyway, I reset the password and logged in to the account to insure that there wasn’t anything else going on that impacted me. This is some guy in California. A really stupid one to boot.
Next I got a throw away email address elsewhere and added it to the account, verified it, then set it as primary and removed my own misused email address. I changed the account name to DoNot Use. I then attached the email address that *I* own to a different Facebook account that *I* own as a secondary address. (Not my main account). Verified it, etc.
I then went into Why-DO U-Care, now DoNOT Use account with the throw away account login and scheduled it for deletion.
I am now getting about six of the following an hour from Facebook that look like:
Each time I click the button didn’t initiate this choice. This joker keeps trying to claim MY email address.
Facebook has a problem, and there is a person out there that needs psychiatric help and needs to be restrained from using the Internet (or at least who needs to understand he just can’t make up any old email address).
Seriously, Facebook allowed me to access this account just by initiating a password reset because I happen to own the email address this stupid person used. There is a security issue here, and this person should have never been allowed to use the account without acknowledging an email sent TO the email address he was trying to use. If anyone knows anyone at Facebook, please relay.
In Part 3, I wrote about setting up dynamic DNS and port forwarding for my cameras and desktop controller as well as authentication for all exposed web servers. Once this is set up properly, camera output can be viewed in real time, any time I want to check in on what’s happening chez moi. If I were to get a motion detection email alert, I could immediately recheck camera output from all my cameras.
The Blue Iris web controller Windows software that I selected is viewable from any web browser. It detects mobile use and presents an iPxxx interface when I access it from my iPhone or iPad. I’ve added the URL to my bookmarks and to my Home screen on my iPxxx devices. Here is what I see from my iPad after I enter the proper credentials (since authentication was set up):
I can select an individual camera from the drop down menu or just tap a camera to see a larger view.
I added a bookmark for the Blue Iris web server and also added it to my iPad and iPhone Home Screens for easy and fast access.
As I mentioned in Part 1, setting up the D-Link IP cameras (and IP camera in general most likely) is easy if you have a simple network. This means you
1. Only have 1 camera
2. Don’t need to access the camera either directly or through any software from outside your own home network
3. Don’t already have a web server running on the default port 80 (if your provider does not block this port)
If you are serious about DIY Home Security/Surveillance, you will need to configure multiple cameras on multiple ports, set up dynamic DNS (if you don’t have his setup already) and forward ports on your router. On your router, you should set up DNS reservations for your cameras, and if using a desktop software controller, a reservation for that computer and port forwarding for the port you are using for the desktop controller software web server. You can get free dynamic DNS from the folks at dyndns.com and if you have a decent router, there should be a place to enter your dyndns host name and password and the router will do the work of ensuring that if your Internet DHCP IP changes, updates are made seamlessly. D-Link actually offers a private branded dynamic DNS set up service from inside their admin interface. It should be ok to use this (last time I checked they were using the services of dyndns.com).