<?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 Csaba Maulis on Medium]]></title>
        <description><![CDATA[Stories by Csaba Maulis on Medium]]></description>
        <link>https://medium.com/@senki?source=rss-102853bc6a07------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*krEjMziEFJ9_7z84.png</url>
            <title>Stories by Csaba Maulis on Medium</title>
            <link>https://medium.com/@senki?source=rss-102853bc6a07------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:35:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@senki/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[A method for updating Laravel]]></title>
            <link>https://medium.com/@senki/a-method-for-updating-laravel-9f347618bcc0?source=rss-102853bc6a07------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f347618bcc0</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Csaba Maulis]]></dc:creator>
            <pubDate>Wed, 10 May 2017 04:42:12 GMT</pubDate>
            <atom:updated>2017-05-10T04:47:10.398Z</atom:updated>
            <content:encoded><![CDATA[<p>Laravel 5.4.22 available since <a href="https://medium.com/laravel-announcements/important-security-upgrade-f00e0f7c72d5">yesterday</a>. It contains an important security update, and that why I’m thinking about the to update my work-in-progress project to the latest patch release. But what is the best method to accomplish this? I googled, but no relevant information came up.</p><h3>Update vs Upgrade</h3><p>I like to distinguish the difference between processing a minor or a major release changes. I prefer to use ‘update’ as applying a minor change (i.e. patch release) and ‘upgrade’ as applying a major change. Although the upgrade processes very well documented in <a href="https://laravel.com/docs/5.4/upgrade">Laravel</a>, almost no information about what the preferred method to update.</p><p>The Best advice I found in somewhere the <a href="https://laracast.com/">laracast.com</a> forum that all you have to do to change the ‘composer.json’ and run composer update. This is tricky because the laravel new blog command creates many files, not just that one. So if I just modify one file, there is a chance my app is out of sync.</p><h3>Past</h3><pre>$ laravel new blog<br>[...]<br>Application ready! Build something amazing.<br>$ cd blog<br>$ git init<br>Initialized empty Git repository in ~/blog/.git/<br>$ git add --all<br>$ git commit -m &quot;Install Laravel Framework 5.4.14&quot;<br>[...]</pre><p>Usually, this is the sequence I follow when I create a new project. Sometimes the development is long enough to Laravel introduce a patch release while I still work in on it. It makes sense to update the framework. But how do I do that?</p><p>Yes, I can type an another laravel new blog-2 command and compare the changes.</p><p><strong>I did that.</strong></p><pre>$ laravel new blog-2<br>$ kdiff3  ~/blog/ ~/blog-2/</pre><p>I usually use <a href="http://kdiff3.sourceforge.net/">Kdiff3</a>, but even with an advanced merge tool, this needs a lot of manual works. Compare and merge by hand every changed file one by one.</p><p>It works. Thank you, but no thank you.</p><h3>Present</h3><p>My habit is to initialise ‘git’ for every project. Can I use that to track the Laravel changes? Fortunately the laravel command basically downloads the <a href="https://github.com/laravel/laravel">laravel/laravel</a> package. Unfortunatelly this is not exactly true, see in the <a href="https://github.com/laravel/installer">laravel/installer</a> package relevant <a href="https://github.com/laravel/installer/blob/master/src/NewCommand.php#L117">source code</a>, but we can use it as a wery good reference.</p><p>So let’s include it in our project.</p><pre>$$ laravel new blog<br>[...]<br>$ cd blog<br>$ git init<br>[...]<br>$ git add --all<br>$ git commit -m &quot;Install Laravel Framework 5.4.15&quot;<br>git remote add -t master --no-tags upstream <a href="https://github.com/laravel/laravel.git">https://github.com/laravel/laravel.git</a><br>$ git fetch upstream<br>[sometimes later]<br>$ git merge --allow-unrelated-histories 2c6d764</pre><p>Right now I have two issue here:</p><ol><li>The laravel/laravel package is couple of days behind of the <a href="https://github.com/laravel/framework">laravel/framework</a> or the laravel/installer package</li><li>Because I do not want all the laravel/laravel tags in my repository (see the --no-tags option above), I need to search the commit hash every time.</li></ol><p>But the system is working well for me.</p><h3>Wrapping Up</h3><p>Here is a very simple shell script that does all the initial work for me.</p><p>Usage: laravel-new.sh blog</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4b21c9d157747daf66df6288683f3aa/href">https://medium.com/media/e4b21c9d157747daf66df6288683f3aa/href</a></iframe><h3>Future</h3><p>I’m thinking about extending the laravel/installer package with new options.</p><ul><li>In the intialisation time we could have --with-git-upstream option, that would run all the git commands to setup the upstream. Eg. laravel new blog --with-git-upstream</li><li>Even we can create a update subcommand too. That would merge the latest patch for me. Eg. laravel update blog</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f347618bcc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Realtime Check of Password Pages (RCP)]]></title>
            <link>https://medium.com/@senki/realtime-check-of-password-pages-rcp-36f8ecca083f?source=rss-102853bc6a07------2</link>
            <guid isPermaLink="false">https://medium.com/p/36f8ecca083f</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Csaba Maulis]]></dc:creator>
            <pubDate>Thu, 25 Aug 2016 05:26:03 GMT</pubDate>
            <atom:updated>2016-08-25T05:26:03.016Z</atom:updated>
            <content:encoded><![CDATA[<p>I have an idea. This came after I saw a tweet from <a href="http://twitter.com/SwiftOnSecurity">@SwiftOnSecurity</a>:</p><h3>SwiftOnSecurity on Twitter</h3><p>Look at this. It&#39;s devastatingly good. This is the perfection of deception that spearphishing can achieve.https://twitter.com/andreasklinger/status/767788697408327682 ...</p><p>We definitely need login page check in our browsers.</p><h3>The Idea</h3><p>Built-in or plugin based login page check in browsers. There are checks for valid URLS.</p><h4>How is this works?</h4><ol><li>The user enters any page.</li><li>Browser checks three things:<br> • Have password field<br> • Have form<br> • URL is secure</li><li>If so, the browser checks the RCP database, sends <br> • the URL<br> • the page certificate</li><li>Response from server: <br> • whitelisted<br> • blacklisted (confirmed or community)<br> • wrong CERT<br> • unknown<br> • and the response TTL</li><li>Based on user preferences, the browser notifies the user and disables the access to the form</li></ol><p>What happens on non-secure login pages? See below.</p><h4>User settings</h4><p>Obviously, there is need a “security level” type configuration what level of protection user is required:</p><ul><li>whitelist only</li><li>blacklist only</li></ul><p>Also, there is a setting need to Browser action</p><ul><li>warning</li><li>disable the form</li><li>etc</li></ul><p>Because the server can respond a community recommended blacklist, there is needed an option for include or not.</p><p>For unsecured forms, maybe there is an option where the user can protect non-secure forms.</p><ul><li>If disabled, the browser always warns there a connection not secure</li><li>If enabled the browser still warns about connection, but handle it locally to build a local DB of password contained pages. So subsequent requests subtle or disables the warning</li></ul><h4>Behaviour of the Browser</h4><p>Browsers can disable the form, display a warning message, such as display an icon (broken key on the URL bar for example). On whitelisted sites, there is not need any action.</p><h4>Behaviour of the Server</h4><p>The server only does one thing:<br>Search his databases for requested URLs, checks the matching Certificate and respond accordingly.</p><h3>Server Management</h3><h4>Blacklist</h4><ul><li>anybody can send a bogus/malicious page</li><li>Already whitelisted pages automatically rejected, see Dispute</li><li>The community vote, if enough vote — let’s say 1% — its introduced as `blacklisted-community`</li><li>if vote increases — maybe 25% — , the server staff decide to add as `blacklisted-confirmed`</li></ul><h4>Whitelist</h4><ol><li>Web page operator request</li><li>The server staff connects to the web page owners, check the web page itself</li><li>Staff check the identity of page owners</li><li>If everything is all right, then insert as `whitelist` to the database</li></ol><h4>Dispute</h4><p>There is also need to solve occasional problems such as</p><ul><li>Community mark page was not authentic but web page owner complain.</li><li>The page was marked as `whitelist`, but someone else is claiming it is bogus.</li></ul><h4>Further consideration</h4><ul><li>Obviously, the communication needs to be straightforward and secure, e.g. REST over HTTPS</li><li>Due to the nature of the volume of this type of requests, maybe it is a good idea to implement as a distributed service. Servers can communicate each other like DNSSEC</li></ul><h3>Conclusion and Disclosure</h3><p>I am a lone man, and I just scratching the surface of the Infosec field. That is why I try to avoid all the development details, technical consideration, or organisation requirements in this post. Moreover, it is clear to me there is two important factor for this type of service</p><ol><li>How light, fast and secure (confidentiality, integrity, and availability) the implementation</li><li>How trustworthy and rapid is the server operating organisation</li></ol><p>For now, there is just an idea. Is it worthy of consideration?</p><p>Time will tell.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36f8ecca083f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chasing a Xenial]]></title>
            <link>https://medium.com/@senki/chasing-a-xenial-45ff97610fbd?source=rss-102853bc6a07------2</link>
            <guid isPermaLink="false">https://medium.com/p/45ff97610fbd</guid>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[virtualbox]]></category>
            <category><![CDATA[vagrant]]></category>
            <category><![CDATA[xenial]]></category>
            <dc:creator><![CDATA[Csaba Maulis]]></dc:creator>
            <pubDate>Thu, 11 Aug 2016 05:45:25 GMT</pubDate>
            <atom:updated>2016-08-11T05:45:25.697Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fbasofea2UEs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dbasofea2UEs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fbasofea2UEs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d7728692041db0efd49d2304ae3ff70/href">https://medium.com/media/4d7728692041db0efd49d2304ae3ff70/href</a></iframe><h3>Chasing a Xenial</h3><h4>A log from an adventure</h4><p>On 08/08/2016 I found an article about LTS support dates of Ubuntu. You know I’m lazy, I use Ubuntu in a few of my web pages (calling work). I went to check the <a href="https://wiki.ubuntu.com/Releases">Releases</a> page, and I was confused. What is the meaning of the <em>HWE August 2016</em> in Ubuntu 14.04.4 LTS line? I’m out of time, and a least one of my server is EOL?</p><p>Forget about a fact for a second I just misread my `lsb_release -a` command. Wich is said ”Ubuntu <strong>14.04.5</strong> LTS”.</p><p>So, I decided to test and upgrade to the new shiny-winy Xenial. Which is available from only a day earlier, and my MOTD kindly reminded me.</p><blockquote>New release ’16.04.1 LTS’ available.<br>Run ‘do-release-upgrade’ to upgrade to it.</blockquote><p>I have a virtual environment on my computer for testing and developing. Which is a <a href="https://www.vagrantup.com/">Vagrant</a> machine, powered by VirtualBox (very poorly if you want to develop web pages which are the whole point. I’m looking at you <a href="https://www.virtualbox.org/search?q=sendfile&amp;noquickjump=1&amp;ticket=on">sendfile</a>).</p><h3>Moving on</h3><p>Fired up my terminal, promptly typed `v box add ubuntu/xenial64` modified my `Vagrantfile` and waited. Eeeeek. Doesn’t seem to work. Ok, let google it -&gt; turns out there is a <a href="https://bugs.launchpad.net/cloud-images/+bug/1565985">bug #1</a>. Ok, so I could not test my application easily. No worries, I can upgrade to Xenial anytime, a little time-consuming compared to a simple download of a new image, but doable.</p><h4>Let’s try.</h4><p>I just opened my Trusty and started the upgrade. But no so harsh, let’s test the upgrade process first:</p><p>`sudo do-release-upgrade -s`</p><blockquote>Sandbox setup failed<br>It was not possible to create the sandbox environment.<br>Preparing the upgrade failed</blockquote><p><strong>What?</strong></p><p>It turns out there is no `aufs` support in `ubuntu/trusty64` Vagrant box. A quick search (again) there is a <a href="http://askubuntu.com/a/73529">solution</a>. Did I mention I’m lazy? I just copied the whole `sudo apt-get install aufs-tools linux-image-extra-virtual` line, restarted my box and started again: `sudo do-release-upgrade -s`. Now, the whole process seems to work.</p><h3>Intermezzo</h3><ul><li>Along with the road of the update process, there is a warning about `ssh` connection. I decided to ignore it. On my machine, I can fire up the VirtualBox, and access my Vagrant box console. But the reality of any VPS update that you have to use ssh to access. So let’s see there is any problem (turns out at the end, there is no problem, I already using Xenial supported chipper in my ssh config).</li><li>From the nowhere, the phpMyAdmin asked me what is the hostname of the MySQL server. I don’t remember this type of question when any time I install a phpMyAdmin on a box wich has a MySQL server on it. The config script just doesn’t search for local MySQL instances anymore? Who knows?</li><li>And there was a second question about chef’s server URL too. Did I have chef? What was it? Google it again, and now I remember. It is a Vagrant supported provision method (from my point of view), so it is logical to installed already. I decided to ignore the question and left the server field empty.</li></ul><h3>Back to track</h3><p>On the end of the upgrade script, another error waits for me.</p><blockquote>Errors were encountered while processing:<br>grub-pc</blockquote><p>Another bug? Yes, it is. A <a href="https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1314350">bug #2</a>. OK, I sandboxed an update for a test reason, in a test environment. Did I seems too cautious? Maybe. Let’s carry on. I can always recreate my box if anything goes wrong.</p><h3>Another intermezzo</h3><p>Let’s face it. Release upgrade is a time, disk and memory consuming process. But I not expected to fail because of low memory. My Vagrant box has allocated 1024 MB, `v.memory = 1024` in my Vagrantfile, but it is simply not enough. This is odd. I checked the <a href="https://help.ubuntu.com/lts/installation-guide/amd64/ch03s04.html">requirements</a> before starting. So increase to 2048 MB and start again.</p><h3>Are we there yet?</h3><p>So the upgrade is completed, you should not restart the box, obviously this is a very nature of sandboxing. Eventually, can I start testing my app? Please?</p><p><strong>Nope.</strong></p><p>The shared folders just stop working. My app is not on my machine anymore. Bummer. Makes sense to need a restart to the new VirtualBox addition to work, but still.</p><p>So I could not test with this. Let’s try again the upgrade for real. Just `vagrant destroy -f &amp;&amp; vagrant up &amp;&amp; vagrant ssh` and a couple of minutes later‚ I can start the upgrade process. Again.</p><p>`sudo do-release-upgrade`</p><p>After a while, I had a freshly updated Xenial on my box. Restart. It was not booted. What happened? You guess. Another <a href="https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1546108">bug #3</a>…</p><h3>This is the end…</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fopen.spotify.com%2Fembed%2Ftrack%2F5UgT7w6zVZjP3oyawMzbiK%3Futm_source%3Doembed&amp;display_name=Spotify&amp;url=https%3A%2F%2Fopen.spotify.com%2Ftrack%2F5UgT7w6zVZjP3oyawMzbiK&amp;image=https%3A%2F%2Fimage-cdn-ak.spotifycdn.com%2Fimage%2Fab67616d00001e025b96a8c5d61be8878452f8f1&amp;type=text%2Fhtml&amp;schema=spotify" width="456" height="152" frameborder="0" scrolling="no"><a href="https://medium.com/media/222efbe23e8ef79fba5c3853dcd6dbb9/href">https://medium.com/media/222efbe23e8ef79fba5c3853dcd6dbb9/href</a></iframe><p>After a couple of hours of wasting time (a whole day actually) in my current environment, I couldn’t test my app in Xenial. I never upgrade any of my servers without testing, so no luck to actually enjoying the speed of PHP 7 and HTTP/2 altogether right now. It is simply not reliably available on Trusty (this is not a complaint). So I desperately waiting for 11/8/2016 (which is today) to test a freshly released <a href="https://launchpad.net/cloud-images/+milestone/y-2016-08-11">cloud-images y-2016–08–11 “y-2016–08–11”</a></p><blockquote>Now I have a launchctl script, which tries in every hour `vagrant box outdated`.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45ff97610fbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>