<?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 Er Galvao Abbott on Medium]]></title>
        <description><![CDATA[Stories by Er Galvao Abbott on Medium]]></description>
        <link>https://medium.com/@galvao?source=rss-c27f1feba584------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*K4Om2t9GA8QlPZyFVwOmPw.jpeg</url>
            <title>Stories by Er Galvao Abbott on Medium</title>
            <link>https://medium.com/@galvao?source=rss-c27f1feba584------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:39:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@galvao/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[I’m Fedora Ambassador LATAM!]]></title>
            <link>https://medium.com/the-white-hat-elephpant/im-fedora-ambassador-latam-3312ddbb0607?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/3312ddbb0607</guid>
            <category><![CDATA[fedora]]></category>
            <category><![CDATA[fedora-ambassador]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Mon, 27 Nov 2017 09:42:57 GMT</pubDate>
            <atom:updated>2017-11-27T09:42:59.267Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*F63e0U4y6NxcwQED.png" /></figure><p>I’m very proud to announce that last week I’ve officially <a href="https://fedoraproject.org/wiki/User:Galvao">joined the Fedora Project as Ambassador LATAM</a>. It’s no secret I’ve been a fan and advocate for Fedora for a while, and it’s a true honor for me to receive such a title.</p><p>Fedora represents to me the best experience I’ve had with a Linux Distribution. It has an impressively fast package release cycle, while providing a stability far greater than any other similarly fast distros. I’ve never encountered any problems installing any softwares, being in the native RPM format, AppImage or even the good old tar.*.</p><p>Aside from that, Fedora never, ever left me hanging due to a serious bug, which more often than not happens — and happened to me personally — with other fast-paced distros out there. I don’t know if people realize the difficulty involved in merging these two concepts: fast release and stability. It’s a truly impressive feat, and Fedora does it like no other.</p><p>As if all that wasn’t enough, the amazing work that <a href="https://blog.remirepo.net/en">Remi Collet</a> has been doing bringing the most recent PHP versions to Fedora in an impressive pace shows how even more perfect the distro is for a PHP contributor and evangelist as myself.</p><p>Speaking of which, as a web developer in general and particularly a PHP developer, I intend to bring both worlds more close together and present a lot of talks on setting environments, using tools and developing web applications in general while based on this great distribution.</p><p>Long live Linux. Long live the Fedora Project. See you all soon! =)</p><p><em>Originally published at </em><a href="https://www.galvao.eti.br/im-fedora-ambassador-latam/"><em>Er Galvão Abbott</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3312ddbb0607" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-white-hat-elephpant/im-fedora-ambassador-latam-3312ddbb0607">I’m Fedora Ambassador LATAM!</a> was originally published in <a href="https://medium.com/the-white-hat-elephpant">The White Hat ElePHPant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Projeto “k”: Análise de complexidade]]></title>
            <link>https://medium.com/o-elephpant-do-chap%C3%A9u-branco/projeto-k-an%C3%A1lise-de-complexidade-d71b4fb215a7?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/d71b4fb215a7</guid>
            <category><![CDATA[fuck-the-wheel-dogma]]></category>
            <category><![CDATA[projetos]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Sun, 05 Nov 2017 11:29:55 GMT</pubDate>
            <atom:updated>2017-11-05T11:29:57.288Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*9Ynw0LuQlEcOuJgX.png" /></figure><p>A medida que o desenvolvimento do “Projeto k” avança — aos trancos, devido a meus outros compromissos — se torna muito claro o quanto ainda estou longe de uma release alpha. Isso não é surpresa pra mim ou mesmo me desanima: quando iniciei o projeto eu tinha uma boa idéia da complexidade envolvida.</p><p>Ainda assim acho interessante compartilhar a complexidade de cada parte que o projeto envolve, já que esse nível de detalhamento eu ainda não possuia quando comecei a trabalhar. Segue, em ordem do mais simples ao mais complexo, os items envolvidos no desenvolvimento do “k”:</p><ol><li>Infra: Sempre tive um conhecimento de intermediário para avançado da Infra envolvida: Servidor web (Apache) e RDBMS (PostgreSQL). Alie-se isso ao fato de que hoje em dia instalar e configurar essas coisas é trivial e é fácil entender porque a infra é, de longe, a parte mais fácil do projeto.<br> Isso não significa, entretanto, que a infra é simplória: existem algumas configurações específicas (em particular com o Apache) que demandam um pouco de pesquisa e testes.</li><li>Modelagem da Base de Dados: Com a exceção de casos muito específicos, meu conhecimento de Modelagem sempre foi excelente (não é à toa que geralmente tenho uma ótima avaliação quando ministro este conteúdo em cursos). Considero — não sem um pouco de otimismo — que a modelagem da base em cima da qual o “k” vai rodar esteja uns 95% concluída. Esses 5% restantes não estão verdadeiramente faltando, apenas figuram como uma espécie de “gordura” para o caso de eu não ter previsto alguma coisa.<br> Ainda assim, devido ao fato de que outros pontos são de uma complexidade considerável, como vocês verão a seguir, ainda não estou utilizando verdadeiramente a base de dados (este ponto começará, lentamente, a ser implementado em breve).</li><li>Logs: Algo que — desonfio — o mercado criminosamente ignora. Confesso que me surpreendi um pouco com a complexidade de logs que serão usados no “k”, mas devia ter imaginado. Em virtude da complexidade do projeto, mesmo utilizando um exclente componente pra isso (<a href="https://github.com/Seldaek/monolog">Monolog</a>, é claro), os níveis e estruturas envolvidas nos logs de execução, erros, etc… são bem complexos. Isso está aproximadamente 85% definido (já existem correções a fazer) e uns 10% implementado de fato. A boa notícia é que justamnte devido ao Monolog a implementação disso não será muito trabalhosa.</li><li>Fluxo lógico: Mais um ponto que o mercado ignora. Esse eu não desconfio, eu <strong>sei</strong>. Acho absurdo um projeto a partir de uma certa complexidade não possuir um desenho de fluxo (leia-se fluxograma). O “k” possui um fluxograma e sub-fluxogramas. Decidi por trabalhar dessa forma para que seja possível detalhar partes do fluxo sem criar um diagrama monstruoso. Uso o <a href="https://wiki.gnome.org/Apps/Dia/">Dia</a> para isso, um software excelente e mais do que competente para esse tipo de coisa.</li><li>Programação Server-Side (PHP, dã!): Como o “k” trata de algo que não é comum no mercado (uma das razões pelas quais tem sido tão interessante trabalhar nele), às vezes faltam artigos e tutoriais a respeito. Pontos (como sempre) para a <a href="http://php.net/manual/en/">documentação oficial e para os comentários que se encontram por lá</a>. Às vezes, como já aconteceu durante o desenvolvimento do “k”, o código mostrado no comentário é de qualidade duvidosa, mas de um valor imprescindível em termos de “pistas” de como chegar onde eu quero. É muito complicado dar muito mais explicação nesse ponto sem entregar muito sobre o projeto, então por enquanto paro por aqui.</li><li>Programação Client-Side: Absolutamente a parte que será mais complexa para mim. Tenho um conhecimento considerável de HTML, CSS e JavaScript, mas confesso que parei no tempo e esse mercado anda caótico demais para acompanhar de fato. Some-se a isso o fato de que tenho idéias bem interessantes para a interface do “k” e certamente precisarei de ajuda quando chegar nos detalhes mais complexos dessa parte. Por conta de tudo isso, o desenvolvimento Client-Side é de longe a parte menos trabalhada no projeto.<br> Ainda assim não significa que eu não tenha feito nada de interessante. Na realidade fiz um componente JS bem bacana para uma das principais partes da interface (não se animem demais, não é nada inovador, na verdade há dezenas (centenas?) de componentes idênticos ou até mesmo muito melhores por aí).</li></ol><p>Aas decisões mais bacanas que tomei como imutáveis ao iniciar o projeto foram:</p><ul><li>Mesmo em um eventual (e cada vez mais improvável) fracasso, o “k” será divulgado de qualquer maneira, seja para servir de exemplo, <em>cautionary tale</em>, ou como ajuda na parte educacional.</li><li>Falando em educação, <strong>TODO o material</strong> produzido no desenvolvimento (ERD, Fluxogramas, código-fonte, etc, etc, etc…) será disponibilizado como Open Source.</li></ul><p>Segue a luta. Espero poder contar mais em breve =)</p><p><em>Originally published at </em><a href="https://www.galvao.eti.br/projeto-k-analise-de-complexidade/"><em>Er Galvão Abbott</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d71b4fb215a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco/projeto-k-an%C3%A1lise-de-complexidade-d71b4fb215a7">Projeto “k”: Análise de complexidade</a> was originally published in <a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco">O ElePHPant do Chapéu Branco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Projeto “k”: O máximo que posso dizer no momento]]></title>
            <link>https://medium.com/o-elephpant-do-chap%C3%A9u-branco/projeto-k-o-m%C3%A1ximo-que-posso-dizer-no-momento-c78c31a5809a?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/c78c31a5809a</guid>
            <category><![CDATA[projetos]]></category>
            <category><![CDATA[fuck-the-wheel-dogma]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Sat, 02 Sep 2017 15:31:39 GMT</pubDate>
            <atom:updated>2017-09-02T15:31:41.905Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*SsdoGi240OyN3DKP.png" /></figure><p>___k___ é, de longe, o projeto mais ambicioso que já trabalhei na minha vida e isso é animador e assustador ao mesmo tempo. Como ontem atingi uma milestone importantíssima pro projeto muito antes do esperado, decidi comemorar fazendo um post pra contar o máximo que posso sobre ele. Como regra geral decidi fazer sigilo (isso inclui até o nome, que revelo uma letrinha aqui numa brincadeira estilo jogo da forca) sobre o projeto até que:</p><ol><li>Ele seja lançado;</li><li>Ele falhe.</li></ol><p>Seja qual for o resultado vou revelar tudo quando chegar a um desses dois pontos.</p><p>O ___k___ se baseia em HTML, CSS, JavaScript (client-side) e Linux, Apache, PHP e PostgreSQL (server-side). ___k___ está sendo desenvolvido, inicialmente, para rodar no Firefox e terá um daemon que poderá ser agendado via cronjob. Ele poderá, opcionalmente, ser instalado em um servidor e acessado via cliente.</p><p>Estou propositalmente usando o mínimo de componentes, mas ___k___ já gerou <a href="https://www.galvao.eti.br/jhrw-um-wrapper-para-ajax/">um sub-componente</a> e deve gerar pelo menos mais um. ___k___ inclusive deve gerar uma boa evolução do JHRW para que ele finalmente saia do estágio alpha.</p><p>Se o meu otimismo não for infundado (ainda é cedo pra saber) em aproximadamente um a dois meses ___k___ deve estar minimamente utilizável — ainda sem todas as funcionalidades, mas as básicas que seriam, fundamentalmente falando, I/O.</p><p>Quando eu atingir essa milestone, vou oficialmente abandonar o produto que uso atualmente e me tornar o primeiro usuário alpha do ___k___. Parece pomposo, mas não é: Se o ___k___ não estiver bem desenvolvido nesse estágio eu estarei — sem exagero — me colocando em risco.</p><p>Enquanto for utilizando vou implementando o que falta e aplicando patches, o que pode levar de 3 a 6 meses (com uma margem de improbabilidade tão grande que na verdade essa minha “previsão” é estúpida, mas tudo bem).</p><p>Depois desses 3 a 6 meses, quando o ___k___ atingir a milestone onde possui todas as funcionalidades necessárias pra ser razoavelmente utilizado vou lançar oficialmente, mas provavelmente em estágio — no máximo — beta.</p><p>Acabei de me dar conta de que uma das vantagens do nome que eu escolhi é que ele não “entrega” o que é o projeto, mas ainda assim vou seguir sem divulgar 😜</p><p>Enfim, quis informar vocês o máximo possível sem burlar nenhuma das regras que defini pra mim mesmo enquanto desenvolvo o ___k___.</p><p>Assim que puder, conto mais.</p><p><em>Originally published at </em><a href="https://www.galvao.eti.br/projeto-k-o-maximo-que-posso-dizer-no-momento/"><em>Er Galvão Abbott</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c78c31a5809a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco/projeto-k-o-m%C3%A1ximo-que-posso-dizer-no-momento-c78c31a5809a">Projeto “k”: O máximo que posso dizer no momento</a> was originally published in <a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco">O ElePHPant do Chapéu Branco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feliz Aniversário, Linux!]]></title>
            <link>https://medium.com/o-elephpant-do-chap%C3%A9u-branco/feliz-anivers%C3%A1rio-linux-ca6338d9e06d?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca6338d9e06d</guid>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Fri, 25 Aug 2017 18:15:52 GMT</pubDate>
            <atom:updated>2017-08-25T18:15:54.416Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*lJjEwQgSyMO2izpM.png" /></figure><p>Quem me conhece sabe que eu não sou um grande fã do que eu chamo de “tecnologia + auto-ajuda”, coisas do tipo “mudou a minha vida”, “fez de mim uma pessoa diferente”, etc… mas, como toda a regra, esta também tem exceção:</p><p>Não é, de forma alguma, exagero da minha parte afirmar que o Linux mudou a minha vida, fez de mim um profissional melhor e até mesmo uma pessoa melhor. Como todo o Brasileiro da minha época fui por muito tempo um usuário de Windows e sim, não apenas era satisfatoriamente feliz como nada me incomodava a respeito deste SO, era “o que tinha”, era “O Sistema Operacional”… até que conheci, com mais intimidade por assim dizer, o Linux.</p><p>A primeira distro que usei — confesso que sem muito sucesso — foi o SUSE (versão 7 ou 8, se não me falha a memória). Depois Ubuntu, Debian e finalmente “me aquietei” (por enquanto, anyway) com o Fedora.</p><p>Usar Linux significa muita coisa pra mim:</p><ul><li>Confiança: Como há absoluta transparência, pelo fato de que Linux é Open Source, eu posso confiar que não serei espionado, manipulado ou que meus dados serão utilizados de forma indesejada;</li><li>Segurança: Acredito não estar sendo injusto quando afirmo que Linux é um SO mais seguro do que as alternativas comerciais. Nunca fui hackeado. Nunca peguei vírus, worm, malware, etc, etc, etc…</li><li>Estabilidade: A minha máquina não trava. Não dá Tela Azul (ou seja qual for a cor do momento) da Morte e, embora Linux tenha, sim, bugs (qual software não os têm?), se você escolher bem a distro que melhor se adapta as suas necessidades as chances de um bug crítico que impeça você de usufruir do SO são praticamente inexistentes.</li></ul><p>Mais do que tudo, entretanto, Linux pra mim significa Liberdade. Ah, Liberdade, palavrinha complicada e que — ironicamente — é a responsável por muitos dos erros que se cometem na Comunidade Open Source… mas sim, o Linux me dá Liberdade:</p><p>O meu SO não me dá ordens, ele me faz pedidos. A minha vontade é soberana na minha máquina. Faço o que bem entendo. Se quiser posso até mesmo violar preceitos do prórprio SO (e, claro, arco com as consequências). Meu SO não dita as regras, ele sugere. E eu aceito, se quiser.</p><p>Meu SO nunca me encurrala em um canto, me deixando sem opções. Instalar uma nova versão de Linux não exige um upgrade de hardware, não devora memória RAM de forma quase criminalmente irresponsável. Meu SO nunca exige que eu reinicie a máquina, eu faço isso se quiser e quando quiser.</p><p>Customizo o meu SO do jeito que eu bem entender. Mudo a cor, mudo o logo, mudo a interface gráfica inteira. Jogo no lixo, refaço, remixo, faço uma zona se eu quiser. Não existem logos obrigatórios, mensagens de copyright ingenuamente estúpidas que estão lá pra ninguém ler.</p><p>É por tudo isso (e muito, mas <strong>muito</strong> mais) que eu não podia deixar esse dia passar em branco.</p><p>Feliz Aniversário, Linux. Conheci você quando você era um pirralho de ≃ 8 anos de mercado e hoje você está fazendo 26. Cada vez mais forte, sempre melhor. Continue assim: graças a você faço o meu trabalho do jeito que quero e usufruo de um sentimento que muita gente não conhece ou entende: tranquilidade em relação ao meu Sistema Operacional.</p><p><em>Originally published at </em><a href="https://www.galvao.eti.br/feliz-aniversario-linux/"><em>Er Galvão Abbott</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca6338d9e06d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco/feliz-anivers%C3%A1rio-linux-ca6338d9e06d">Feliz Aniversário, Linux!</a> was originally published in <a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco">O ElePHPant do Chapéu Branco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Important announcement #1]]></title>
            <link>https://medium.com/the-white-hat-elephpant/important-announcement-1-916d15cfd839?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/916d15cfd839</guid>
            <category><![CDATA[speakerdeck]]></category>
            <category><![CDATA[slides]]></category>
            <category><![CDATA[slideshare]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Sat, 12 Aug 2017 21:21:06 GMT</pubDate>
            <atom:updated>2017-08-12T21:21:39.701Z</atom:updated>
            <content:encoded><![CDATA[<p>Migrating from SlideShare to SpeakerDeck</p><p><strong>TLDR;</strong> I’m moving from my original <a href="https://www.slideshare.net/ergalvao/">SlideShare</a> to my <a href="https://speakerdeck.com/galvao">SpeakerDeck</a>.</p><p>It’s no secret that <a href="https://medium.com/the-white-hat-elephpant/hey-slideshare-keep-your-act-together-84db50dd60fd">I’ve been very unsatisfied with SlideShare</a>: From silly bugs to weird interface issues to ads, I came to believe it’s not the best place to share my talks’ slides.</p><p>I’ve finally began the painful process of migrating my presentations to SpeakerDeck. This will take me a while to complete, since I’ll need to:</p><ol><li>Manually collect the original data from SlideShare and put it on each talk;</li><li>I don’t have all the original slides here, so I’ll need to download them from SlideShare and upload them to SpeakerDeck;</li><li>The ones I have on both sides need to be checked for inconsistencies.</li></ol><p><strong>The important part to notice here</strong> <strong>is that I’ll be deleting the presentations I migrate</strong> to keep them all in one place and underline the single point to find them.</p><p>Thank you all for your support and understanding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=916d15cfd839" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-white-hat-elephpant/important-announcement-1-916d15cfd839">Important announcement #1</a> was originally published in <a href="https://medium.com/the-white-hat-elephpant">The White Hat ElePHPant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eventos que você deveria conhecer]]></title>
            <link>https://medium.com/o-elephpant-do-chap%C3%A9u-branco/eventos-que-voc%C3%AA-deveria-conhecer-853cda216668?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/853cda216668</guid>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Sat, 05 Aug 2017 19:17:57 GMT</pubDate>
            <atom:updated>2017-08-05T19:17:57.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/469/1*9ugZ3KZDrE5ik4gIjRM64A.png" /></figure><h4>Parte 2: Fórum de Tecnologia em Software Livre</h4><p>Não é surpresa que o segundo evento que venho aqui divulgar também aconteça no Paraná: o Estado é um dos maiores destaques nacionais em Software Livre.</p><p>O <a href="http://ftsl.org.br/">Fórum de Tecnologia em Software Livre</a> terá sua 9ª edição de 27 a 29 de Setembro, na UTFPR em Curitiba.e conta com o apoio, entre outros, do <a href="http://www.serpro.gov.br/">SERPRO</a>, uma das entidades de maior relevância no país no uso e produção de Software Livre.</p><p>O evento conta com atividades diversas e tem confirmadas as participações de profissionais que admiro muito: Daniel Lenharo, Eriberto Motta, Antonio Marques e o mestre Flávio Lisboa.</p><p>Este ano tive, mais uma vez, o prazer ser convidado pela organização para participar: vou estar estar lá, falando de PHP e Segurança.</p><p>E aí, ‘bora pro FTSL? =)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=853cda216668" width="1" height="1" alt=""><hr><p><a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco/eventos-que-voc%C3%AA-deveria-conhecer-853cda216668">Eventos que você deveria conhecer</a> was originally published in <a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco">O ElePHPant do Chapéu Branco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A look into sessions and security]]></title>
            <link>https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-5cf7553f611c?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/5cf7553f611c</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[sessions]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Fri, 04 Aug 2017 12:46:13 GMT</pubDate>
            <atom:updated>2017-08-04T12:46:13.419Z</atom:updated>
            <content:encoded><![CDATA[<h4>“Final” Part: Eternal sessions of the clueless user</h4><p>In the <a href="https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-363d11438c5f">fourth article</a> of this series we talked about how to use a score-based approach to minimize false occurrences. Now it’s time to talk about… time.</p><h4>Before we begin: A bit of history on eternal sessions</h4><p>It’s no secret that companies like Google, Facebook and Twitter (just to name a few) are trend setters in the industry, for better or for worse.<br>A long time ago, trend setting companies changed the security landscape drastically by introducing/popularizing two concepts:</p><ol><li>The extinction of the username: The e-mail address, a public, well known detail about the user, began to be used as a user’s identity (More on this on a future article);</li><li>What I call “eternal session”, but is often referred as “permanent session” or “one-time authentication”: Once you authenticate to the application on a device you <strong>never </strong>have to do it again.</li></ol><p>Let me be clear: There’s absolutely no problem with either idea per se. Our industry should — as often as possible — try out new concepts, open the dialogue, debate pros and cons and then decide wether or not to adopt them. The problem is our industry seems to always rush to the adoption part as quickly as possible, often ignoring any of those pesky, time consuming intermediary steps.</p><p>Some companies resisted/still reist the idea (the first case I remember being Yahoo!, which at the time used 14-day sessions, which while not perfect is still better than “forever”), but the problem remains. Since making the user comfortable is the goal here (more on this below), the “Industry Giants”, the ones the user deals with every day, perpetuate the practice.</p><h4>The problem with eternal sessions</h4><p>The main problem with eternal sessions is, simply put, that they tie a user to a device. This might seem logical, since the user do own the device in question, but the issue comes when someone else gains control of the device.</p><p>What makes the issue so complicated is that it involves much more human aspects than technological ones:</p><ol><li>The issue is often explored on infidelity/privacy anecdotes and jokes, which frequently lead to the terrible concept of “why worrying if you have nothing to hide”;</li><li>A foul use of someone else’s device is often perceived as improbable or easily fixed;</li><li>The potential damage of a hijacked device is often dismissed as minimal;</li><li>The ever so common concept that the user <strong>must</strong> be as comfortable as possible, no matter the risks;</li><li>The “solution” (in-my-never-humble-opinion) requiring time, dedication, patience and effort, values that are more and more rare nowadays.</li></ol><h4>But… What about 2FA or &lt;insert-your-solution-here&gt;?</h4><p>Of course there’s nothing wrong with 2FA, quite the opposite: everyone should use it and I strongly promote it as anyone involved in the security scenario should, but I believe the problem runs deeper than that.</p><p>Also, 2FA is one more “lock to be picked”, one more technological solution that, while strong and praised, doesn’t treat the “real problem”, so to speak.</p><h4>Let’s talk about a solution</h4><p>In my point of view the problem is, once again, centered on human issues, such as habits — which are always hard to change — and mainly education. Security is not only a serious issue, it’s something every segment of the industry should be informed about and focused on improving. Contrary to this idea, though, the userbase of an application is usually the segment which is left in the dark.</p><p>We assume our users want comfort and ease of use over anything else, but we don’t ask and we don’t offer them anything to clarify this assumption, no choice, no information. It’s like we’re saying to them “Here: assume our company is savvy enough to keep you safe”. Problem is no one talks about how much this trust that we demand of our userbase is affected with security-related issues being portrayed by the media almost on a daily basis. The only lesson a user may learn is that maybe we’re not that savvy; maybe there’s something deeply wrong; maybe we shouldn’t be trusted so blindly. How could we expect them to learn anything else if we don’t make any effort to teach them anything else?</p><p>We must stop infantilizing our userbase. They need to be educated and informed on how serious and complex security is and how much risk are they taking when they check the little “Remember me” checkbox. They need to know the tradeoff between their comfort and their digital security. Most of all, they need to have the choice — many applications don’t even offer that — to put their comfort in first place, as long as they have some knowledge of what that entails.</p><p>Giving them a choice is specially important because it shifts the responsibility to their side. Once again, treat the user as an adult, not a child: “You want this? OK, you’ve got it, but know what you’re getting and know what you’re gaining and losing”.</p><h4>So, what should I do?</h4><p>Well, it’s a fact that nowadays the user has assimilated the concept of comfort and cutting this off “cold turkey” would be tough. I propose a middle ground that benefits everyone: Make the user session last two weeks tops. Also, try to educate the user, give them information, tell them why your company is doing that.</p><p>The main issue, as I’ve stated, is that the user must begin to understand — even if on a basic level — what they are gaining/losing by accepting less comfort. Turn a negative concept into a positive one, make them know their security is being improved.</p><p>So, I finally reached the “end” of this series (the subject and the disussion are really endless). This particular article was by far the hardest one, since it deals with less (none?) technological issues. I hope you’ve enjoyed this as much as I did.</p><p>Thank you and see you soon! =)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cf7553f611c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-5cf7553f611c">A look into sessions and security</a> was originally published in <a href="https://medium.com/the-white-hat-elephpant">The White Hat ElePHPant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A look into sessions and security]]></title>
            <link>https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-363d11438c5f?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/363d11438c5f</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[sessions]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Wed, 05 Jul 2017 15:00:52 GMT</pubDate>
            <atom:updated>2017-07-06T09:20:06.407Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part #3: The score approach</h4><p>In the <a href="https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-ea3fa75b4f58">third article</a> I’ve reached the conclusion that the most important concepts when thinking about secure sessions are Coherence and Validity. I’ve also touched a very delicate point when dealing with those: false positives. No one wants to keep kicking the user out or worse, preventing the user to log back in when he/she haven’t done anything wrong. While this is a very valid point I’d argue that it’s best to wrongfully do so instead of getting your application hacked. There’s another way, though: keeping a score.</p><h4>Score? What is this all about?</h4><p>In theory it’s as straightforward as it sounds: Keeping a score, giving or taking points depending on the situation. In practice (and context) it’s much more complicated than that.</p><p>This approach makes a lot of sense because it lets us deal with the boolean concept of validity in a mathematical way, and therefore easily translatable to code.</p><p>Before we begin we need to decide if we’ll initially consider a session to be inherently valid or invalid. In security we more often than not apply the concept I like to call “guilty until proven innocent”: to be suspicious until we have some level of certainty. I often tell a little joke to my students, saying that the best security experts are “paranoid control freaks”. There’s a lot of truth — and efficiency — in that.</p><p>When dealing with sessions though, this concept doesn’t apply for a very simple reason: In order to consider a session invalid we need to collect data about it to determine it’s inconsistency and therefore unless a session was previously locked (see the past article on that), we have no other option than to consider it valid from the beginning.</p><h4>Defining points, severities and thresholds</h4><p>The entire point of this article is to provide ideas to make a system from which we can determine a session’s apparent validity. For that we’ll need an initial value, a scale, defining severity (and it’s numerical value) for each of the possible transgressions and finally a threshold from which a session can no longer be considered valid.</p><h4>Scale, initial value, and threshold</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*L12wh3eXv6-0CIc0gdT8pQ.png" /><figcaption>A proposed scale</figcaption></figure><p>We begin our scale considering a session to be perfectly valid (10). The valid threshold goes until 8 and if it goes any lower than that we need to take action. The kind of action to be taken will be determined, obviously, by how low the session will descent on our scale.</p><h4>On suspicion and action</h4><p>Between 7 and 6 (Suspicious), detailed logging must take place. It’s when we keep our user under heavy scrutiny and while maintaining a decent level of privacy we need to know which actions the user will take in our application (e.g. is he/she going to delete something? modify something?).</p><p>Taking the complexity up to a whole different level, we could (should?) implement a level of granularity that raises the security on our application even more: I’d argue that, on applications that need a strict security implementation[1], actions should begin to be less and less available to the user as he/she proceeds. A “level 7” score, for an example, shouldn’t be able to “truly delete”[2] something, while a level 6 should be logged out and forced to log back in. Anything below that should be automatically locked and analysed.</p><p>[1] This goes beyond the scope of this article, but a very good reference for this can be found, as usual, at <a href="https://www.owasp.org/">OWASP</a>: more specifically in the <a href="https://www.owasp.org/index.php/Category:OWASP_Application_Security_Verification_Standard_Project">ASVS project</a>.<br>[2] The good ol’ “flagging x deleting” strategy.</p><h4>Collected data, transgressions and severity</h4><p>As we’ve determined, we need to collect some data about the session in order to be able to define it’s validity. I’d argue that the more data (always respecting a decent level of privacy) we have the best. User browser, OS (if possible), IP address, and so on.</p><p>Also, for the purposes of consistency of implementation, we should define the possible severities and their quantified values. I’d propose a simple Low (-1), Medium (-2), High (-4) and Critical (-5) set, with the advantage that, if necessity arrives, we could easily insert middle-grounds between them.</p><p>While it may appear that low transgressions may not be useful, the concept here resides on the number of occurrences inside a session. It’s basically asking “How many times a user can do this inside the same session?”.</p><p>I obviously didn’t — and won’t — covered all possible cases of what I call “transgression”, but I’ll explore an additional one in here, which I believe to be self-explanatory (similar to the IP case).</p><p><strong>Transgression</strong>: User’s browser changes inside a session<br><strong>Proposed Value (Severity)</strong>: -1 (low)</p><p><strong>Transgression</strong>: User’s IP changes inside a session<br><strong>Proposed Value (Severity)</strong>:<strong> -2</strong> (medium)</p><p><strong>Transgression</strong>: Session token mismatch/non-existent<br><strong>Proposed Value (Severity)</strong>: -4 (high)</p><p><strong>Transgression</strong>: User‘s role changes without admin intervention<br><strong>Proposed Value (Severity)</strong>: -5 (critical)</p><p><strong>Transgression</strong>: Attempt to change the User’s account ID inside a session<br><strong>Proposed Value (Severity)</strong>: -5 (critical)</p><p>I believe you’ve got the idea at this point.</p><h4>“But… but… in <em>my</em> case this is not…”</h4><p>I know, I know, believe me. There are a lot of practical issues to be considered, but security isn’t optional or dependent on whims and special cases. It simply can’t be.</p><p>The advantage of this approach, when allied with consistent logging and debugging practices, is that not only the number of false positives should drop but you can also learn and refine the score system as you go.</p><p>On the next (and last) article of this series I’ll talk about sessions &amp; time and present a logical sketch that encompasses the topics covered here. See you then!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=363d11438c5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-363d11438c5f">A look into sessions and security</a> was originally published in <a href="https://medium.com/the-white-hat-elephpant">The White Hat ElePHPant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP7 is evolving! What’s new?]]></title>
            <link>https://medium.com/the-white-hat-elephpant/php7-is-evolving-whats-new-4aa38090112f?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/4aa38090112f</guid>
            <category><![CDATA[php7]]></category>
            <category><![CDATA[php]]></category>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Mon, 03 Jul 2017 15:34:36 GMT</pubDate>
            <atom:updated>2017-07-03T15:34:36.891Z</atom:updated>
            <content:encoded><![CDATA[<h4>7.1 and the upcoming 7.2 release make PHP even more awesome!</h4><p>While I’m currently writing the next part of my “<a href="https://medium.com/the-white-hat-elephpant/a-look-into-sessions-and-security-86a381675bbd">A look into sessions and security</a>” series, I couldn’t help to take some time to write on how fast PHP7 is evolving.</p><p>PHP 7.0 was, in my opinion, the most important PHP release since PHP 5.3: it brought us new operators, awesome functionalities and even <a href="https://medium.com/the-white-hat-elephpant/php7-more-strict-but-only-if-you-want-it-to-be-78d6690f2090">the possibility to code with strict typing</a> — at least to a point. It’s amazing to see how fast the language keeps evolving after the .0 release and how the new functionalities themselves brought a plethora of new issues. In case you don’t know this already, you can easily follow the process of each release <a href="https://wiki.php.net/rfc">here</a>.</p><p>PHP 7.1 (the current stable release) already brought us a lot of interesting features and PHP 7.2 (currently in alpha and planned for release at the end of November) will get us a few more. These are the ones that are most noticeable, in my opinion:</p><h4>PHP 7.1</h4><ul><li><strong>Nullable Types, </strong><a href="https://wiki.php.net/rfc/nullable_types"><strong>RFC</strong></a><strong> by Levi Morrison and Dmitry Stogov:</strong><br>A much needed improvement over the typing system, this makes possible to pass a NULL value to a parameter of any type.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/966edbf318c5525311768049fadd322d/href">https://medium.com/media/966edbf318c5525311768049fadd322d/href</a></iframe><p>$bar in this case MUST receive either a string or NULL.<br>$baz MAY receive an int, NULL or be omitted, defaulting to NULL.</p><ul><li><strong>The end of Mcrypt, </strong><a href="https://wiki.php.net/rfc/mcrypt-viking-funeral"><strong>RFC</strong></a><strong> by Scott Arciszewski:</strong><br>It’s a known fact that Mcrypt is considered abandonware: it was last updated ≃ 5 years ago and it has open tickets dating back to 2003. Being an extension related to security and having a much more reliable project such as openssl available made Mcrypt’s end inevitable.</li><li><strong>Void Return Type, </strong><a href="https://wiki.php.net/rfc/void_return_type"><strong>RFC</strong></a><strong> by Andrea Faulds:</strong><br>Another inherent need of PHP7’s typing system: the ability to write functions/methods that doesn’t return a value.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/724a6a727a723fcc7d66aa688c48fcb0/href">https://medium.com/media/724a6a727a723fcc7d66aa688c48fcb0/href</a></iframe><ul><li><strong>Support Class Constant Visibility, </strong><a href="https://wiki.php.net/rfc/class_const_visibility"><strong>RFC</strong></a><strong> by Sean DuBois:</strong><br>This one will probably see a slower rate of adoption of even interest, but it’s very useful (and arguably an obvious need) in the context of OO: the ability to define class constants as public, protected or private.</li></ul><h4>PHP 7.2</h4><ul><li><strong>Argon2 Password Hash, </strong><a href="https://wiki.php.net/rfc/argon2_password_hash"><strong>RFC</strong></a><strong> by Charles R. Portwood II</strong><br>Argon2 is the newest and most talked about hashing algorithm in actuality and rightly so: it won the <a href="https://password-hashing.net/">Password Hashing Competition</a>, beating 23 competitors. Starting on PHP 7.2, Argon2 will be available to be used in the password_hash functions.</li><li><strong>Debugging PDO Prepared Statement Emulation, </strong><a href="https://wiki.php.net/rfc/debugging_pdo_prepared_statement_emulation_v2"><strong>RFCs</strong></a><strong> by Adam Baratz</strong><br>Probably one of the most awaited features on the language, it is as clear and straightforward as it sounds: starting on PHp 7.2 we’ll finally be able to show the resulting query of a prepared statement.</li><li><strong>Object typehint, </strong><a href="https://wiki.php.net/rfc/object-typehint"><strong>RFC</strong></a><strong> by Michał Brzuchalski</strong><br>A much needed addition to the typing system, the ability to declare a parameter and/or a return type as a “generic” object. Since I’m currently developing my applications relying heavily on the typing system this is, for me, the most awaited addition to it.</li></ul><h4>Conclusion</h4><p>PHP7 is a thing of beauty. The amount and quality of the changes being implemented are incredible and they are lifting the language and it’s ecosystem to a whole new level. There are a lot of other RFCs that I’ve missed here and the process is entirely public so please, go check it out and keep yourself informed and current!</p><p>Long live PHP7! ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4aa38090112f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-white-hat-elephpant/php7-is-evolving-whats-new-4aa38090112f">PHP7 is evolving! What’s new?</a> was originally published in <a href="https://medium.com/the-white-hat-elephpant">The White Hat ElePHPant</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eventos que você deveria conhecer]]></title>
            <link>https://medium.com/o-elephpant-do-chap%C3%A9u-branco/eventos-que-voc%C3%AA-deveria-conhecer-37134911b412?source=rss-c27f1feba584------2</link>
            <guid isPermaLink="false">https://medium.com/p/37134911b412</guid>
            <dc:creator><![CDATA[Er Galvao Abbott]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 12:50:40 GMT</pubDate>
            <atom:updated>2017-06-28T12:50:40.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/883/1*5vgcVsNcylLFnHpiDP0ZgQ.jpeg" /></figure><h4>Parte 1 — Latinoware</h4><p>Meu amigo / minha amiga: Se você não conhece o <a href="http://latinoware.org/">Latinoware</a>… eu nem sei o que lhe dizer. Mentira, claro que eu sei: e vou dizer agora =)</p><p>O Latinoware é, pura e simplesmente, um dos melhores eventos de Software Livre da América Latina. São três dias de pura imersão em Tecnologias Livres: do hardware ao desenvolvimento, da robótica ao sistema operacional, contando com cursos, palestras e oficinas.</p><p>O evento, que tem sua 14ª edição este ano, acontece nas fantásticas dependências da Itaipu Binacional, em Foz do Iguaçu (PR), combinando tecnologia, networking e turismo.</p><p>Ao contrário do que acontece com diversos eventos, o Latinoware soube crescer mantendo seu DNA “Nerd”, nunca perdendo o foco na tecnologia.</p><p>A Chamada de Trabalhos do evento vai até o dia 31 de Agosto (tá esperando o que, mané?) e as inscrições para participantes já estão abertas a um preço super razoável para um evento dessa dimensão.</p><p>E sim, tem PHP (além de Python, Java e outras linguagens) na programação do evento.</p><p><a href="http://latinoware.org/er-galvao-abbott/">Eu vou estar lá</a>, imensamente feliz e honrado de ser novamente convidado para palestrar.</p><p>Estamos combinados então: Vejo você no Latinoware 2017!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37134911b412" width="1" height="1" alt=""><hr><p><a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco/eventos-que-voc%C3%AA-deveria-conhecer-37134911b412">Eventos que você deveria conhecer</a> was originally published in <a href="https://medium.com/o-elephpant-do-chap%C3%A9u-branco">O ElePHPant do Chapéu Branco</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>