About Me

Since the 1990s I have been very involved with fighting the military "don't ask don't tell" policy for gays in the military, and with First Amendment issues. Best contact is 571-334-6107 (legitimate calls; messages can be left; if not picked up retry; I don't answer when driving) Three other url's: doaskdotell.com, billboushka.com johnwboushka.com Links to my URLs are provided for legitimate content and user navigation purposes only.
My legal name is "John William Boushka" or "John W. Boushka"; my parents gave me the nickname of "Bill" based on my middle name, and this is how I am generally greeted. This is also the name for my book authorship. On the Web, you can find me as both "Bill Boushka" and "John W. Boushka"; this has been the case since the late 1990s. Sometimes I can be located as "John Boushka" without the "W." That's the identity my parents dealt me in 1943!

Tuesday, February 27, 2018

Today, on one of my sites protected by SiteLock, I got a bizarre
captcha when I tried to access it, reading “V1 SHUTDOWN On 2018/03/01”.I also got an advisory that I can opt-out of
the warning, and thar getting means that SiteLock has detected the symptoms of
possible botware or malware on your computer. I do get intercepted occasionally by SiteLock normally.

Trend Micro virus scans never find anything, and this
happens once in a while, but I’ve never gotten a captcha message like this.

Thursday, February 15, 2018

I wanted to share Electronic Frontier Foundation’s page on
protecting your privacy from your telecom provider, by Amul Kalia, here.There is a lot of discussion of VPN’s and (especially
overseas) TOR.There is also a list of
smaller telecom’s, not available everywhere, that seem less interested in
monetizing your personal information.

Likewise, one could ask questions about hosting companies,
who from my experience generally keep hands off.

Nevertheless, there are automated tools in use that might be
able to detect (by digital watermark) illegal content when it is backed up in a
cloud (I know of at least one arrest in Maryland (of a school employee) over
this possibility).Likewise Google
searches attachments to emails, which has resulted in at least one arrest in
Houston, TX. There are cases where there
could be legal issues with intentionally viewing some social media images or
video portions out of context, and this might be detectable.

Monday, February 05, 2018

Electronic Frontier Foundation has a valuable advisory paper
today reminding visitors that they should always install software updates
promptly. The advisory appears as a Security Education Companion from Surveillance
Self-Defense.

The article maintains that updated systems are much less likely
to be targeted by malware or known enemies because they are much more “expensive”
to attack.

It also advises that notification normally does not come by
email but within the product itself, so subverted updates should be extremely
rare.

It also admits that there is a small risk with an update of failure,
but an older system is already “broken”.

I have to admit that secondary backup computers (for travel)
don’t get updated as option, and that may be one reason a Lenovo ultra table
that I bought in early 2015 with Windows 8 became unusable this year.

I’ve also been unwilling to rock the boat with a 2011 Macbook
and Sibelius, because there is so much music that is working there that way
now. But that could be one reason why I’ve had trouble with iCloud recently.

I might also take exception to this idea when Microsoft pushes operating system replacements on users with older hardware. I burned up a Toshiba laptop in 2014 going from 8.0 to 8.1; the motherboard just got too hot.

It may be advisable to look into the issue of whether you “use”
all the services you have with an account you have, or someone else could hack
them without your knowledge. Then I don’t
know who would be legally liable. You don’t hear this idea discussed very often.

Saturday, February 03, 2018

I continue to receive strange emails claiming signon to my
iCloud account and purchases overseas, especially in Indonesia and former Soviet
republics. I have marked them all as spam
and forwarded them to Apple’s reportphishing@apple.com. AOL does not seem to catch these as spam (nor does it catch emails that say your own AOL mailbox has been closed).

I am also getting emails claiming my iCloud account has been
canceled, with the sender addressed spoofed well enough even when tested by mouse-over
to appear to have come from Apple. But the iCloud id and pw still work so that
appears to be phishing. These also have been forwarded to Apple.

Yet security company Webroot is not aware of a specific
problem with phishing involving iCloud.

However employees at an Apple store told me there has been a problem.

So far there is no evidence of invalid charges or of fake
accounts overseas in my name. But it is
conceivable that someone could get arrested overseas if a fake identity had
been created and the person went to that (third world) country. It is
conceivable that fake accounts could result in judgment attempts.

Another possible risk could be that a hacker could place illegal content in an iCloud account. Users should always periodically spot check all online accounts that they have for possible abuse.

This does seem to be a very large and bot-automated phishing
attack probably from parts of the former Soviet Union.

Analytics

Privacy Policy

Privacy Policy for billsinternetsafety.blogspot.com

If you require any more information or have any questions about my privacy policy, please feel free to contact me by email at JBoushka@aol.com.

At billsinternetsafety.blogspot.com , the privacy of my visitors is of extreme importance to me. This privacy policy document outlines the types of personal information is received and collected by billsinternetsafety.blogspot.com and how it is used.

Log Files Like many other Web sites, billsinternetsafety.blogspot.com makes use of log files. The information inside the log files includes internet protocol ( IP ) addresses, type of browser, Internet Service Provider ( ISP ), date/time stamp, referring/exit pages, and number of clicks to analyze trends, administer the site, track user’s movement around the site, and gather demographic information. IP addresses, and other such information are not linked to any information that is personally identifiable.

Cookies and Web Beacons billsinternetsafety.blogspot.com does not use cookies.

DoubleClick DART Cookie

.:: Google, as a third party vendor, uses cookies to serve ads on billsinternetsafety.blogspot.com .
.:: Google's use of the DART cookie enables it to serve ads to your users based on their visit to billsinternetsafety.blogspot.com and other sites on the Internet.
.:: Users may opt out of the use of the DART cookie by visiting the Google ad and content network privacy policy at the following link.

Some of my advertising partners may use cookies and web beacons on my site. My advertising partners include ....... Google Adsense

These third-party ad servers or ad networks use technology to the advertisements and links that appear on billsinternetsafety.blogspot.com send directly to your browsers. They automatically receive your IP address when this occurs. Other technologies ( such as cookies, JavaScript, or Web Beacons ) may also be used by the third-party ad networks to measure the effectiveness of their advertisements and / or to personalize the advertising content that you see.

billsinternetsafety.blogspot.com has no access to or control over these cookies that are used by third-party advertisers.

You should consult the respective privacy policies of these third-party ad servers for more detailed information on their practices as well as for instructions about how to opt-out of certain practices. billsinternetsafety.blogspot.com 's privacy policy does not apply to, and we cannot control the activities of, such other advertisers or web sites.

If you wish to disable cookies, you may do so through your individual browser options. More detailed information about cookie management with specific web browsers can be found at the browsers' respective websites.