• 1 Post
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle


  • 15’000/15’000 65 chf/month (~70$/month). No cap. Native IPv6 (with static IP subnet and reverse DNS if you want), Free IPTV on multicast. With a bit of extra you can have Static IPv4 or even the ability to run your own Autonomous System and have BGP at home.

    Here in Zurich/Switzerland.

    But there aren’t consumer router that can handle this speed so I need to have a workstation on 24/7 for routing that











  • Bobby table, this, buffer overflow… Are all similar in spirit.

    Bobby table is a way for hiding the malicious SQL query after a normal query (in that case after the select with “Bobby” you inject the malicious drop table)

    In this case after the normal email (that normally would serve for both identifying the user and for the mail to send the recovering mail), the attacker sends two mails, the first is fo identifying the user the second to send the recovering mail

    In the case of buffer overflow you inject malicious code after normal(-ish) data

    It’s not an XHR attack since for the mail recovery workflow you don’t need an authenticated session.

    To be a bit more compassionate to the developers, this is probably some dynamic typing problem. Probably ruby is “smart” into understand that an array can contain strings after all… So an array of strings is as good as a string… But here we go into static vs dynamic typing… And it’s a bit of religious war (fun fact in 2011 i was advocating with Guido Van Rossum in having at least an optional static typing check in Python - at the time the discussion was how to make python faster/compiled - and he was borderline mocking me 😅 and few years after pytypes but still no compilation at horizon 😂)







  • This! The point of automation is rarely saving time. The point of automation is increasing quality.

    It can be a data quality, it can be mitigating a production risk, can be avoiding regression.

    Heck even unit tests are automation (you may just manually test your code once and call the day).

    I am not saying that automation is always good, but the evaluation should be

    1. what is the cost of production/data quality/regression gone wild? (Possibly in€/$/¥)
    2. what is the cost of the person/team performing the task over 1 Year (Again, £€$¥)
    3. what is the expected cost of the person/team implementing automation?

    Then you do (3)*3 - (1) *3 - (2). Is it positive? You do, is it negative you? You don’t. The more it’s positive the higher the priority of doing.

    Why the *3? The first because the expected cost of automation is always massively underestimated The second because it takes multiple times something goes wrong till the decision is reconsidered 🙂

    Why 1 year? Because generally the task to automatize changes or disappear