Here I am. Okay so welcome back again. I hope you refilled. This is the last session of the day and I think it's one of the, it's probably the most important I think at the end because in terms, I'm speaking as the coordinator because it's very important to disseminate our work but also to collaborate with others which are being funded today by the same call. We're working towards the same mission which is the use. We had several zero seven projects again which are today represented by Deborah, Gergli, Raúl and Christian. They will tell us about their initiatives which are working on still horizontal but in some cases community specific efforts towards service provision and resource provisions for the use. So the first speaker would be Deborah Testi presenting DICE, so the Data Infrastructure Capacity for EOSC. It's an extensive name. These work engages with the UDOT and previous work on that and several work actions in the EOSCab as well and they will tell us more. Gergli, Stipols, a colleague and now friend, we know each other for a while, representing EGI, which again is one of the actions that offers and extends in several aspects, tool specific and community specific services for EGI towards the use and reliance is scale which are two quite important actions and I think also appealing from my point of view because they are focusing somehow on the communities but at the same time trying to offer general powerful services represented by Raúl and Christian. So I will now give the floor to Deborah, who's the first speaker and thanks again for being here to all of you. Hi Paolo, thanks for the invitation and for the organization of this very interesting event. I agree with you that the collaboration between our respective projects in this school is very important not only to strengthen our own projects but to strengthen the EOSC in general and what we can provide to the community. So thank you very much for this. I'll now share my screen if I can. Okay, thank you very much for confirmation. So as Paolo's already introduced, I'm Deborah Testi. I work at the Chineca Supercomputing Centre in Italy and I'm the project coordinator of the DICE project. As already said, DICE has been funded in the same call as OpenAir at Nexus, one of the InfraEOSCO 7 projects. So we start at the same time and we will have the same duration. We have 24 partners and our aim is related to the provisioning of the data management infrastructure to EOSC. So between our 24 partners, we have most of them that are service provider. This because also as for the other InfraEOSCO 7 project, more than after our budget is to provide services and resources to user and communities. So the majority of the partners are service provider but we engage also with some user communities and we have partners to support sustainability and outreach. As Paolo said before, the service provider that are coming together into DICE have a long experience working together. Some of them have been working together since the start of UDET. We have also some new partners, not UDET members that are helping us to support the service provisioning but with which we have collaborated already for since many years. So it's a very strong and very well connected group of providers. So which are the objectives of DICE? As I mentioned in general is to enable the data management infrastructure for EOSC. So the core of the activities is the provisioning of services and not only services but also the resources behind the services to enable fair workflow for communities. But we will also work to extend a little bit the data management service offered by working on long-term preservation policies to support sensitive data and to work with on the connection between the data services and the computing part. That will be also part of the work that will be related to keeping connection and updating the connection with the EOSC core as it will evolve in the next years. So that we will try to remain compliant with our services to the different EOSC rule of participation as they will be evolving in the next years. So a little bit more details on what we are offering in terms of services at least for in general as categories. This is a presentation of the resource data workflow that normally is being followed even if maybe not in all the steps but starting from the data collection to the data publication and basically what DICE services are trying to cover is all the from the storage of the raw data coming from the preprocessing up to when they are ready to be more globally searchable and published. If we look at the same diagram but put it into a pyramid representation so we can classify the DICE offering into different categories. So first of all we have services to cover the what we call project or personal workspace which is the short-term midterm storage that is used during the execution of a project so where the data changing and being updated frequently. On top of this we have a data archive which is midterm storage to be used in between projects or after the project has been completed so it's related to less active resource data. Then we have policy-based data archive which is mid-long-term archive again for non-active resource data which adds on top of data archive additional services like integrity checks, replication, so it's for very stable data archives. Then we have a data repository to share the final data with other members of the communities or to the generic public in according to fair principle and then we have some data discovery service to find the data that has been published. If we look at the different this type of services are very different and we have basic services so some of these services can be already accessed with a web interface. They do not require any specific configuration or authorization by the service providers they can just be used as is but we can also more satisfy more specific requests and we classify the service into standard requests and into more customized solution for specific communities or users. The difference between the last two is basically mostly on the time needed to fulfill the request and make the service available to the customer. If we put together the two type of categorization the one that I've shown before and this one we see that in DICE we try to cover as much as possible all the categories of services with as much as possible different options for user communities so to be as general as we can and be able to satisfy most possibly all the needs that will come up during the project. In the end we will have 14 services offered so we have more than 14 installation for virtual access and these are supported by more than 50 petabytes of storage offered by the different service provider. Some of the services are already available through the US portal that are the ones that have been already in production since a while but more installation more service provider will join and more services will be made available in the next couple of months through the US portal. Which are the expected inputs of DICE obviously first to scale up the offer provided via the US portal to provide scientific communities with state-of-the-art services in data management and to facilitate the open-size practice and for supporting the fair principle to foster synergy between upon European infrastructures support the collaboration in data provisioning and exchange across infrastructure and obviously try to incentivize the public actors to open up services and resources to researchers. In terms of collaboration as this is the session on possible collaboration so DICE plans to actively collaborate with in general all the European initiative but in particular we are looking forward to work together with the other O7 project and the O3 project when we start. We also would like to build a strong connection with user community we have already as I mentioned at the beginning few communities part of the project we but this is limited due to budget constraints but we plan to engage very actively with other communities outside of the project consortium in the next months. So this is a brief summary hope it was clear enough but if you have questions just feel free to ask or to contact me by email in the future. Thank you very much Deborah. So I would suggest to continue write your questions if you have any in the chat and to continue with the presentation so we can have a final discussion if this is fine with you. So I think next one in the line is Gervily am I right? Yes that's correct good afternoon can you see my slide? Yes. Yeah great so welcome everyone to this EGIA's overview presentation. I'm Gervily I work for the EGIA foundation and this Paolo nicely introduced me we've worked together for several years now on different infrastructure projects. I represent one of the compute project in this landscape and I work as the technical coordinator of this project since January. Let me start with a brief overview of the objectives so this project is very much focused on the computing aspect. The first objective is very specifically about this delivering the so-called cloud compute platform of the European Open Science Cloud offering compute capabilities to users. The second is linking to data management and to the so-called European data commons structure and vision and particularly the project aims to build so-called data spaces which is basically a collection of scientific data sets that are hosted on or near compute resources together with some analytic systems, portals, gateways, workflow systems that enables exploitation of the data by scientific audiences. The objective three is about integrating the platform with the EOS core. Actually I have some animation here. Objective three is about linking this compute platform and the data commons with the EOS through the EOS core and objective four and five are more outside looking. Number four is about working with initiatives that are similar to EOS and similar to the compute platform outside of Europe and number five is working with different providers that are not just in the consortium but wish to join this compute platform as we go ahead in the next 30 months. Similarly to the to Nexus and to DICE this project is very much focused on delivery of ready-to-use services. More than half of the budget is on service provisioning. The total budget of the project is around 12 million out of which 80 million comes from the commission and four million is contributed by the members of the EGI Federation. The whole consortium is coordinated by the EGI Foundation which is coordinator of the Penn European EGI Federation and the consortium largely or primarily is built from members of this EGI Federation and is expanding with different scientific communities who contribute to this data spaces work and act as early adopters of the overall setup. And what this setup is about is shown on this picture indicating a kind of architectural layout of the different layers where we position our services. We start fundamentally with the low-level infrastructure services which consist of different research clouds operated by universities, research institutes, public clouds operated by commercial entities, high throughput compute systems, clusters that are designed for massively parallel applications and high performance computing systems that are supercomputers that are suitable for closely coupled applications. On top of these infrastructure services we have different kind of federation tools that enables and allow users and user applications to use multiple infrastructure clouds, multiple clusters, multiple supercomputers together. This is achieved by providing federated computing, job distribution systems, federated identity management, a single sign-on across systems and federated data access enabling access to distributed data from any of these compute systems. As we move closer to the to the user layer or the top layer we have more user-facing capabilities such as interfaces, web portals designed for interactive computing, automated deployment of scalable clusters in these underlying systems, different services designed for artificial intelligence and machine learning applications and frameworks that help user portals distribute a high number of jobs and tasks across the available capacities. On top we have these data spaces, I will have further slide about that one. Basically these are the science discipline specific capabilities that are offered for certain disciplinary areas that incorporates applications, visualization tools that are designed and coming from the discipline and they exploit the underlying compute and federation capabilities. All these services are connected together through different service management tools, processes and policies by which we mean different monitoring systems for example that observe the availability and reliability of the services, accounting systems through which we can observe who used what, how much consumption was made by each community or use case and the documentation that the different service providers use in order to ensure responsiveness towards the use cases. All this tech is delivered through the ESC portal and made available for ESC users. And let me just show you one example that combination of these elements is possible for a given use case or for a given setup and for example the project provides so-called notebook service which is some of you may know is based on the Jupyter notebooks which is a web-based interactive computing environment through which one can write scripts, one can write codes and mix that with documentation, mix that with multimedia content. The CGN notebook service which is supported by the project offers access to big data that's distributed across the network, can be sitting in different scientific repositories and can import those big data into this interactive computing environment to perform to define and run analysis. Another service that this whole use case can rely on is the GitHub and the Zenodo repository that many of you know from the previous presentations and from the previous years. The setup enables users to export their notebooks and store them for the long term and share them through Zenodo and then other users can reproduce basically the same analysis by importing those notebooks from Zenodo into the so-called binder service that EJA offers and then import the same big data and rerun the same analytics again or in a customized way. So that's an example of how the cloud compute services, the different federation services and the interactive computing capabilities are all integrated together and work together also with GitHub and Zenodo to reproduce big data analytics. The full portfolio of our services is quite large. We have 61 providers and they contribute to 31 different types of services. You can see here that the largest contributor list is under the cloud compute service indicating that major part of this project is delivering infrastructure as a service cloud compute capabilities. This cloud compute enables the users to run their own applications to set up their own system within remote servers. The other services that we provide add extra capabilities on top of this underlying infrastructure. Many of these services of these 31 different types of services are already available in the Yask portal. If those of you who know the portal in the marketplace section there is a so-called communities and infrastructures grouping and within that you can already find the EJA as a community or grouping and if you click there you can see the 25 or so maybe a bit more services that are already available out of these 31 that I showed earlier and through this you can either access the services immediately because there is already ready to use configurations or you can request your own setup from the provider. One of the recurring questions is how capacity is allocated and how it's managed by the project. We have a large number of capacity providers who provide this cloud high throughput compute and high performance supercomputers and they assign this capacity on one hand to communities that are already in the project and I will talk about them in a minute and obviously for new users because that's the point of the whole project to be open for new business. The total capacity you can see here is distributed between traditional CPU based computers GPUs and also storage that's available for mid or short term usage. It's basically a scratch base that one can use while doing a certain calculations. All these compute capacity is allocated through a mix of funding mechanisms. On one hand we use the virtual access funding model and we have 16 providers using that one and they are paid by the commission to deliver the capacity so the access is free for any new user community. These 16 providers have been selected during the proposal preparation based on their location and the type of compute flavor they can offer in order to be able to cater for diverse needs but we also have agreement as a project with additional providers who are not paid by the commission but who are paid by their national government or funding agency or ministry to deliver compute capacity through EOSC for different types of audiences and integrating those policy based access providers enables us to extend the total capacity that we can assign for new use cases. We need to consider those different policy constraints that they have. Very often they are open for users who are coming from their own country but doing this intelligent brokering and the allocation of capacity we can hopefully satisfy all the incoming use cases. We also have pay for use providers, cloud for empty systems, offer capacity for payments so the payment on this case is for the users and we have also four sites that deliver supercomputers for piloting activities in the project and how these capacities assigned to users is shown on the on the next slide. We basically work with or expect to work with two types of use cases. One is that kind of long tail of science use cases the smaller user groups or users who want to try out things before going into more serious business. They can come in and they can access the capacity through the EOS portal. We have ready to use allocations that is open for many of the users and on the other hand we expect to have more complex use cases from multinational international communities where we need to fine-tune the setup. We need to allocate significant capacity in given set of countries or sites. We aim to attract those use cases and serve those use cases through a call that we will publish very soon in the coming weeks and we plan to have a cut of dates or evaluation three times per year for the submissions and through those evaluation process we will assign providers to each use case who will serve the use case and support them for aiming for the longer term and customized engagement. The scientific communities that are in the project are represented here. On one hand we have these data spaces that I mentioned is basically a mix of infrastructure capacity services storage and compute together with domain specific libraries and applications all combined together and offered as an integrated setup for example typically as a web portal through the EOS portal. We have 13 of these data spaces you can see here the scientific distribution and also the names of the different communities who offer them very often they are linked to as free research infrastructures or similar international initiatives. We will not just deliver these data spaces services but also perform a fair maturity assessment on those in order to ensure that they not just support users but support scientists in such a way that the final outcome of the research those researchers conduct are meeting the fairness criteria of EOSC and enrich EOSC with new scientific outcomes. We also have other types of user communities in the project we call them early adopters they basically are less mature they are not aiming to become providers in EOSC they want to use the EGIS services in order to carry out certain computing activities. And let me close with some notes on possible interaction with Nexus and with other 07 projects we had the first similar meeting at the EGIS public launch event so my ideas or our ideas are based on the knowledge there also I slightly fine-tuned these messages based on what I heard this morning. So one is I think we should work together on closing this whole research cycle and make this research cycle as easy to carry out for researchers as possible. Paulo started with this virtual cycle in his presentation fortunately I couldn't take a screenshot I wanted to include something like that basically here the idea is that EGIS would fit into the I think the left side of that slide that Paulo presented more in the computing and short and mid-term storage space and we should work with DICE with Zenodo with Nexus on importing scientific items into this computing model and pushing these final scientific outcomes or computing outcomes in the form of publications or in form of datasets into these longer term archives and repositories and catalogs. The second is working together on tracking the impact let's say impact of EGIS for example from my perspective or ours perspective this could be based on the EGIS commit dashboard which we have in a beta version I think we should move forward and move that into the latest dashboard and tools that you presented this morning and we probably should discuss how to do that and how to how to customize it in such a way that we can capture EGIS impact and we can capture EGIS impact and we can capture EGIS users impact in that you mentioned earlier that some of these will be part of the EOS score or are part of the EOS score I think we need to understand what are those and probably start with those as the EOS score is expected to be the long-term entity that we need to interface with. Very specifically with the Earth Observation Project C-Skill and reliance we work or we have worked on hopefully on the integration of their services and data with the compute platform that EGIS provides. Number four is to align the support for the big communities there are or there is common communities in some of the projects that we work in I think we should seek for these these commonalities as we go ahead and sign up and support new use cases. One of the activities that I mentioned EGIS will conduct is this so-called fairness assessment of the EGIS data spaces maybe some of you who did something similar could help us in here. Number five is the grid computing which is about lowering the environmental impact and CO2 emission of the overall compute platform that we deliver. I expect that your project has a similar activity there I think that's something worse to be aligned on what are the practices that you will apply and we will apply in order to have some joint activities here and the number six is I think the simplest is cross-project promotion and dissemination of the results of the opportunities that we all make available for ESC users. So as a summary EGIS delivers the compute platform which consists of basically two layers one is the compute continuum with HTC cloud HPC machines and related platforms and there are these online data analytics services the data spaces. We are already open for business most of the services we deliver are accessible through the ESC portal and we will have call for use cases published very soon with the first so-called cut-off date or selection to be later in the spring. Next week we will have a meeting with with Paolo and some of your colleagues from open and access so I think that's will be the the real work where we start the joint endeavor. Thank you. Thank you very much. The last thing was precious and I think aligned with what many of us have in mind but we concrete ideas so thank you very much. So shall we continue with Raul? Yes hi can you hear me? Yes we can. Hello Raul thank you. Thank you everybody and especially Paolo for for putting this together. I am very happy to be here as well. Okay so for everybody I mean my name is Raul Palma. I am working at the Postnat Supercomputing and Networking Center in Poland. This is the largest HPC provider in Poland and I am the coordinator of Reliance Project. This is one of the zero seven projects as it has been mentioned before but we are in the topic of A6 which was about extending the research enabling services in EOSC. So at a glance in short Reliance I mean first of all it stands for this long title but basically it captures what we are doing in Reliance so it's the research lifecycle management technologies for earth science communities and Copernicus users in EOSC. This is what we are doing in a very short title. Now in particularly Reliance seeks to extend the EOSC capabilities with an enhanced support to different research activities through a set of different interconnected services which are quite innovative and in alignment with the EOSC Interoperability framework which actually is a few of the authors are part of our team. Reliance also through the adoption of a holistic research management approach it aims to enhance the discovery of and the access to research data and resource with particular focus on Copernicus data improve the extraction of relevant information managing the research lifecycle while promoting the first and open science principles. So this is of course very much aligned with other projects of zero seven but we are going into a higher level as I will show you in the next slides. So our pilot I mean our project will pilot and demonstrate the services and their value in three earth science communities and we will engage others via some open call with the goal especially to foster the use of Copernicus data and to enhance in general the support in EOSC for multidisciplinary research improving the EOS science as a whole. The priority is it's a shorter compared to the previous one so we are 24 months we have a smaller budget is to two million euro budget but we started together with the others so in in January 2021. So the service portfolio of Reliance is based on three key and complementary technologies and approaches that these are basically what comprise the ecosystem that we are planning to deliver. So first of all we have research objects which is used as the overarching mechanisms to manage scientific research activities and connect associated resources. I will give you a bit more of context of research objects later on but the technology behind this is called ROHA so this has been a project we have been working for several years already and we have over around 3,000 research research objects in the in the repository at this moment. Next we have some data cubes which are basically providing the mechanisms for enabling efficient and scalable access to and discovery of data and access particularly air observation data so in the platform behind this is called Adam which already includes several petabytes of data coming from Copernicus. Then we have services for text mining and enrichment that will allow to extract machine readable metadata from resources in the research object and other researchers for example to discover scientific information at scale structure their own research. The technology behind this or the service behind this is called Kogito from one of our partners in the in the consortium. So based on that we can say summarize the objectives of reliance in the following. First of all when we want to provide a suite of services for the research life cycle management there are based on research objects data cubes and text mining which are in compliance with fair principles. We are aiming to integrate on board of course all of our services into AOS leveraging and connecting with other complementary services that are already available there. We will demonstrate and validate the value of our services through several use cases in real life scenarios. In particularly we have one multi-disciplinary use case and five thematic earth observation use cases that I will also briefly mention at the end of this presentation. And finally our goal is to foster the adoption of Copernicus data and AOS services in such communities to increase the impact of this in the whole European context. So in terms of the project partners the consortium is smaller so we are just nine partners from five European countries. Particularly we have three research communities involved there so these communities are from the earth science I will show you a little bit later about them. We have five technical partners and four of the partners are from the industry and you see in the in the slide the geographic distribution. Okay so being as one of the background technologies in reliance it's important to give a bit of overview of research objects and probably some of you already know about this and we have heard even the word research objects through the presentations in the past. So we started to work with this for many years ago from 2009 more or less in a project called work for forever but this has evolved of course during the years and several branches have started to spread in different directions but all in all we are still having a community about research objects we are having probably also you some of you know this arrow crate community that we are part of of course as one of the initiators of this initiative but research of this is basically a rich information object that accounts and describes and shares everything about your research including how things are related to each other in a way that is understable by both humans and machines. They are of course you can think of them as a kind of logical container that has a unique identifier and that connects different kind of resources that can be for example hypotheses the data that was used the results that were produced the method that you were employing and adopting scientific workflows the provenance versioning information the people that was involved and annotations about all of these resources. Research objects have been used and demonstrated in different communities in previous projects from bioinformatics to astronomy to earth science and as a result they are becoming like gaining more and more attention as one of the promising research enabling technologies. So based on that and having this into consideration in this picture in this diagram we can see a high level view of the reliant service architecture and their connection with AOSC and other existing services. So first of all you can see in the middle we have the services of reliance that are interconnecting and complementing each other and that will enable researchers and scientists to to access all this functionality provided in particularly their work from different interfaces using the research object as the main connecting point. So all of these services will expose some restful API some we will also generate some Python libraries that will enable also the communication with different services in AOSC for example but also the communication and access through some client applications and in particular it's important to know that data cubes are going to be linked in the research objects as first class entities so they will be described with a rich set of metadata enabling the you know not only the access to this data that they are providing especially like Copernicus and so on but also to enable the reproducibility and reusability of these access mechanisms in the future. Then we have all of these services for text mining and enrichment that will be automatically incrementing and enriching the the research objects metadata for example extracting information from resources like the data cubes annotations but also about the resources scholarly communication resources in the research object and and so on. Some of these connections are already in place so you know we are not of course starting from scratch but we of course need to make some adaptations to connect to AOSC as well. And also as you can see in the diagram we are leveraging of course some of the AOSC services from the cross core cutting services but also some advanced services that can be of added value for our researchers. So these also include other existing services like this scholarly communication services you know Jupyter notebooks from like like the EGI notebooks that was mentioned before but also QCG services for HPC management resources and so on. So based on that in the overall picture you can think of reliance as playing a complementary role to what is already in place that is already available. So reliant services the idea is that they will act at a higher level as you know as a bridge between different AOSC services and resources that are already available. So the idea is that they will be able to connect for example from the data that was used by researchers for example the data cubes but also other data in AOSC services or repositories methods that were used to process the data that can be accessed via you know for example the EGI Jupyter notebooks also the research infrastructure that were used to to you know execute all of these calculations or research in general to the results that were published in scholarly communication services and repositories and other open air and so on. But overall as well taking into account the research lifecycle as a whole entity. So for example during the research lifecycle we will be able to create snapshot releases that will increase and make faster the the publication process and for example we were connecting to again repositories like like Zenodo to to deposit whatever is being produced and released and at the end of the cycle for example when the final release of the research is made this will kind of bridge and close the gap from the moment of the data that was gathered and access to the moment of the publication has been released. So very briefly I want to introduce our research communities so we are that we've been validating our services we're bringing three main earth science communities that are working in different aspects and different disciplines. First of all we have the sea monitoring community that is studying the marine habitats and the present past dynamics and the ocean and the interface between ocean and atmosphere. Then we have the this community first of all is represented by CNR East Marine Italy they have a very large community of user community of researchers and they have a lot of connections with others. Then we have the Geohastar community that is aiming to provide and improve the scientific knowledge of volcanic and seismic supersize to support the disaster risk reduction. This community is represented by INGVU also in Italy but they are also being represented as one of the key partners of this Geohastar Super Science and National Laboratory where they are sharing the scientific advisory committee so they are very strong in this community. And finally but not least of course we have the anospheric and climate modeling community that includes scientists working on the development of numerical meteorological ocean and climate models. This community is represented by the University of Oslo the Department of Geosciences. So these communities will be driven the one multidisciplinary use case that will be working on the the impacts on coastal environmental during the 2020 lockdown. So this will be a very interesting thing that will encompass many different disciplines and they will also have five thematic use cases. So overall this will showcase the reliant services and how they can support researchers and promote the cooperation among scientists in earth science. But it's also important to take into account that these services may be adapted to any other research domain. And with that I just finish and thank you very much and of course I am very happy to have you on this. And thank you Raul. I think we better postpone the questions at the end. We also have two parallel sessions for those who are willing to participate. I think it would be really worth continuing on several aspects the discussion if you have time. So we are now getting to the last presentation from Christian. So leave it on the floor, please. Yes, thank you. I hope that you can already hear me. Yes, we can. Here, see you and presentation. Also these slides are theirs and then I follow on. So as a last presenter now I would also like to present our activities within seascales of the Copernicus EOSC analytics engine. We are also focusing on earth observation and have the big ambition to build an easy to use platform to make use of the huge amount of Copernicus data that is available. I'm the CEO of the earth observation data center situated in Austria and I'm also in the role of being the project director of seascale. Yeah, within the consortium we have a number of partners. I will present them afterwards in one of my subsequent slides. What is our problem statement? So the European Copernicus program has really established itself as a predominantly predominant spatial data provider in providing more than 10 of terabytes of data per day that basically gives insight in the current status of our earth. Currently, we don't have any single European processing backend that serves all the data sets of interest towards the scientific community that really hampers at the moment the use of the data and makes it really complex. Either you use some of the U.S. services where you maybe have also quite a number of limitations and therefore our and also maybe concerns to use them. And therefore our big ambition within seascale is to provide a big data analytics federated infrastructure with with cloud computing and storage architecture in order to really quickly use and analyze the long term archive that needs to be established for the Copernicus data that we all require. So therefore we will set up seascale in a manner that we integrate it with the help of several researchers and institutions over Europe to build up this federated infrastructure to provide this infrastructure within years so that scientists can make use out of it and enable state-of-the-art research towards subsequent use of observation data for other scientific disciplines for strategic European decisions, facilitating the European Green Deal ambitions, facilitating also the new initiative from the Commission called Destination Earth where basically a digital twin of the Earth shall be established in order to analyze processes on the Earth's possible future influences and looking at and compare the current status, this past status of the Earth. So that's where we want to contribute. So the high level of objective of seascale is to integrate this federated computing and data platform into EOSC. We will include the users from the very beginning in order to set up a system that is really perfectly fits to their needs. So we will have an architecture blueprint, we will have a constant onboarding process to know new users but also to new service providers so that this federation really also goes beyond the project partner. So that's really one of our goals. So we will not limit ourselves within the project. We want to set up something where others can contribute from an IT perspective, from a data perspective, but also from a user perspective. Yeah, so where did we start? We had a look on the current situation in Europe. So we have the diocese that have been established by diocese projects that have been established by the European Commission. We have national initiative so-called color drift ground segment nodes and other activities. And on the other hand we have the infrastructure services that are well presented within EOSC. And our idea is to federate these two groups towards a large scale infrastructure and really bringing together the expertise on one hand from the EOSC sector, with UDC, Dildares, Vito, Calcfaro, Tiovin, Zesnet and Gionet being involved in the project, but also with infrastructure providers. Some of them are identical but we haven't reached the consortium by EGI as an important player by NFN, SurfSara, and also INCD. Gionet and Zesnet are basically acting on both sides already. And the aim is really to tighten the EOSC sector with the EOSC and the infrastructure sector in a very close manner. So that's the big C-scale ambition. How do we or what will we provide? We will provide this in EOSC data archive consisting of current but also historic long-term data sets from Copernicus and other satellite data. We will provide compute services which means on one hand cloud environments but also HPC services that can be used for the analysis of the EOSC data. And we will provide an analytical platform on top of these resources so that an easy deployment of solutions and use cases can be performed on top of this federated activity. Yeah, all these services will be integrated into the EOSC portal with the ambition to do this somewhere mid next year so that everybody can book these services and can make use of these services in these scientific questions. Yeah, everything within C-scale is significantly built around the use cases. So we have defined six use cases or use cases already within the project so that we have the users basically on board and they drive the development but we will also onboard other use cases within open coal where we also provide virtual access and free infrastructure costs for them so that even the use of the platform will be significantly widened in respect to what's also new ideas and new research communities. Yeah, the idea is really to validate and optimize C-scale during its development phase towards supporting an agile approach, getting user feedback immediately considering their feedback in their current development. So that's one of the ambitions. Yeah, the solution should be really cloud agnostic, independence of commercial closed and non-new providers so that's what we want to achieve, cross and interdisciplinary exposure so we don't want to see Earth observation and the use of the Copernicus data just in a limited field. We really want to make it as accessible and this access should also be done in a fair manner. Yeah, in the following I just want to present you three of the use cases so that you get an idea of what shall be possible. The first one is the aqua monitor that is currently running on the Google Earth's engine in a quite successful manner. We want to transfer this towards EOSC and the infrastructure and data that is provided between C-scale. So that's one of the big ambitions that are around to move that from the Google Earth's engine towards EOSC and having that around. Yeah, the second one is water watch, a near real-time update of the surface water resources, so lakes, rivers and wetlands. Also here we want to have the real-time monitoring available within C-scale. The third one is then high sea, again about water that's maybe also related to the significant involvement of deltaras, but instead of the monitoring of the water areas it's here now the big topic of water quality at the seas. Again here we will require a huge volume of data. We need to have a lot of computational capabilities in order to discover monitoring of that high sea activity. Use case number four, five and six I don't present in detail in order to keep the presentation short. So high resolution land surface analysis that's within the high-res LSTA use case. The big topic, the second use case number five is the return use case from the University of Wageningen is focusing here on the monitoring of tropical forest areas with the help of multispectral satellite data as well as radar satellite data and last but not least the virtual European Sentinel data cube where we want to provide a new access possibility to higher level Sentinel data that then can be directly used for the implementation of other use cases. So that's the six use cases that are already fixed. As mentioned we will also provide a number of virtual access resources from different providers so that's the overall numbers we will have more than 1500 CPU core hours a year. We have significant HPC resources and we have more than a petabyte of storage that we will offer towards users that they can book and that will be provided by this virtual access mechanism. Yeah to sum up already so the big ambition is to federate the infrastructures with EO data, data services that are around and infrastructures that are around and to make really Copernicus resources easily accessible towards research areas and the EOSC in general. We will deliver this federated infrastructure services so the data, the compute but also the analytics service that we have presented that shall all be accessible to the via the EOSC portal. One important factor for us is that the federation will be co-designed with the researchers so they will be involved from the very beginning in the setup and we will make this environment then available to others via the virtual access mechanism that is provided in the call option and yeah we are really looking forward in order to implement this C-scale idea. Yeah then I already thank you for your attention here you find the contact information so this info at cscale.u you can get all the details you can also register and ask for the questions there we are currently setting up the webpage and that's still under construction but also will be available soon to the basically whole world so that we can inform people about our C-scale activities there was a Twitter hashtags around the C-scale in order to receive updates via social media. Yeah with this I close now really thank you for your attention and I'm happy to receive some questions however I need to leave in five minutes latest. Oh sorry I was muted thank you very much. So I think there is a lot of material and very interesting material as I anticipated so I tried to take some notes trying to share them now with you okay can you see the slide? Yes yes okay so in some cases this has very personal notes so you won't find what I need to buy for my refrigerator but some of the things that I surely would like to discuss with you so do you first of all is there any questions for the speakers? Things that you'd like to be clarified or that are not clear enough okay so from your presentations I see several possible collaborations bilateral in some cases which can be extended to a more general purpose approaches so this is the second bullet that came up to my mind so we can of course consume each other's resources right especially when this is a specific action like data storage or computing provision then one project where this is not already the case for example EGI is part of reliance one project may benefit of the resources of another so you can apply for the tenders you could do the actions that are necessary for that but the second point is make our services interoperable okay and I see many opportunities here one is bilateral which I think is interesting of course because we could benefit from each other's services but it's the one that I less prefer in the vision of the years so I would like for example any interaction between two services across our project to be driven by the broader mission of defining protocols that would allow other similar services to perform the same interaction so on this respect for example and this is a question for DICE and the EGI years I see an opportunity there for you to exchange for example the results of your processing in EGI for all the use cases that you have to be fully integrated with data publishing and also with what we're providing in open air so the overall publishing in the broader context so what do you think what's your opinion in that direction wants to start Deborah maybe yeah yeah I was thinking more or less along the same line this morning when I was hearing all the different presentation on the open air services so for sure one one possibility is to rely on the open air services for the publication what comes from the DICE services or from the computing I'm not to talk about EGI but he can speak for himself but as a general picture I think that would be very interesting and would provide a complete set of services and from the data processing data creation data processing storage and make them available to the public across the three project at least maybe involving also the first thematic issues but for general purpose I think in general purpose services I think the three project can find a nice solution for for user communities yeah yeah I agree yeah that's just a kind of analysis where I think we should yeah I mean yeah then we we should make a technical analysis I agree but at least in in in principle I see it a nice has a nice idea so would you agree on the fact that we should aim at more general purpose frameworks so going towards rather than bilateral integrations from broader yeah then maybe the general purpose framework will lead to some bilateral work and bilateral integrations but use cases yes would be bilateral with the expulsion of applications of this but I think this is the best we can do for the years in general right so the more we do it the better so we we have I like to hear we're all aligned on this kind of perspectives I'm asking also to the colleagues from C-scale and reliance if they want to mention you want to have a voice on this yeah hi just easy role well regarding then from my side of course I see a lot of potential collaboration and you know reuse of different things that other of the projects of 07 are doing for for the one hand as I tried to show on the presentation I think in our case we want to you know leverage existing data sources data repositories like the ones from v2share or some others that may come from from dice but also repositories like synodom that is coming from open air nexus and on the this is also the computing infrastructure like you mentioned the dji jupyter notebooks for example this is very important for us as we are planning to use this kind of environment as the default computing environment for the research object let's say so we want to create some kind of libraries pattern libraries that will be able to access the resources in the research object and do whatever you do in your in your library but in your notebook but then you can always come back to your research object and then after that of course we have the part of the publication site like I mentioned this is very important as well so our research objects I mean we have our platform but what idea is that we can actually publish this in some of these existing scholarly communication platforms and this includes of course again synodom because it's very popular one so for example the idea now that we have is whenever we are creating some kind of releases of the research object that we have like life cycles then we we will have the possibility to release this also into synodom so we will just be able to deposit whatever the user was the researcher was working on the the team of researchers were working on the research object as also one entry in them in the synodom and this will be able then to we need to further discuss this and we are in strict contact with cattle gobble on these kind of topics on how to nicely and to the point integrate research objects in synodom and in here because I think it's a key aspect of your work as well so it's good that this closes the circle in a way Christian from this scale uh paolo christian wrote in the chat that he had to leave okay yes he said five minutes sorry I should have asked him first okay so we now have two parallel sessions I hope many of you will be able to stay to further discuss these aspects because it's really important for us to receive feedback can I share my screen paolo so that the participants can see the the different sessions no as you can see they have two different connotations one is more on uh nexus services in the national setting so how can we make sure that our services are useful are useful at the country level to support the uh dissemination adoption of take improvement and channels regarding open science in general open science practices and this has a regional say national perspective because uh open air has representative at the national levels which are trying to cope with the different maturity level and different expectations in terms of technologies road maps which the national level are different so what we would like to discuss is to how to serve these people uh which are helping the open the open science dissemination in the best way so this is the first session let's say the other parallel session instead is more related with research communities and the rise so how the services can be better customized to serve the needs of research communities and the rise and that's uh of course in collaboration with other infrastructures in collaboration with the research communities etc this is this has more a more technical again um bias but still uh policies are in place uh to the point that we can uh uh flexibly adapt to them and understand what they are at a community level it's a different level of customization we'll say uh so we have two rooms uh how can we access these rooms uh Paola the first one for no words I think they already have received uh an email well for for registration so as it's a closed session um it's um we shared via email the link for registration so they maybe have just already received a reminder as for this session on research infrastructures you will stay here in the same in the same room okay so sorry for the the missing this uh the time I I get it wrong because it's 50 okay it's it's happening now we we won't have any any breaks so for the ones for the no words we want to to move to the other session please check your email um for the reminder of the maybe you can maybe you can paste here the link to the other the link for registration yes yes I can pass or no or the link oh yes yes you need the registration otherwise yes yes for zoom yes


