<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.baszerr.eu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>BaSzErr - blog:2016:05:04</title>
        <description></description>
        <link>https://www.baszerr.eu/</link>
        <lastBuildDate>Wed, 06 May 2026 11:14:22 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://www.baszerr.eu/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
            <title>BaSzErr</title>
            <link>https://www.baszerr.eu/</link>
        </image>
        <item>
            <title>secure_contactless_payment</title>
            <link>https://www.baszerr.eu/doku.php?id=blog:2016:05:04:secure_contactless_payment</link>
            <description>
&lt;h1 class=&quot;sectionedit1&quot; id=&quot;secure_contactless_payment&quot;&gt;2016-05-04 - secure contactless payment?&lt;/h1&gt;
&lt;div class=&quot;level1&quot;&gt;

&lt;p&gt;
&lt;a href=&quot;https://www.baszerr.eu/lib/exe/detail.php?id=blog%3A2016%3A05%3A04%3Asecure_contactless_payment&amp;amp;media=blog:2016:05:04:universal_contactless_card_symbol.png&quot; class=&quot;media&quot; title=&quot;blog:2016:05:04:universal_contactless_card_symbol.png&quot;&gt;&lt;img src=&quot;https://www.baszerr.eu/lib/exe/fetch.php?w=300&amp;amp;tok=eee564&amp;amp;media=blog:2016:05:04:universal_contactless_card_symbol.png&quot; class=&quot;mediaright&quot; align=&quot;right&quot; loading=&quot;lazy&quot; title=&quot;contactless card symbol (from wikipedia)&quot; alt=&quot;contactless card symbol (from wikipedia)&quot; width=&quot;300&quot; /&gt;&lt;/a&gt;
&lt;/p&gt;

&lt;p&gt;
&lt;a href=&quot;https://en.wikipedia.org/wiki/contactless payment&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/contactless payment&quot;&gt;contactless payment&lt;/a&gt; is a neat idea. unfortunately it is not very secure (&lt;a href=&quot;https://niebezpiecznik.pl/post/klonowanie-zblizeniowych-kart-kredytowych-rfid/&quot; class=&quot;urlextern&quot; title=&quot;https://niebezpiecznik.pl/post/klonowanie-zblizeniowych-kart-kredytowych-rfid/&quot; rel=&quot;ugc nofollow&quot;&gt;1&lt;/a&gt; &lt;a href=&quot;https://niebezpiecznik.pl/post/ataki-na-zblizeniowe-karty-kredytowe-rfid/&quot; class=&quot;urlextern&quot; title=&quot;https://niebezpiecznik.pl/post/ataki-na-zblizeniowe-karty-kredytowe-rfid/&quot; rel=&quot;ugc nofollow&quot;&gt;2&lt;/a&gt; &lt;a href=&quot;https://niebezpiecznik.pl/post/uniwersalny-atak-na-karty-zblizeniowe/&quot; class=&quot;urlextern&quot; title=&quot;https://niebezpiecznik.pl/post/uniwersalny-atak-na-karty-zblizeniowe/&quot; rel=&quot;ugc nofollow&quot;&gt;3&lt;/a&gt; – to name some of the issues). the main problem is that the card itself is able to allow payment w/o any interaction. how about adding one?
&lt;/p&gt;

&lt;p&gt;
of course it cannot be PIN code, as the main idea was to eliminate it for “small payments”. instead card could have a sort of a small contact fields, that one would need to touch, in order to accept payment. from user&amp;#039;s PoV it would only mean to keep card by a selected corner (say: with contacts on top and bottom). w/o closing the loop, payment would not get accepted. this way &lt;a href=&quot;https://niebezpiecznik.pl/post/uniwersalny-atak-na-karty-zblizeniowe/&quot; class=&quot;urlextern&quot; title=&quot;https://niebezpiecznik.pl/post/uniwersalny-atak-na-karty-zblizeniowe/&quot; rel=&quot;ugc nofollow&quot;&gt;universal, remote attack&lt;/a&gt; becomes useless, as thief would have to have a physical access to a card first.
&lt;/p&gt;

&lt;p&gt;
there is still one more problem – physical card&amp;#039;s theft. thief can obviously close the loop manually, thus making a payment. this still gets problematic when &lt;a href=&quot;https://niebezpiecznik.pl/post/okradli-go-przez-karty-zblizeniowe-a-banki-nie-chca-oddac-pieniedzy/&quot; class=&quot;urlextern&quot; title=&quot;https://niebezpiecznik.pl/post/okradli-go-przez-karty-zblizeniowe-a-banki-nie-chca-oddac-pieniedzy/&quot; rel=&quot;ugc nofollow&quot;&gt;trying to get your money back&lt;/a&gt; after being robbed. unfortunately circumventing this is a bit more tricky, as event “simple” biometry like fingerprints will not do, since you often touch your card with your fingertips, thus thief can try reconstructing these, base on prints you left.
&lt;/p&gt;

