In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
Lessons learnt from hunting an old Linux kernel bug30m
The story behind a recent blogpost of ours: https://engineering.skroutz.gr/blog/uncovering-a-24-year-old-bug-in-the-linux-kernel/
I will try to cover the aspects not covered extensively in the blogpost, i.e. the interaction with the Linux kernel community, the availability of tools and how it has impacted kernel debugging over time, etc. Additionally, I will comment on the responses to the post itself, demonstrating why this bug may have remained uncovered for 24 years.
In this presentation, we discuss recent segment routing innovations, in particular Flex-Algo and BGP Classful Transport (BGP-CT). These provide a way of extending the Seamless MPLS paradigm to allow inter-domain transport according to a variety of cost-functions, such as minimum latency or minimum monetary cost.
An introduction to a new and novel routing protocol for the datacenter; Routing in Fat Trees or in short RIFT. In this presentation we will dive into what challenges RIFT solves over the use of OSPF, IS-IS and BGP in the datacenter. I will also give an update on the status of the work in IETF and point out to some implementations.