What's up guys? Today we have an epic opening of Champion Pack 3. We have 10 packs. These are not heavy or light. I bought them on wade, so the chances are pretty low that they actually have a foil in them because it's about one and 12 per pack anyway. But we're going to try and get one. The foils in this set are insane. They're super valuable. But before that, the giveaway. I'll be giving away these three cards. You have an original Nobleman of Crossout, Insect Queen's Secret Rare from the 10, and a Horus Secret Rare. That's all you got to do. Like the video. Be subscribed and let me know your favorite card from Champion Pack 3 or any of the Champion Pack sets. Alright, let's get into this. We have 10 packs. So the cards we're looking for, you can pull Gravekeeper Spy. You can pull Spirit Reaper. You can pull Sniper Hunter. You can pull all that stuff. The Ultra Rare in here is not as valuable. The Magicians Unite. We have actually opened this up before you guys can check that out. It's a pretty nice set. We opened up all heavy packs this time, so I got a ton of different foils. It was really cool. So this time I bought these from one of you guys. So maybe we'll get lucky and pull one foil. The chances being one in 12, not necessarily unweight. He said they were, but you never know where they came from or what the guy before him did or whatever. But we're just going to try it out. There's only three cards per pack. We can also pull the DD Assailant as a Rare. So that would be a nice pull as well. I think it's worth like $8 or $9. So let's go ahead and open this up. We're only going to have 30 cards in this video because there's three per pack. So I think the foil is at the front. So let's try not to spoil it. We'll figure it out on this first pack. I've not opened Champion Pack in a bit. So we used to open a ton of these, but they're pretty rare now. Pretty rare, pretty valuable. The foils are pretty expensive. Let's see if it's, okay, it is backwards. Let's see where the foil is. Is the foil or whatever, the rare or whatever is it on the back? Okay, Necro Valley. It's actually a pretty nice comment. So let's see what we can get in here. Necro Valley. Kaiba Man is a common. You're not even, no, you are guaranteed a rare in Champion Pack. You're not in Tournament Pack, but you are in Champion. The Agent of, the Agent of Judgment Saturn. Not the Agent of Saturn. So that is a rare. So we'll sleeve that up because it is a Champion Pack card. Still a nice card even though it is a rare. So what I'm hoping for is one foil. One foil does us really good because the Gravekeeper Spy and the, the Spirit Reaper, that's very expensive card. So hopefully we can pull one. The chances are pretty low though. Pretty low to find unscaled Champion Pack. So we're going to try. All right, one pack down. Hope you guys enjoy this old school opening. Yeah, we're going straight into the old school. We've been doing some old school box breaks, but I personally haven't been able to open anything old school since I think the LOB kind of thing. If we open anything since LOB Booster Box, that was personally my, I think it probably was, but it hasn't been as much. So okay, that goes to the back. Here we go. A Feather of the Phoenix. Fairy draft. Isn't this, wait, this might be a decent card. I think this is a decent card. One sec. Yeah, this card's worth like a couple of dollars. So that's actually a pretty good common to get and DD Assailant. So that's the best rare in the set. So a nice common and a nice rare. So a pretty good pack overall. Check these out. Champion Pack three. Always going to pull some good cards. I've never pulled a DD Assailant because when we opened the, or I've never pulled it out of Champion Pack, because when we opened Champion Pack three, we only opened the heavy packs. So this time we're opening some unweight. So we actually get some cards we didn't get. So Feather from the Phoenix. All right, so we got the best common and the best rare in one pack. So that's pretty good. So now let's try and get a Super Rare. Even if we get the worst one, I think it's Dark World Lightning. It's still worth like $50 or something. So still a good, a nice card to get. I wonder actually, I think it's the worst. And then Magician's Unite is actually after that, even though it's an Ultra Rare. But that's still a really cool card. Magician's Unite looks really good. So this card, this is ripping up really weird. Let's see if I can get these out. Okay, good. Let's put this to the back. These are very glossy cards kind of on the back. The front is pretty normal, pretty matte. You can see it. Okay, Contract of the Abyss. Another Fairy Dragon. We'll take that and Gold Woo Lord of Dark World, a nice rare. It's pretty cool. The Woo Lord of Dark World. And then we got, of course, the Fairy Dragon, really good. We will sleeve that up because it is over $2. It's pretty solid value for a common. All right, we still have seven packs. So we're taking our time a little bit because we have less packs, less cards to see, stuff like that. So we're not going to try and speed through these. Oh, I didn't mean to do that. But this is going to work out fine. So let's go like this. I have a ton of these still light packs. I still have a ton of them. These could or could not be light, but the other ones I know are light because we scaled out the other heavy packs when we opened them up. So here we go. We have a Contract of the Abyss. Chiron the Mage. It's a nice card. I remember I used this in a pop of corn deck and dueling a couple of years ago. It was actually really good. It was really fun. Another Gold Woo Lord of Dark Lord. A dark world. Okay. Yeah, we're falling apart here. Nice. Okay, nice rare. Not a foil, but that's okay. Chiron the Mage. So far, let's look at the variety of common. So not too much. There's a lot less cards in these kind of sets because they obviously only give you three cards per pack. So I'm not going to have like 200 cards per set or whatever. Okay. Here we go. Finally. That was a very, very strong one right there. Here we go. Wild Nature's Release. Wait, have we seen that one maybe once? BES Crystal Core. We haven't seen that one either. DDS Salen. Another DDS Salen. That's pretty good. It does have a little nick at the top, unfortunately. Still a pretty nice condition it looks like, other than the very top. So yeah, hard, maybe not a near mint because of that. It is close though. It's pretty close with just that nick, but that would be like a near mint. If you sold as near mint, you would need to disclose that it's a nick to the top. Okay. Five more packs, halfway through. No foil. Kind of expected. I mean, it is very, it's very unlikely to find an unweight champion pack, but we're going to go for it anyway. We're going to see if we can possibly pull something. Oh, okay. There we go. Three cards. Necro Valley. Here we go. Grave Keeper's Cheap. That's the first time we pulled that one. Let's pull, let's pull a nice spy. Let's just do it. Pikachu's Circle of Enchantment. The trap. Ew, not the one we're looking for. Oh well, we did get a couple Grave Keeper's cards. Nice. The Necro Valley's are nice. They're probably worth a little bit. Four more packs. Champion pack. Can we pull? This would be one of the more exciting champion pack pulls, because in the other ones I knew I had foils. I've never pulled a champion pack foil when I didn't expect a foil. So that would be pretty exciting. I have done it with Turnip pack. We've had some unweight packs there, but we've not done it with champion pack. Fairy Dragon, nice start. Another one. Wild Nature's Release and Widespread Ruin. Okay, a different one. Widespread Ruin. Pretty cool. This was originally a game, not a Game Boy, but a Game Proma. I don't know if it was a Game Boy Proma or not. I can't remember exactly which one it was. No, it was the Xbox. Was it in Dawn of Destiny, I think? Yeah. So these champion packs were given out during tournaments. So if you're playing in a tournament at your locals, they were given out. Champion pack three was probably around 2007, something like that? Maybe. I'm just guessing, completely guessing. I think CP01 was, it might have been earlier than 2007 actually. Think about the cards in here. Let's see. Gravekeepers. Hmm, I can't remember. It's something like that. I'll probably try and pop it up on the screen so you guys can see it. All right, we have a Gravekeepers chief, a feather of the phoenix, and another DD assailant. So we're not pulling any foils, but we will take the triple DD assailant. That's the best we're in the set. That's a good one. All right, two more packs of champion pack three. Can we get some good? All right, don't forget to do the thing and ruin it. All right, perfect. Oh, that one was nice and clean. Nice and clean there. That one's got some stuff on the back. Watch this will be a foil. Watch this. I'd still take it though. I'd still take it. All right, we got Kyra on the mage. Wild nature's release and hit the like button for luck, guys. Okay, it's just peekaroo. Just peekaroo. It's fine. Just a peekaroo. That is not a big deal. Okay, we can't get the sliver. There we go. Okay, final pack. Final pack magic. Can we pull something good? Likely we bought a bunch of light packs, but that's okay. It was a good time. It was enjoyable. Maybe next time we'll get something good. All right, here we go. Final pack. Gotta take the risk to pull something epic. Here we go. We have the Kaiba man. Haven't seen him since the beginning. Is that a good sign? Come on. Necro Valley. Nice pull. Here we go. We Lord of Dark World. All right, all rears. As expected, but that's okay. It was a good time. If we had pulled something, it'd been super exciting, but we actually pulled pretty well, I think, for the rears. I mean, we pulled three DD assailants is really awesome. All right, so we really didn't get too much, but we did get three fairy dragons, which were worth a couple bucks each, and then three DD assailants. So we definitely did not make our money back on this for sure. But we did get some nice cards out of it. Also, if you guys are interested in the light CPO three pack, one that has been weighed and there's not a foil in it for sure, and you guys can hit me up. I do have several CPO one, two, three, four, and five packs that are all weighed light.  But if you want them for your collection, hit me up. So that was a fun opening. Maybe next time we'll get a foil. And if you guys enjoyed the video, make sure to subscribe because we are almost at 60,000. We are really, really close. If we hit that, we'll open up all the 2005 tens in one video. It's going to be insane. So thank you guys for watching. I'll see you guys later. Peace.