&lt;p&gt;
for now – better safe than sorry. just disable the contactless payment method in your bank (one call to info line + using a ATM twice in my case) and sleep tight. :)
&lt;/p&gt;

&lt;/div&gt;
</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 15 Jun 2021 20:09:22 +0000</pubDate>
        </item>
        <item>
            <title>sys_sw_snapshot</title>
            <link>https://www.baszerr.eu/doku.php?id=blog:2016:05:04:sys_sw_snapshot</link>
            <description>
&lt;h1 class=&quot;sectionedit1&quot; id=&quot;sys_sw_snapshot&quot;&gt;2016-05-04 - sys SW snapshot&lt;/h1&gt;
&lt;div class=&quot;level1&quot;&gt;

&lt;p&gt;
modern &lt;a href=&quot;https://en.wikipedia.org/wiki/radeon&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/radeon&quot;&gt;radeon&lt;/a&gt; GP/GPUs are really good in terms of both performance and price/performance. unfortunately &lt;a href=&quot;https://en.wikipedia.org/wiki/AMD&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/AMD&quot;&gt;AMD&lt;/a&gt; constantly fails to provide up-to-date &lt;a href=&quot;https://en.wikipedia.org/wiki/Fglrx#Linux&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/Fglrx#Linux&quot;&gt;fglrx driver&lt;/a&gt;. even though &lt;a href=&quot;https://en.wikipedia.org/wiki/Free_and_open-source_graphics_device_driver#.2Fdrivers.2Fgpu.2Fdrm.2Famd.2Famdgpu&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/Free_and_open-source_graphics_device_driver#.2Fdrivers.2Fgpu.2Fdrm.2Famd.2Famdgpu&quot;&gt;this will most likely change with amdgpu&lt;/a&gt; driver, as it goes highly open-source… my card is not that new, so i won&amp;#039;t get support from there either. no luck this time either.
&lt;/p&gt;

&lt;p&gt;
the problem is that when &lt;a href=&quot;https://en.wikipedia.org/wiki/X11&quot; class=&quot;interwiki iw_wp&quot; title=&quot;https://en.wikipedia.org/wiki/X11&quot;&gt;X11&lt;/a&gt; ABI changes, fglrx usually lags behind for a few months, before compatible binary gets released. until then quite a few updates got blocked.
&lt;/p&gt;

&lt;p&gt;
there is one more problem – human factor. i update my system very often. since i need to &lt;strong&gt;remember&lt;/strong&gt;, that proper driver is not there and i should not install X11 updates until new driver is provided, it&amp;#039;s just a matter of time until i make a mistake and have hours-long fun of restoring all necessary packages (and their dependencies!) back to “compatible” version, so that my video driver is happy again. after doing this twice i decided to automate this a little, with two little shell scripts:
&lt;/p&gt;
&lt;ul&gt;
&lt;li class=&quot;level1&quot;&gt;&lt;div class=&quot;li&quot;&gt; &lt;a href=&quot;https://www.baszerr.eu/lib/exe/fetch.php?media=blog:2016:05:04:make_sys_snapshot.gz&quot; class=&quot;media mediafile mf_gz&quot; title=&quot;blog:2016:05:04:make_sys_snapshot.gz (355 B)&quot;&gt;make_sys_snapshot&lt;/a&gt; – writes down list of currently installed packages and their versions&lt;/div&gt;
&lt;/li&gt;
&lt;li class=&quot;level1&quot;&gt;&lt;div class=&quot;li&quot;&gt; &lt;a href=&quot;https://www.baszerr.eu/lib/exe/fetch.php?media=blog:2016:05:04:restore_sys_snapshot.gz&quot; class=&quot;media mediafile mf_gz&quot; title=&quot;blog:2016:05:04:restore_sys_snapshot.gz (1.1 KB)&quot;&gt;restore_sys_snapshot&lt;/a&gt; – script for doing the actual magic. :)&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
once system gets accidentally updated, all i need to do is to call the “restore” script and provide it with a date/time of a snapshot to restore to.
&lt;/p&gt;

&lt;p&gt;
there are two “buts” to make this work:
&lt;/p&gt;
&lt;ul&gt;
&lt;li class=&quot;level1&quot;&gt;&lt;div class=&quot;li&quot;&gt; run “snapshot” script along with an update (another script in my case – so no problem here)&lt;/div&gt;
&lt;/li&gt;
&lt;li class=&quot;level1&quot;&gt;&lt;div class=&quot;li&quot;&gt; make sure not to remove apt-get archives (this could be improved, by just downloading needed packages, when missing)&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;
scripts are not high quality, but they seem to do the work for now.
&lt;/p&gt;

&lt;/div&gt;
</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Tue, 15 Jun 2021 20:09:22 +0000</pubDate>
        </item>
    </channel>
</rss>
