Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Google Privacy Changes: 6 Steps To Take
Newest First  |  Oldest First  |  Threaded View
IlyaG960
IlyaG960,
User Rank: Apprentice
5/19/2015 | 1:36:42 PM
The Era of Absolute Privacy is coming! No need in queries, cookies or browsing history anymore.
Good news! The Era of Absolute Privacy is coming! No need in queries, cookies or browsing history anymore.

Google cannot protect privacy by definition: as the source of statistics (for gained from texts phrases) Google uses popularity, how popular are the phrases among people that typed the same search queries/ search for the same. Google cannot exist without spying.

However, there is structured data that can search for people - not people for information, but information for people. I discovered and patented how to structure any data: Language has its own Internal parsing, indexing and statistics. For instance, there are two sentences:

a) 'Sam!'
b) 'A loud ringing of one of the bells was followed by the appearance of a
smart chambermaid in the upper sleeping gallery, who, after tapping at
one of the doors, and receiving a request from within, called over the
balustrades -'Sam!'.'

Evidently, that the 'Sam' has different importance into both sentences, in regard to extra information in both. This distinction is reflected as the phrases, which contain 'Sam', weights: the first has 1, the second – 0.08; the greater weight signifies stronger emotional 'acuteness'.
First you need to parse obtaining phrases from clauses, restoring omitted words, for sentences and paragraphs.
Next, you calculate Internal statistics, weights; where the weight refers to the frequency that a phrase occurs in relation to other phrases.
After that data is indexed by common dictionary, like Webster, and annotated by subtexts.
This is a small sample of the structured data:
this - signify - <> : 333333
both - are - once : 333333
confusion - signify - <> : 333321
speaking - done - once : 333112
speaking - was - both : 333109
place - is - in : 250000
To see the validity of technology - pick up any sentence.

Do you have a pencil?

My technology came from Analytic Philosophy, Internal Relations Theory.
Number 6
Number 6,
User Rank: Apprentice
3/5/2012 | 5:30:23 PM
re: Google Privacy Changes: 6 Steps To Take
I use 2 browsers: IE configured to accept all cookies and Firefox configured to ask. Use Firefox for serious work and IE for temporary searches. Wipe out IE's cookies every couple weeks. With Firefox, first deny, and if needed accept for session only. Remember only for sites I regularly visit.

With a firewall, have never had a problem.
kiapiz
kiapiz,
User Rank: Apprentice
3/3/2012 | 10:06:06 PM
re: Google Privacy Changes: 6 Steps To Take
Checkout http://donottrack.me

Simple steps to opt-out from Ad Networks tracking you
You can also clean the data collected about you.
SLINK000
SLINK000,
User Rank: Apprentice
3/3/2012 | 1:29:33 PM
re: Google Privacy Changes: 6 Steps To Take
One thing that I don't see is a suggestion to manually accept all cookies. Of course this is a hassle for a little while while you build up the list of accept/reject cookies, but I can say that I have never had an unrecoverable virus/spyware problem. And the count of problems in many years stands at two, I believe. I mentioned this trick in my book - Link Em Up on Outlook - and bring it up every time that I can. It seems that not too many people embrace this simple step.
Number 6
Number 6,
User Rank: Apprentice
3/2/2012 | 6:30:00 PM
re: Google Privacy Changes: 6 Steps To Take
Wish the headline wasn't misleading. 6 steps are more like 2 useful, Google-specific steps, 2 non-Google suggestions and 2 funny but not really useful suggestions. Heading back to my cave now before Number 2 spots me.
ANON1237925156805
ANON1237925156805,
User Rank: Apprentice
3/1/2012 | 9:35:51 PM
re: Google Privacy Changes: 6 Steps To Take
Oops! I menat to say even in the space that we CAN control no one is really willing to give up their newfound conveniences to protect their anonymity. The Googles of the world know this.
ANON1237925156805
ANON1237925156805,
User Rank: Apprentice
3/1/2012 | 9:32:54 PM
re: Google Privacy Changes: 6 Steps To Take
This is a sad place we've ended up in. What we defeated post J. Edgar with laws like the Freedom of Information act we are now giving back without a thought. We have no idea who's got what data and what they will do with it.

Thanks to the Patriot Act, that's true even at the gov't level over which we have no apparent control. As you write, even in the space we can't control, no one is really willing to give up their newfound conveniences to protect their anonymity. So we are walking down a very unfamiliar path. By the time the first major calamity happens it'll be too late to turn back.

Stay tuned.
joe345
joe345,
User Rank: Apprentice
3/1/2012 | 3:14:23 PM
re: Google Privacy Changes: 6 Steps To Take
What about using add-ons like TrackMeNot?


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type=&quot;text&quot;` via a javascript &quot;Show Password&quot; button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn&acirc;&euro;&trade;t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file