We were home playing and I looked down and realized that he had more bruises than usual on his legs and His torso had some ptiki eye So I took him into the doctors and they had labs drawn and they called me the next day And I knew when the doctor said that his labs were remarkable There was a problem and the next day we found ourself at Maine Children's Cancer Program and he had a diagnosis of aplastic anemia And so essentially that meant he had bone marrow failure river had very very low platelets and That meant he could not play in the usual way that an almost three-year-old could So we had to put the bike downstairs We didn't get the swing set that summer. He has a metaport and that is how He has blood draws essentially he had a lot of blood draws They were doing in the arms and it was becoming traumatizing for him. So for children in his circumstance, they put in an abort And that's when Greg came in. That's when we received home health services when I first met river He was in a pretty scary situation for I think at the time he was three his blood counts were very low His platelet count was really low and his red blood cell count was really low I think his whites were also quite low. So when all of those things happen For red blood cells you lose your energy you lose kind of the color So he was very pale and having a bit of trouble with energy, but also Because of his platelet count his platelet count being low he was susceptible to bleeds Bruising you know kind of like spontaneous bruising and stuff like that So he was pretty fragile when I first kind of came into his life I would say it was stressful traumatizing in some ways We couldn't go to some birthday parties because his white blood cells were so low. We didn't want him to Have an infection So and then he couldn't play with children in the same way as far as running around and Tumbling and bouncing and we just it felt like we put him in a bubble for a little while That's what it felt like. So Greg came in initially weekly or sometimes twice a week to check on River and Access his port and draw labs so we could see what was happening With his red blood cells white blood cells and platelets a big part of our routine was going to be drawing blood every day and certainly This was an uncomfortable thing for River to have a needle placed so that blood could be drawn the medications that he was on Had some not so great side effects You know, he was also on some steroid treatment. I think at one point Which made him a very moody young man Greg's been with us for two years and he's here on time on a regular basis taking good care of River having fun with him For kids of this age I think it's so important to turn a medical visit into something that doesn't feel so medical when your heart You is just overwhelmed with grief You need somebody to step in professionally and help care for your child and your family and that's what Greg has done for us It's the key to to working with kids is to try and work with that anxiety around what has to happen so that That doesn't become a big obstacle And try to maybe use it to your advantage even sometimes River today is in remission There's there's conversation about taking out his port, which is really exciting And he's able to play which is what you saw today. He's so full of energy and life Laughter River's future is open to him and I'm very excited for him. I just really want to emphasize how grateful we are for home health visiting nurses And exceptionally grateful for Greg. I cannot say enough kind words about him We count our blessings every day and Greg's one of them You


