<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Abhishek Thomas on Medium]]></title>
        <description><![CDATA[Stories by Abhishek Thomas on Medium]]></description>
        <link>https://medium.com/@abhishekthoms?source=rss-d8f2bc66f782------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bwbShXeWYliDqTax.jpg</url>
            <title>Stories by Abhishek Thomas on Medium</title>
            <link>https://medium.com/@abhishekthoms?source=rss-d8f2bc66f782------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:05:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhishekthoms/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Demystifying Tor]]></title>
            <link>https://abhishekthoms.medium.com/demystifying-tor-470603201f32?source=rss-d8f2bc66f782------2</link>
            <guid isPermaLink="false">https://medium.com/p/470603201f32</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[browsers]]></category>
            <category><![CDATA[tor]]></category>
            <dc:creator><![CDATA[Abhishek Thomas]]></dc:creator>
            <pubDate>Sat, 05 Jul 2025 16:26:54 GMT</pubDate>
            <atom:updated>2025-07-05T16:26:54.162Z</atom:updated>
            <content:encoded><![CDATA[<p>Anonymity is not something that most people surfing the internet are concerned about. I always knew there was this browser that turns you into a digital ninja but never really understood how.</p><h3>Incognito, but for real — How?</h3><p>While i was trying to understand Tor, i was curious about other ways you can be anonymous on the internet. Here are some potential candidates:</p><ul><li>VPN — It kinda does the job but your VPN provider knows what you are upto</li><li>Tails OS — This is a portable operating system that internally uses Tor, hence disqualified</li><li>Internet Cafe?? — Little extra physical effort but it will do the trick</li></ul><p>There were some others that popped up in my search like Freenet, I2P, VPN chaining. Feel free to go in depth about these if you like</p><h3>What is Tor?</h3><ul><li>Stands for — The onion router</li><li>It is an implementation of the onion routing that helps in anonymizing network traffic</li></ul><h3>Seems simple enough, But what is Onion Routing?</h3><p>In a nutshell ( <strong>if you want detailed version please scroll a bit more </strong>), onion routing uses multiple relay nodes between you and the internet to ensure that no one in the middle has any idea who you are and what you are trying to do.</p><p><strong>Tor Implementation:</strong></p><p>The Tor client chooses 3 different Tor relay nodes to route traffic through. It sets up a connection with each relay node to build a circuit. It also shares some private symmetric keys with them.</p><p>Then each message the client sends is encrypted by all 3 keys, in the order that makes sense ( please guess ). Each relay nodes decrypts one layer of encryption and forwards it to the next node ( hence the name “Onion” ). The final node decrypts the final layer of encryption and sees that it needs to hit <a href="https://blogs.mtdv.me/J5XmEn4CAw">https://blogs.mtdv.me/J5XmEn4CAw</a>. It forwards it to the website. Whatever request it gets back, it encrypts it again with the symmetric key it has and forwards it back in the same order to the client via the relay nodes. The Tor client then decrypts the message 3 times and can finally serve you whatever you requested for</p><h3>Now there were a bunch of questions in my mind when i learned about this</h3><ol><li>If i want to browse a website that requires me to login, does it not make Tor useless? — Yes, it does</li><li>Wouldn’t this make browsing slower? — Definitely</li><li>Can i use a VPN along with this ?— Depends. If you use the VPN before the TOR network, then it does not make sense and defeats the purpose. Your VPN provider can know what you are upto. If you use VPN after the tor network ( painful to create &amp; manage apparently ) then it continues to not make sense but atleast the website will not figure out you are using Tor ( Your VPN potentially could )</li><li>Where does DNS get resolved for the website you are accessing ?— In the Exit node</li><li>Does Tor use some secret network or do the message go through the internet? — The circuit is part of the internet. The anonymity comes from the fact that your messages are encrypted and are getting routed through public servers multiple times to ensure no one can find the source and destination</li></ol><h3>Onion Routing [Much Details]</h3><blockquote>Disclaimer: Below is how Tor implements onion routing, there could be other implementations</blockquote><p><strong>What is a relay node?</strong></p><p>Nothing special, it is just a server on the internet that volunteers to be part of the Tor circuit, it decrypts messages it receives and passes it to the next node. You will need a Tor relay software running in that server to be one, once you install this, Tor will add you as a relay node to a signed directory.</p><p><strong>Finding relay nodes</strong></p><p>The Tor client needs details about the relay nodes to create a circuit. It gets this from a signed directory which contains details ( IP, port, etc ) about the relay nodes. These directory documents are signed by directory authority servers which are maintained by Tor. This data is signed by the directory authority server’s private keys so the Tor client can verify authenticity using their public keys.</p><p><strong>Creating a Circuit</strong></p><p>Tor client arbitrarily chooses 3 nodes from the fresh list of relay nodes it has just received from the Directory Authority. Guard Node, Relay Node &amp; Exit Node. Now it proceeds to build a circuit to the internet via these nodes.</p><ol><li>The Tor clients sends a CREATE message to the Guard node, along with some key exchange parameters. The Guard node receives this, creates shared symmetric keys ( key_forward, key_backward ) using the parameters that the Tor client sent. It uses a version of Diffie-Helmen ( NTor ) + key derivation function to create these keys. The Guard node then returns a CREATED message along with some key exchange parameters. The Client then is able to create the shared symmetric keys using the parameters sent. This establishes the first connection in the circuit.</li><li>Once the initial connecting is established, the client encrypts an EXTEND message which also has details of the relay node and sends it to the Guard node ( again along with parameters for key exchange ). The Guard node decrypts this and understands that it needs to extend the circuit and sends a CREATE message to the Relay node. The relay node does what the guard node did previously and sends back CREATED to the Guard node along with some key exchange parameters, which the guard node sends to the Tor Client. At this point we have Client -&gt; Guard -&gt; Relay connection setup and client has shared symmetric keys with each node.</li><li>Now a similar Encryption + EXTEND is used to extend the circuit to the Exit node. Now we have Client -&gt; Guard -&gt; Relay -&gt; Exit.</li></ol><p><strong>Sending Messages</strong></p><p>Once the circuit is ready, the client encrypts the message it wants to send using the all 3 key_forward keys. It sends it through the circuit via the nodes. It is decrypted layer by layer by each node until it makes sense. When it makes sense, the node which it makes sense to ( Exit node ) does what the message says — Lets say, fetch some website content</p><p><strong>Reading Messages</strong></p><p>Once the website responds, the Exit node encrypts the data with the key_backward key. The Relay &amp; Guard node follow suit before sending it to the client. Now the client peels back the layers ( Onion Pun, hehe ) using the different keys it has and can serve the website to the user.</p><p><strong>How exactly is it Anonymous</strong></p><ul><li>Guard Node — Knows that its you who is trying to access the internet, but has no idea what you are trying to access</li><li>Relay Node — Knows only the previous and next node’s IP and Port, It mostly just forwards encrypted gibberish both ways</li><li>Exit Node — Can potentially see all the websites that are being accessed, but cannot determine who is accessing what website</li></ul><h3>Tor Hidden services</h3><p>Now i have not gone in depth about this, but here is a very overall explanation about what these are:</p><p>Up until now we have seen how you can access public websites surreptitiously. Now what if you want to access a website that cannot be accessed via the internet? Enter <strong><em>Tor Hidden services</em></strong></p><p><strong>What are these hidden services?</strong></p><p>There are services that are not public and don’t want to be accessed via the public internet. They can only be accessed via the Tor network. To become a hidden service, you need to do the following</p><ul><li>Have a server</li><li>Choose a few Tor Relay nodes as your Introduction Points (IPs)</li><li>Build Tor circuits to these relays and tell them to forward introduction requests to your server</li><li>Upload service descriptors to HSdir ( Hidden services directory ) which contains your onion address and your IPs details</li></ul><p>Most of the above is done by the Tor software itself if configured to act as a hidden service</p><p><strong>How does connection to these hidden services happen ?</strong></p><p>You need to first know the onion address of the website you are trying to access. Lets say you want to access “abc.onion”. Now your Tor client will access the HSdir to get the details about the Introduction Points (IPs) of the hidden service. Then the Tor client will choose a random relay node and create a circuit to it. This would be the Rendezvous Point (RP). Then it sends a message to one of the IPs with the details of the RP, asking to connect to the hidden service. The IP forwards this to the hidden service via the circuit that the hidden service has built to it. The hidden service decides if it wants to allow the client to access it. If yes, it creates a circuit to the rendezvous point that the client message had. Then the rendezvous point just acts as a middleman between the client and the hidden service</p><h3>References</h3><ul><li><a href="https://spec.torproject.org/intro/index.html">https://spec.torproject.org/intro/index.html</a></li><li><a href="https://www.youtube.com/watch?v=QRYzre4bf7I">https://www.youtube.com/watch?v=QRYzre4bf7I</a></li><li><a href="https://www.youtube.com/watch?v=lVcbq_a5N9I">https://www.youtube.com/watch?v=lVcbq_a5N9I</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=470603201f32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Custom Delete Button in react-admin With Custom Notification Message]]></title>
            <link>https://abhishekthoms.medium.com/custom-delete-button-in-react-admin-with-custom-notification-message-3392526cb43c?source=rss-d8f2bc66f782------2</link>
            <guid isPermaLink="false">https://medium.com/p/3392526cb43c</guid>
            <category><![CDATA[custom-notification]]></category>
            <category><![CDATA[custom-delete]]></category>
            <category><![CDATA[react-admin]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Abhishek Thomas]]></dc:creator>
            <pubDate>Sun, 02 May 2021 17:37:29 GMT</pubDate>
            <atom:updated>2021-05-29T09:51:40.952Z</atom:updated>
            <content:encoded><![CDATA[<p>React-admin is a framework built using React, Material UI React, Redux and React Router, to give you an admin framework which you can customize based on your project needs. But like all frameworks, it takes a bit of researching and tweaking to customize some features for which direct customization hooks are not provided by the framework.</p><p>In this very short post, we will be looking at how to create a custom Delete Button, which will have a confirmation popup as well as a custom toast notification after deleting a record.</p><h3>Prerequisites</h3><p>Before Getting into the Custom Delete Button, We will need to setup a basic react-admin project with Create, List and Edit functionality.</p><p>Here is a Great Tutorial on Just how to do that</p><p><a href="https://retool.com/blog/building-an-admin-console-in-react-admin/">Tutorial: building an admin console in react-admin</a></p><p>The above tutorial uses <a href="https://jsonplaceholder.typicode.com/">JsonPlaceholder </a>as a DataProvider backend for it, but you can customize it to fetch data from your own backend.</p><p>Check out the methods react-admin provides to create your own DataProvider below.</p><p><a href="https://marmelab.com/react-admin/DataProviders.html#writing-your-own-data-provider">Data Providers</a></p><h3>Custom Delete Button</h3><p>Now Let us Create a Custom Delete Button Component.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/19efa4803254a30dcd0944fb89ac1d1e/href">https://medium.com/media/19efa4803254a30dcd0944fb89ac1d1e/href</a></iframe><ol><li>First we create a CustomDeleteButton component, with the UI that we require. In our case it is a basic Dialogue with confirmation text, basic delete/cancel buttons and some added styles. You can add any other UI elements you require as well.</li><li>Then we use the Connect method from Redux and pass the method crudDelete from ra-core ( react-admin core components ) using alias dispatchCrudDelete.</li><li>We then use this method dispatchCrudDelete inside our handleDelete function to delete the record.</li><li>The state of class and It’s handler functions are self explanatory.</li></ol><h3>Almost Done…</h3><p>Everything seems perfect, Until you realize that after you delete a record , It gives a toast notification saying ‘Element Deleted’. Now we will look at how to customize this message.</p><p>Looking into the below file, we can easily write our own CustomCrudDelete function</p><p><a href="https://github.com/marmelab/react-admin/blob/master/packages/ra-core/src/actions/dataActions/crudDelete.ts">https://github.com/marmelab/react-admin/blob/master/packages/ra-core/src/actions/dataActions/crudDelete.ts</a></p><p>For this we will be creating our own CustomCrudDelete function, which we were previously importing from ra-core.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0e10933aef7be34fcfed3e8447953a1e/href">https://medium.com/media/0e10933aef7be34fcfed3e8447953a1e/href</a></iframe><p>Now all You have to do is import our CustomCrudDelete function into our CustomDeleteButton file, and use our new method inside our redux connect, instead of using the default crudDelete provided by react-admin.</p><h3>Where do i put this button ?</h3><p>For those of you wondering where to now place our CustomDeleteButton, Below is a small example.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/887ea5fb9f8149da71cc9055121f3b39/href">https://medium.com/media/887ea5fb9f8149da71cc9055121f3b39/href</a></iframe><p>Aaaaand that is it, You now know how to write your own Custom Delete Button on react-admin and show custom toast notifications to the user.</p><p>Hope this helps !!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3392526cb43c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>