<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cookies on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/cookies/</link><description>Recent content in Cookies on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sun, 07 May 2023 19:47:38 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/cookies/index.xml" rel="self" type="application/rss+xml"/><item><title>Consent-O-Matic: Extensión de navegador que rellena automáticamente las ventanas emergentes de cookies en función de tus preferencias</title><link>http://karpoke.ignaciocano.com/2023/05/07/consent-o-matic-extension-de-navegador-que-rellena-automaticamente-las-ventanas/</link><pubDate>Sun, 07 May 2023 19:47:38 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/05/07/consent-o-matic-extension-de-navegador-que-rellena-automaticamente-las-ventanas/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Browser extension that automatically fills out cookie popups based on
your preferences - cavi-au/Consent-O-Matic&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» GitHub | &lt;a href="https://github.com/cavi-au/Consent-O-Matic"&gt;github.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Today's rabbit hole: securing JWTs for authentication, httpOnly cookies, CSRF tokens, secrets &amp; more</title><link>http://karpoke.ignaciocano.com/2020/08/25/today-s-rabbit-hole-securing-jwts-for-authentication-httponly-cookies-csrf-token/</link><pubDate>Tue, 25 Aug 2020 22:04:11 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/08/25/today-s-rabbit-hole-securing-jwts-for-authentication-httponly-cookies-csrf-token/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Note: this is first and foremost the tale of a journey. It acts as a
how-to, but I also want to share&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/petrussola/today-s-rabbit-hole-jwts-in-httponly-cookies-csrf-tokens-secrets-more-1jbp"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>11 Ways To Track Your Moves When Using a Web Browser</title><link>http://karpoke.ignaciocano.com/2015/03/15/11-ways-to-track-your-moves-when-using-a-web-browser/</link><pubDate>Sun, 15 Mar 2015 12:21:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2015/03/15/11-ways-to-track-your-moves-when-using-a-web-browser/</guid><description>&lt;blockquote&gt;
&lt;p&gt;some tracking methods do attempt to track the user over a long time,
and in particular attempt to make it difficult to evade the tracking.
This is sometimes done for advertisement purposes, but can also be
done to stop certain attacks like brute forcing or to identify
attackers that return to a site. In its worst case, from a private
perspective, the tracking is done to follow a user across various web
sites. Over the years, browsers and plugins have provided a number of
ways to restrict this tracking. Here are some of the more common
techniques how tracking is done and how the user can prevent (some of)
it&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Unsafe cookies leave WordPress accounts open to hijacking, 2-factor bypass</title><link>http://karpoke.ignaciocano.com/2014/05/26/unsafe-cookies-leave-wordpress-accounts-open-to-hijacking-2-factor-bypass/</link><pubDate>Mon, 26 May 2014 21:50:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2014/05/26/unsafe-cookies-leave-wordpress-accounts-open-to-hijacking-2-factor-bypass/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Yan Zhu, a staff technologist at the Electronic Frontier Foundation,
came to that determination after noticing that WordPress servers send
a key browser cookie in plain text, rather than encrypting it, as long
mandated by widely accepted security practices. The cookie, which
carries the tag ”wordpress_logged_in,” is set once an end user has
entered a valid WordPress user name and password. It’s the website
equivalent of a plastic bracelets used by nightclubs. Once a browser
presents the cookie, WordPress servers will usher the user behind a
velvet rope to highly privileged sections that reveal private
messages, update some user settings, publish blog posts, and more. The
move by WordPress engineers to allow the cookie to be transmitted
unencrypted makes them susceptible to interception in many cases.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>