Hello everyone and welcome to the Talk Spectra, which is about new wireless escalation targets. This is a joint work by me, Jiska and Francesco, who has been working a lot with Wi-Fi, while I have been working with Bluetooth in the past. And in this work, we join our abilities to build a new attack scheme. So the motivation of this is as simple as this. I found a partial Bluetooth RCE a while ago and then a bit later, a student of Mein Jan built a fuzzle Frankenstein which emulates the Bluetooth chips and he also found a couple of more remote code executions. And with this, I said like, yeah, that's a great chance. Now we can tour the world, tell everyone, like we have Bluetooth remote code execution, take my unicorn, travel with it and show everyone. But the thing is that people said they are not too surprised about Bluetooth remote code execution because, you know, Bluetooth after 22 years is really indistinguishable from magic and they kind of expected that it is broken. And then people also told me, you know, there is Bluetooth RCE, there's Wi-Fi RCE. And Wi-Fi RCE is much cooler because, first of all, Bluetooth, it's connected via UART and Wi-Fi is connected with PCI Express that it's just nicer for exploitation. And also, if you can pop Kalk, it's a nice attack, but if you cannot pop Kalk, then what kind of attack is a Bluetooth on chip remote code execution? So I was thinking because now the idea is, of course, like I could try to, like, take the Bluetooth RCE and then break into the operating system all the way up. But another funny attack would be to instead attack the Wi-Fi chip or maybe even the LTE chip. So to break the interchip separation instead of doing the same thing again of breaking into the operating system. And then I called Francesco and said like, hey, let's build speculative transmission. And the idea of the attack was that in a smartphone, you have the same frequency used by Wi-Fi and Bluetooth and LTE has harmonics in the same spectrum. And they cause interference in such a small device. So they need to arbitrate the channel access, which means they need to actually tell I'm sending a packet, can you please not send a packet right now and so on. And also need to tell priority and so on. And this is called a coexistence mechanism and it's a performance optimization. And of course, you could now also instead speculatively transmit a packet and use this to infer what the other cores are doing. So this was the initial attack idea. In the end, it turned out to be a bit more of a spectrum transmission, but this is the attack scheme. Of course, it requires a lot of exploitation before. So it requires the Bluetooth remote code execution or Wi-Fi remote code execution to then escalate into the other chip. But the interesting part here is, as this is a connection directly between the chips, you cannot plug it with the operating system. So there is a very nice attack vector that is hard to prevent. And if you look into a modern iPhone, this is what it roughly looks like. So you have the Bluetooth and the Wi-Fi chip, which are within a combo chip, but they still run on different ARM cores. And they are connected via the serial enhanced coexistence interface. This is what we are going to attack. The combo chip is also interconnected with an LTE chip. And this is using mobile wireless standards. And then you can also see that the Bluetooth daemon has fewer writes than the Wi-Fi daemon. And the Bluetooth chip is usually connected with UiD. The newer iPhones use PCI Express here. And now if you could escalate between the chips, you have newer text paths that become possible. So for example, I could now start from Bluetooth over the air and then escalate into Wi-Fi and then go all the way up. Or I could also try to infer timings in between those chips and so on. The spectra impact can be very different depending on how this coexistence interface is implemented. So first of all, the most obvious one is the denied of service. If one core denies transmission to another core, but it could also be information disclosure via timings or packet types and so on. And the worst case would be code execution.  When this attack has been first on the internet because of the blackhead abstract, someone started tweeting and giving it other names. And I have to say I also like the clear goals attack, but spectra is like the original name. Of course, it's harder to find this on the internet because spectra is just a very generic word. And now let's go for the Broadcom coexistence interface, which we are now going to exploit. This is also present in a couple of Cypress chips because Cypress acquired parts of Broadcom in 2016. So it's synonymous to be used here. So don't be confused if I mix up Broadcom and Cypress. It's all the same. Actually Broadcom is a very nice target because they don't do any firmware checks. And no firmware checks means that if we are able to reverse engineer certain parts of the firmware, then we can also patch it within Wi-Fi and within Bluetooth. And there are no further checks, which means that there is no secure boot, no signature checking, etc. So you still need to understand what is going on to patch such a chip. But then there are no further security measures to prevent this. And those chips are in many, many, many devices. So for example, all iPhones or MacBooks, IMAX and also the older Apple Watch system just wants to have a different one. The Samsung Galaxy S series, the older Google Nexus phones or Raspberry Pi is a couple of IoT devices and so on. So this is a very nice prototyping platform for all kinds of attacks. If you look into the older data sheets, you can also find a couple of data, still not everything, but the new data sheets just don't exist. So we need to live with what is there, what is documented. And what you can see here, there's this Bluetooth chip, there is a Wi-Fi chip. They share an antenna, so they need to arbitrate access onto this one. And then there is a lot of stuff going on between those chips, which we are going to attack in the following. Nonetheless, they have different ARM cores. So this one has an ARM Cortex-M3, there's the Cortex-R4, and so on. So this is still separated in some ways. For understanding the attacks, now we need to understand the serial enhanced coexistence interface, which is used between Wi-Fi and Bluetooth. It's also called ECI, so without the serial and GCI which might be global or generic coexistence interface. But it's all used in the same way in the data sheets. To understand it, the best way is to actually separate Bluetooth and Wi-Fi. And in this setup, you can see that there is a Bluetooth and a Wi-Fi board by Cypress. They don't have a shared antenna, so everything is separate. There are no side effects, and the only connection that they have is the serial enhanced coexistence interface, which we can now also intercept. So that means that we are actually able to observe each and every signal that is sent between those two boards. And there is nothing else that is going on that could block a transmission. If you look into this in detail, first of all, we did the experiments of streaming just some music over Bluetooth. And then on the Wi-Fi chip, we did a scan for other Wi-Fis. You can see a peak when you start the scan. Actually, it's two peaks, and then there are a couple of other peaks when you get the scan results and the end of the scan. And what is very interesting about this protocol already at this level is that the Bluetooth and Wi-Fi are sending with three mega-bolts over the serial interface. And three mega-bolts is also the same amount of data that is sent from the Bluetooth chip to the host to send the actual music of the stream. So you can imagine how much data there is within the coexistence interface. Now you can see that Bluetooth is within each peak actually sending some data that is annotated in hex here and also Wi-Fi is sending some data. So each tiny peak there really has some information about the task that is running and other stuff that has priorities of packets. And in the last example, you can also see a Bluetooth keyboard, which has regular peaks that is then being sent by Wi-Fi as idle. So this is roughly what it looks like just to give you some idea about this protocol. In the first attack, we didn't even need to understand all the details of this. It's just a simple reconfiguration of this interface. So there are a lot, a lot, a lot of registers that are mapped into the Bluetooth ARM core that you can write into or read from. And actually I tried to understand all of them in the very beginning and you can also do fancy stuff with this. But I didn't understand all of them and then Francesco just told me, well, if you don't understand it, just try breaking it, just write something in all those registers and see what breaks. And I found out when I write just apps into the CCI chip control, this crashes Wi-Fi. And more interestingly in this evaluation board setup, I could even see some voltage drop on the logic analyzer. This was very weird. And on some devices, this even causes a kernel panic because upon writing to the CCI chip control within Bluetooth, Wi-Fi might stop or even spam stuff over PCI Express and so on. And then there are very weird effects from this. I tested it on a couple of devices, so starting from the Nexus 5, but then also going all the way up to the newest MacBooks and iPhones and so on and the Samsung Galaxy S10, S20. And what you can see here is that, first of all, depending on the date of the chip, you have a slightly different scheme. But on the newest ones, you just write apps into one address. And already this is sufficient to have a kernel panic on a lot of those devices. On some of them, it's also just Wi-Fi that restites and that's it. Now, this already looks very promising for such a simple attack. And because of this, we try to build more fancy attacks with this primitive. And this is what Francesco is now going to tell you about. Thanks, Giska, for introducing this part of the talk. Let's start describing the Broadcom Wi-Fi chipset. In the last two decades, it evolved from a soft Mac to a full Mac implementation and functions that were originally running on the Linux host at the top are today offloaded by an intermediate ARM core. Interestingly, low-level operations are always managed by the same piece of hardware that did not change much in 70 years. No matter which Wi-Fi chipset we are using, time-critical operations are managed by the same D11 microcontroller that coordinates five radiofrequency and DMA operations. Let's have a closer look to the low level. The D11 microcontroller runs the microcode, a short piece of software that keeps checking hardware conditions and triggers specific operations. We see here some code from the main loop that checks if the PHY started receiving a PLCP prehambl or if the current reception is terminated. In such cases, it will execute the corresponding handlers that will decide what to do with the current flight. This other piece of code is extracted from the part that schedules the transmission of an acknowledgement. We see the preparation of the reply frame that starts with D4 as usual. The D11 toolchain was created by Michael Buetsch in 2007. We incorporated it inside our Netman project and we periodically updated it by adding new instructions when a new chipset is introduced. As spotting the U-code in the ARM binary blob is easy, we can modify it to adding customized parts as we will see later. The D11 CPU coordinates many blocks. First of all, it controls the transmission and reception engines. It manages channel's access by scheduling transmissions and decides which received frames should be pushed to the ARM core. It can configure the PHY and the radio and it does so by running the U-code that is loaded into the U-code memory by the ARM firmware during initialization. The D11 has access to an eight kilobyte shared memory where it keeps its configuration and state variables. And it also accesses indirectly the ARM memory where packets ready for transmissions are queued for deciding which packets can be transmitted or aggregated. The D11 is equipped with general-purpose timers and with many different interfaces for talking to other parts of the chipset like the second interface. During the years, it turned out to be a pretty flexible architecture and we used it as a research platform for showcasing operations like jamming, piggybacking schemes and time-off-light measurements. Let's now talk about the D11 coexistence interface. It includes quite a number of registers and a 64-bit buffer for receiving messages from the Bluetooth. Such messages are transmitted by Bluetooth every 1.25 ms, that is the minimum Bluetooth connection interval. They report to Wi-Fi the timing and type of all Bluetooth operations. Wi-Fi copies this information inside dedicated, shaky countdown timers that defer Wi-Fi operations and prevent collisions. On the opposite direction, Wi-Fi uses the Bluetooth transmission control register in red for granting Bluetooth access to the chat. The flow of messages in the two directions builds a grant-reject scheme. As we will see, in our attacks, we use the knowledge we collected on such registers for breaking such scheme. According to our analysis, more than 10% of the U-code is dedicated to coexistence. As in general, many other operations take much less code, we understand how much complex is the coexistence interface. Finally, by programming two boards for transmitting SEKI messages when receiving the same Wi-Fi beacon, we measured, with the help of an external FPGA, the jitter of the SEKI line. It added out to be Gaussian with 200 ns deviation, which is perfect for this application. So let's see how we broke the grant-reject scheme. We did that to see the effect when watching a movie that requires to download content over the Wi-Fi and send audio to a Bluetooth headset. At the bottom, in green, we see SEKI grant messages transmitted by the Wi-Fi. Bluetooth uses them for understanding when it can transmit audio to the headset. We introduced it into the U-code a few lines for configuring the Wi-Fi chipset remotely from the air interface. We can hence prevent the Wi-Fi from sending SEKI grant messages to Bluetooth. You see this happens between 2.6 and 3.5 seconds. During this interval, no more SEKI messages are transmitted, and in fact, we cannot hear any sound from the headset. We tested this both on an AXUS 5 and on undevelopment boards from Cyprus. This experiment clearly demonstrates that a denial of service attack from the Wi-Fi side against Bluetooth is possible. Let's take a closer look now at the messages that Bluetooth sends to Wi-Fi and if we can use such information for an attack. These are the SEKI time diagrams when we have a keyboard connected over Bluetooth. Depending on the keyboard, we can observe SEKI messages transmitted every 15 or 30 ms. Bluetooth sends these SEKI messages to inform Wi-Fi that it is going to pull the keyboard so that Wi-Fi, the first channel access, mean Y. In this diagram, Wi-Fi is idle, so Wi-Fi always grants access to Bluetooth. This is what happens when somebody is actually typing on a keyboard. At the bottom, we have the periodic sequence of SEKI messages. On top, we have the key presses sniffed by Wireshark when capturing from the Bluetooth interface. As we are typing with moderate speed, each key press is separate from the others, and we can also see the Bluetooth message with key release following each key press. In between, we can see the HID data captured by Wireshark with the specific event ID that represents a key press. Below, we see SEKI messages that we filtered on the Wi-Fi chipset by selecting the same message type. This demonstrates that at the Wi-Fi side, we can easily distinguish SEKI messages related to key presses. This clearly demonstrates that having access to the Wi-Fi chipset is enough for measuring key press timings with very accurate resolution. And we know that, in some cases, with the help of some artificial intelligence or classification technique, this is enough for guessing what a user is typing. We hence believe that without any further protection, the SEKI interface can be used for mounting side-channel attacks. And we requested the CVE for reporting the associated vulnerability. Cisca, the ground is yours again. Thank you Francesco for the very detailed explanations about the Serial Hearts coexistence interface and attacks on it. There is still one thing mentioned in the datasheet, which was clearly missing, which is the WLAN RAM sharing. And in the following, we are also going to attack this. I would call this effect when you spend too much time looking for very fancy side-channels and dig deeper into all of this and try to explore them. While there is the one obvious thing in the datasheet that you just couldn't find within the Serial Hearts coexistence interface. And for us, this was this WLAN RAM sharing. So it must be somewhere. It's in the datasheet errors just go into one direction here from to Wi-Fi. And we just didn't understand where it is and couldn't find it for quite a long time. And the reason for this is that the Cypress boards come with some development kit. And within this, there are some symbol leaks, but the problem here is there's nothing mentioned with WLAN. And so there probably is no WLAN RAM sharing, I thought. Maybe it's just another word for the enhanced coexistence mappings. But then there was also another part of symbols and I was able to obtain a ROM image. And it's not from a development board, but actually from a MacBook. And within those symbols, there suddenly were a few called WLAN buff something. So it looked a bit like probably the shared RAM, but it were just functions. And then I analyzed those functions. And there was one function that was pulling somewhere in the 6800000 region. And actually when I saw this, then I tried to read it. It sometimes crashes if you don't do it in the right order and so on. But in the beginning of the section, I actually saw, wow, there is a string 802.11 something on the device where I did this. And then I was like, probably I'm already in there. Still to confirm it, I instead write writing to it. And when I write to this, what happens is that quite often the Wi-Fi crashes. So within Bluetooth, I write into those registers and suddenly Wi-Fi crashes. And a nice part about a Wi-Fi crashes is that on a couple of devices, this is causing a crash dump. And this crash dump actually contains parts of the ROM image. So I could write data that I know and try to find the same data again to make the mapping and find like how Wi-Fi and Bluetooth are mapped into each other. And also it revealed a couple of pointers, function pointers. So within the function pointer table, I was just overwriting a couple of pointers. And it turned out that within this position, there is a pointer table. And when I write to this, I can get the program counter under control. So I can write to ROM, I can set the program counter. So I can have code execution. And that was really amazing. I have a demo video for this on a MacBook. The mapping is slightly different. So on the left-hand side, I use internal clue to write assembly instructions because I'm just writing within a function and not within a function pointer. And then on the right-hand side, you see the Wi-Fi crash logs on macOS. And you can see that I can get the program counter under control. And this is how fast this attack works. So just within Bluetooth, I can get code execution in Wi-Fi. The interesting part here is that I couldn't find this area on the Nexus 5. So either it's not mapped at all or it's mapped to a different region. Even though this was the one that I initially had as the idea like from this datasheet, there must be this Wi-Fi rum sharing. But so this one, I didn't find it. Then there are a couple of devices where within the ROM dump, you can even find the 68000 and so on. So you know that within the firmware, this is used and on those also the attack works. The fun part here is that the MacBook, I don't have it with me, I just have this dump. So I couldn't try it on my own on this MacBook, but at least I know it should work because the symbol is there. And in the newest devices, this registry is never ever mentioned in the firmware but still the attack works. So it's probably a feature that has been abandoned and it's no longer used, but still we can use it for this type of attack on all those devices. The even more fun part is that sometimes I got again issues with PCI Express. So why is that? On all those chips, I had no idea what exactly I was doing. So I mean, yes, there is the mapping, but I first of all need to get the chip to crash, to get this rum image. And then I need to load it into IDA and analyze it and somehow find a place to get code execution for each chip. And so I was just writing certain things. And then again, like sometimes finding a pattern again when I find the pattern like in the program counter then I probably have code execution. So this was roughly my approach. And then on a couple of devices, this turned out to be a very efficient puzzle. So just flipping a couple of bytes somewhere in the shared memory between Wi-Fi and Bluetooth was sufficient to get kernel panics on a couple of devices. So sometimes just Wi-Fi crashes, but sometimes even kernel panics. And this is interesting because there are of course also some memory areas that I used for the PCI Express queue between the Wi-Fi chip and the host and so on. Or it might just simply block something within the communication between the Wi-Fi chip and the host. And depending on this, it can already cause a reboot. So with the super simple fuzzer of just flipping some bytes or like exchanging some bytes, you can reboot devices. And this is a capture of this. I just use an iPhone 6 because on this one it's very fast. It also works on a couple of other devices. You can see first of all Wi-Fi is switched off. So that's on the left hand side. And then the device is already rebooting. Now you might wonder what the patch looks like. And I mean a lot of this is in hardware. So you cannot really patch it. But what I have seen in a couple of devices is that they are now blocking the communication. So after the Bluetooth chip is initialized by the Bluetooth demon, the Bluetooth chip is then blocking any write, read, run commands, or at least writing. The reading is only blocked on a few devices, but writing is blocked on all newer chips as far as I've seen. And now the thing is that this prevents at least attacks where the Bluetooth demon would try to get code execution within Wi-Fi. So that's like this path. But what is not prevented by this is if you have remote code execution over the air and then escalate into Wi-Fi, or if you just know that the timing between the Wi-Fi and Bluetooth is a fixed one by now and use the known timing, which is not random because of some things sent over the air, but actually like predictable because of coexistence schemes. This might also be a thing that's exploitable here. But at least they added this to the attack model that suddenly Bluetooth might be able to attack Wi-Fi and because of this, this part is now blocked because you can block this quite easily. And now I mentioned in the beginning that this might also apply to other chips. And now the question here is like, what are the chips? If you look into the Bluetooth specification and read it backwards, because I mean, I'm a reverse engineer, so I also read the specification backwards, obviously. What you can see on the last page is the Bluetooth logo and on the second last page, it already starts with the mobile wireless standards. And this is another serial protocol which is used between Wi-Fi and Bluetooth chips or Bluetooth chips and LTE. And they are also sending activity information and so on over UART. And then there is another thing that goes via the operating system to initially configure it. And this one is also used on iPhones. So I saw it on an iPhone, so it probably is also tickable on them. And because everyone has some proprietary coexistence features, we asked Broadcom if we can also include other manufacturers in the responsibly splurge process and they said, yes, we can. And so we informed a couple of those who at least mentioned that they have coexistence in their data sheets and so on. And some of their responses were like that this doesn't really apply to them because there are some chips that have just one core that handles multiple wireless protocols. So by definition, that wouldn't be attackable in the sense of you already have code execution either way, so Bluetooth remote code execution is automatically a Wi-Fi remote code execution. But of course there might be other side channels like I can now from the timing of Wi-Fi frames that I sent on an upper layer maybe predict how the typing on a keyboard or something was, for example, or how the activity was on the other wireless core. And this might be something that could still be possible even though the code execution is kind of by design and cannot be prevented, there might be further attacks. And as a summary, so what we reached is if you have a Bluetooth remote code execution on a Broadcom chip, you can now cause driver kernel panics, get information disclosure about Wi-Fi and even code execution within Wi-Fi. And the other way around, if you have a Wi-Fi remote code execution, you can now do denial of service against Bluetooth and also get information disclosure within Bluetooth. If you have further questions, there will be a Q&A session and you can of course also reach me on Twitter or you can write an email to Francesco and me. Thanks for listening.


