I have a bunch of unknown cookies after I scanned the website, and I need to find out what these cookies do to categorize them further.
I tried to google cookies name but didn't find anything. Does anyone know what should be done in this situation?
Related
I'm trying to read one of the documentation pages on Google, but Google won't let me!
History of the issue:
Google blocks any ip address that would make a request from certain countries to its documentation pages, including the country that I'm currently living in, "IRAN". In the past, people from this country would use "proxy servers/VPNs" to change their real ip address in order to access to the documentation pages, but that won't work any more, and somehow Google can detect people requesting from this country. Nice job Google, ugh!!!
Would somebody please help me get access to the documentation pages? Either by providing me with a screenshot of the page or copy/pasting the docs as an answer? I'm specifically trying to read the following page:
https://developer.chrome.com/docs/extensions/mv3/architecture-overview/
Honestly, that makes me sick, when I see this kind of discrimination from Google! Ugh!!!
It is NOT acceptable. There is already heavy censorship on the internet by the government in "IRAN", Google is making it so much harder for people to access the information on the internet.
I'm just trying to read the documentation, could somebody please help me?
Thank you!
#مهسا_امینی
#MahsaAmini
(I'm not sure the best way to word this, and I haven't found anything yet)
Is there a setting, or a plugin to allow me to isolate cookies to the site that originated the calls. I.e. when a script is called from a 3rd party site, that can include cookie information. I.e. this is how sites like FB track your usage across everything.
What I'm looking for is a way that when I go to BobsDomain.com who happens to be making calls to Facebook.com, instead of having cookies stores like this:
BobsDomain.com/Cookie1
Facebook.com/Cookie1
it would be stored like this:
BobsDomain.com/Cookie1
BobsDomain.com/Facebook.com/Cookie1.
That way when I go to another site, I get a new cookie from facebook, and it has no idea who I am. Of course It should also have the ability to allow the cookies to be taken from other sites in particular instances. (a user's choice)
Any one know of an existing plugin like this? For Chrome, IE, or some other browser?
Thanks.
I want to show the amount of visitors for a Bolt page in the frontend. I could not find a proper solution for this in the docs or in the extensions.
Is this possible with Twig? Or should I use a third-party solution?
From the point of view of Twig, no. You would need a reliable way to log each visit, remove bots and crawlers and still no trash your database.
I wrote something for WP once, well twice actually, that attempted to do the visit tracking but it ended up putting a lot of pressure on the backend to track things that people like Google had far better resources to handle in terms of a) knowing what should be considered a 'real' visitor, and b) storing/processing the associated data.
What you however could do, implement Google Analytics to log the visitors and then use the API to display visitors on the front-end.
Might be quite a hassle to figure out how the API works for certain pages, but it will solve your problem.
Good luck!
Also see https://developers.google.com/analytics/
But Its a lie
I am facing this issue with my installer:
Installer exe when downloaded from the websites in Chrome are flagged as being malicious software.
To overcome this problem so far we have tried changing domain names,but its not a permanent solution.
Even after signing my exe with Thawte certificate the flag is still there.
I have scanned my exe with all popular AVs and there is nothing malicious in it.
How can I get rid of this chrome flag?
The webmaster site doesn't do anything to help with the false positive on installers. All it does is tell you the file is potentially malware without giving you any way of appealing or asking for a review of their findings.
With FireFox and Chrome and others using this data, you would think Google would provide a way to appeal. It is ironic the company starting the false positive initiative with Microsoft is the worst offender in creating false positives.
You may be able to get around the issue by supplying your site's URL to "Google Webmaster Tools". You don't even have to supply a URL for every single "malicious" file; an overall, top-level URL for your site (or, for your little corner of Blogger.com) seems to be adequate.
If you've got a Google account, just log in and go to this URL. There's a prominent textbox with an "Add Site" button next to it that does the trick. This worked for me, in a matter of minutes (and I don't have a "certificate", other than the one I got for winning a raft race in Pre-K).
Oh, and I too have experience working in heuristics, as part of my degree. "Heuristics" are really just what ordinary, unpretentious people call "rules of thumb"!
It may be that Chrome is using heuristic analysis, to determine that this file is "malicious". That is to say, it is basically saying "Because this file possesses these qualities, we therefore believe this file to be malicious".
Given that a few years ago, someone got hold of a root certificate authority, and proceeded to make genuine security certificates (so that people wouldn't be suspicious, and because they were actually genuine, browsers did not notify the user), for their sites which asked for personal data (bank username and password, etc), and stole it, until that authority was annulled a few days later.
Therefore, simply having an .exe with a certificate (a genuine one, which of course, you have), won't suffice, in Chrome's mind, for the above two reasons.
I'm sorry I can't tell you how to get rid (or at least alleviate somewhat) this issue, but I thought it'd be helpful for you to have some possible reasons as to why this is occurring.
**EDIT: Sources to back up my claims: http://news.techworld.com/security/3266817/online-fraudsters-issue-fake-security-certificates-for-google-yahoo/
http://www.bbc.co.uk/news/technology-14819257**
I also have experience working in heuristics, as part of my programming degree.
I have a page that is just a non interactive display for a shop window.
Obviously, I don't link to it, and I'd also like to avoid people stumbling across it (by Google etc).
It will always be powered by Chrome.
I have thought of...
Checking User Agent for Chrome
Ensuring resolution is 1920 x 1080 (not that useful as it is a client side check)
Banning under robots.txt to keep Google out of it
Do you have any more suggestions?
Should I not really worry about it?
Not that I would EVER recommend what I'm about to suggest - how about filtering by IP address. Since you provider IP is rarely going to change you can use Javascript to kick out or deny requests from IP addresses other than yours. Maybe a clean redirect to http://www.google.com or something silly like that. Although I would still suggest locking it down with a login and password and just have it write a never expiring cookie. That's still not a great idea but a shy bit better than the road your trucking down right now.
You could always limit the connections by IP address (If you know it ahead of time/it's reliable):
Apache's access control
If it is just for a shop window, do you even need access to a web page?
You can host the file locally.
Personally, I wouldn't worry about it, if no-one is linking to it externally it is unlikely to ever be found by search engines.