home.social

#centr2019 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #centr2019, aggregated by home.social.

fetched live
  1. Using jq on a JSON file on my machine. This is "amazonless" analysis. #CENTR2019 #DataOps

  2. Using jq on a JSON file on my machine. This is "amazonless" analysis. #CENTR2019 #DataOps

  3. " I know Stéphane dislike the word 'serverless'. " Apparently, I have a reputation at #CENTR2019.

  4. " I know Stéphane dislike the word 'serverless'. " Apparently, I have a reputation at #CENTR2019.

  5. Just reading the front Web page of *every* possible #DataOps tool is a full-time job. I discover Amazon Athena aws.amazon.com/athena/

    #CENTR2019

  6. Just reading the front Web page of *every* possible #DataOps tool is a full-time job. I discover Amazon Athena aws.amazon.com/athena/

    #CENTR2019

  7. The meeting chair, to the next speaker: "How long do you need?"

    The speaker: "Three hours"

    #CENTR2019

  8. The meeting chair, to the next speaker: "How long do you need?"

    The speaker: "Three hours"

    #CENTR2019

  9. Also, new keyword: #DataOps, doing things with data and programs (processing text files with grep and awk is DataOps?)

    #CENTR2019

  10. Also, new keyword: #DataOps, doing things with data and programs (processing text files with grep and awk is DataOps?)

    #CENTR2019

  11. Now discovering the #Celery framework (in meetings, I always discover things I didn't know)

    "an asynchronous task queue/job queue based on distributed message passing." celeryproject.org/

    #CENTR2019

  12. Now discovering the #Celery framework (in meetings, I always discover things I didn't know)

    "an asynchronous task queue/job queue based on distributed message passing." celeryproject.org/

    #CENTR2019

  13. Good morning, Amsterdam!
    One last day for the #CENTR2019 meeting. Let's talk about domain names.

    Now, R&D working group, the funny new stuff. (Expect machine learning and AI.)

  14. Good morning, Amsterdam!
    One last day for the #CENTR2019 meeting. Let's talk about domain names.

    Now, R&D working group, the funny new stuff. (Expect machine learning and AI.)

  15. Migrating to the cloud: are the servers cattle (the cloud) or pets (the machines you manage)? #CENTR2019

  16. Funny coffee break idea at #CENTR2019 when discussing #registryLock against #domainNameHijackings: a "light" lock where domain name changes could still be done automatically through #EPP _but_ only during office hours, to allow detection and repair (most hijackings take place during the night, or week-ends or holidays). Bonus: it is easy to implement it.

  17. Funny coffee break idea at #CENTR2019 when discussing #registryLock against #domainNameHijackings: a "light" lock where domain name changes could still be done automatically through #EPP _but_ only during office hours, to allow detection and repair (most hijackings take place during the night, or week-ends or holidays). Bonus: it is easy to implement it.

  18. "For an engineer, 2FA improves security, because it is hard for an attacker to work around it. For a lawyer, a signed paper improves security, because you will be toasted but you can sue someone. Different views on security." #CENTR2019 #domainName #domainHijackings

  19. "For an engineer, 2FA improves security, because it is hard for an attacker to work around it. For a lawyer, a signed paper improves security, because you will be toasted but you can sue someone. Different views on security." #CENTR2019 #domainName #domainHijackings

  20. #CENTR2019 meeting, this morning: registry lock (for instance to prevent attacks like the 2018 middle-east hijackings)

    Do you lock your domains names? If no, why? Lack of money? Lack of awareness? Unlocking too inconvenient?

    #cybersecurity #domainNames

  21. #CENTR2019 meeting, this morning: registry lock (for instance to prevent attacks like the 2018 middle-east hijackings)

    Do you lock your domains names? If no, why? Lack of money? Lack of awareness? Unlocking too inconvenient?

    #cybersecurity #domainNames

  22. Want to know if *your* network rejects invalid/hijacked #BGP routes, as it should? Visit ripe.net/s/rpki-test and wait a few seconds. #RPKI #CENTR2019 #cybersecurity

  23. And Job Snijders talks now about #RPKI, to protect #DNS operators against #BGP hijackings. #CENTR2019

    Also: "Shortest AS path is now a security feature: keep peering"

  24. "Social networks are important." (And the speaker was not talking about Facebook.) #cooperation #DNS #CENTR2019

  25. Also: monitor, monitor, monitor crt.sh/ And from external viewpoints such as RIPE Atlas. And monitor the parents, not just you. #DNS #CENTR2019

  26. Lessons from the hijacking attack against #Netnod: use in-bailiwick glue for your domains, use 2FA, use #DNSSEC, use registry lock.
    Good advices for all domains!
    #CENTR2019

  27. Now, the session on domain name hijackings (Middle-East governments in 2018) at #CENTR2019. First, Netnod. This is TLP:white, I betray nothing in posting this.

  28. "The script is cronned" (for "the script runs from cron"). Heard at #CENTR2019

  29. "The problem occurred during the week-end, thus increasing the time before the fix." #Murphy #production #CENTR2019 #DNSSEC

  30. "Tour de table" of european domain name registries at #CENTR2019. Nice to hear english spoken with so many accents. That's Europe at work :-)

  31. OK, going to the Technical and Security Working Groups (both at the same time) of #CENTR. Among the (many) subjects, #DoH and domain name hijackings. Any input for this meeting, dear users of the #DNS?

    #Amsterdam #CENTR2019