Hi, how are y'all doing? My name is Paul Canobie, head men's lacrosse coach here at Stevenson University and I just want to tell you a little bit about our program and what we're looking for in student athletes to come here each and every day. But we really try to look for out of the recruiting world and try to bring kids to Stevenson or tough nose kids who want to be good lacrosse players and understand what it takes to be good. You know, if you want to kind of party and live the dream, there's lots of other great schools to go. But we're looking for kids who really want to be good and understand what it takes, the dedication, the desire, and how to win. It's really tough to win in today's market and what we're trying to do is to try to get kids that want to win and understand that. And part of that's dedication, doing what you're exposed to do, and wanting to be a good lacrosse player. That means putting in the work off the field, not during just the time we're practicing, but in the weight room, shooting with your teammates, but also being a good person in the real world. And that takes a lot of work nowadays to make sure that we're representing ourselves not only when we're on campus, but we're also outside with our friends at home and everything. We're looking for well-rounded kids who want to be good lacrosse players, but also want to be great students. What we really take our pride on is having kids that are great in the classroom. Coach Pauls is a great job, our assistant coach for me for the last 16 years with our kids, monitoring your progress, going over your syllabi, logging on to your Blackboard, making sure you're doing the work you're exposed to do.  We had a 3-1 overall. We had 40 guys that made the Mac all-conference honor roll. And we also had eight guys that got four rows. And so that's one of the best parts that we can to be a great student in the classroom so you can be a great player on the lacrosse field and be an even better player, even a better person in the real world so we can be the best program possible. Well, we think that we want to choose Stevenson because they understand it takes a university to help raise a lacrosse program. And we built this program up from when it was nothing. Most high school teams would have beat us when I first got here. We had 17 guys in the slanted field. And now we have one of the best stadiums in all the country, some of the best facilities. We play the hardest schedule in the nation year in and year out. We run the Mustang Classic, which is one of the best tournaments in the country here each and every year. And we really think we're more of a D1 program but just on the D3 level. We have the Maverick deal and the Underarmor deal. We do great things with these Coast Dyes. And we really want to operate that to give you a D1 experience but it's on the D3 level. And that's what really separates us from all of other programs in the country.


In this video we provide the solution to question number eight for the practice final exam for Maths 1210. We're asked to find the sum where k ranges from one to fourteen of the terms k squared minus four. So if I was approaching this one, I would break it up into two pieces. Let's take the sum of the k squares minus the sum of the fours, again as we're ranging from one to fourteen here, equals one to fourteen. For which when you take the sum of the squares we're going to apply the formula of that situation, which is n times n plus one times two n plus one all over six. And we're doing this in the instance where n equals, sorry in this case fourteen. And then for the other one that's a lot easier, you're going to get four times n. But in that case n again is fourteen. So again much easier to do. So plugging these values into the formulas that we have here we're going to have fourteen times fifteen times twenty nine over six. And then we're going to subtract from the next one four times fourteen. For which I'm going to actually simplify the fraction before I multiply things out because sixteen of course is just two times three. Two goes into fourteen seven times three goes into fifteen five times. And so with that in mind we're going to take seven times five times twenty nine which is going to give us one thousand and fifteen. We also have four times fifteen which is fifty six and then excuse me fifty six. And of course if we take one thousand fifteen and subtract from a fifty six we're going to end up with nine hundred and fifty nine. In which case we see the correct answer is C.