Okay. Hi. I'm Robert Barron. I'm a software engineer at the Massachusetts Open Cloud. Joining me on stage is Steve Gregory from CyVerse and Hong Xu, who works with me at the MOC. Here at the MOC, we are providing services to both people who require computational services as well as to people who are providing computational resources. What we are describing today is our collaborative effort to provide a simple-to-use GUI, Gigi, that is designed to complement Horizon. Although Horizon is a very powerful tool in being so powerful and providing so many options, many of our users have found it to be intimidating. When I think of our users, I think of a group of computational chemists down the hall from me. They would write their code locally, but barter for time on a much faster system. While they may be experts in quantum computing, they may not know how to set up a router, the first thing that you have to do in Horizon. That said, our goal is to provide them an interface that automates common tasks that most of our users that they would need as well as most of our users would need, but also allows them to use Horizon to work with the same project when they need the power. This goal extends to our federated cloud, where we will have different portions of our cloud, where we actually have different portions of our cloud being administrated by different groups adding to the complexity. Although we are designing this to work with Horizon, there are more degrees of freedom. We are using Gigi to simplify common operations that all of our users will encounter. We don't want to reinvent the wheel. Our basic strategy is to make commonly used use cases simple.  To accomplish this, Gigi will provide a set of default security groups, a default network, and all they need to decide is how large a VM that they need. If at some point down the road they decide that they want to collaborate with more individuals, they can change the security groups to allow them to come in using Horizon, or they may want a cluster of VMs, they can do so also using Horizon. We are also providing services that are not found in Horizon, such as Cloud Dataverse, which we have built on top of OpenStack. So our basic requirement, one of our basic requirements is to allow users to switch between Horizon and Gigi. As a starting point for Gigi, we chose to fork Cyvus's Atmosphere Troposphere project for the following reasons. It provides a similar user experience that we wish to provide to our users. It is open source. It has a similar user base and some maturity. To give you an idea to the basic architecture of how Gigi is and what we are inheriting from Cyvus Atmosphere Troposphere, we have the front end at the top, which is their Troposphere project. We have the middle layer, Atmosphere, which is their Atmosphere project. I will discuss this in more detail after an introduction to Cyvus Atmosphere Troposphere by its lead developer, Steve Briggery. Thanks, Rob. Today we will be talking about Atmosphere, some of the problems that we have encountered and how to solve those problems for our user base. First, I would like to quickly go over the history. The Atmosphere project was started in 2011 as part of Cyvus's Cyber Infrastructure, an NSF-funded project at the University of Arizona. Our first supported cloud was Eucalyptus, and in 2012 we expanded that support to include OpenStack. So what is Atmosphere? Atmosphere is an open source platform for the science and research community, which simplifies the cloud computing experience for users with a wide range of computational literacy. We did this by creating a straightforward user interface and a robust REST API that allows users to view their cloud resources, collaborate with others, and focus on the science. Since releasing OpenStack integration in 2012, we continued to see steady user growth. Over the last five years, Atmosphere's user base has increased from 600 to over 6,000 users. And during those five years, Atmosphere itself has transitioned from a single cloud to a multi-cloud interface. In 2016, we took that to the next level, allowing Atmosphere to become a platform that can be self-hosted by other sites like the Massachusetts OpenCloud. The first problem that Atmosphere set out to solve was simplifying the complexities in cloud computing. For our user base, that meant creating that simple interface, Atmosphere Airport, that allowed them to see only the most critical cloud resources, instances, images, and volumes. The most important part of Atmosphere Airport was making it as easy as possible for the scientists who had never been exposed to cloud computing to launch and then gain access to their instance. So we solved this by creating sensible defaults that enabled a one-click launch requiring users only select the instance size to be launched. To help users access their instances, we also provided browser-based terminal and VNC functionality. This enabled our users to go from launching to viewing their instances desktop in just two clicks. But sensible defaults alone are not enough to get users to launch and then access their instance. Behind the scenes, the Atmosphere API was responsible for ensuring that security groups and networking were initialized, and after the instance had made it to active was responsible for the allocation and assignment of floating IPs and a boot script that would secure the VM as well as enable that browser-based terminal and VNC access before we handed that instance over to the user. And as it turned out, there were a whole lot of scientists who were interested in free cloud computing resources. So many, in fact, that our clouds were constantly at 100% capacity. And with no incentive to delete instances, we found that a lot of those resources were sitting idle. So we addressed this by starting, by tracking the amount of instance usage over time and assigning a monthly quota to our users. Users who went over their quota would have their instances stopped until their quota was renewed or supplemented. That would allow others access to the cloud. The next problem that we encountered is that the rapid development of OpenStack meant a new release every six months, but our production systems were not quite as agile. We needed to maintain compatibility for the production systems and ensure that the latest and greatest version of OpenStack could all be supported by Atmosphere. So we created an abstraction library that relied on libcloud and the OpenStack client tools, which enabled Atmosphere to manage OpenStack versions from Havana to Newton. Although airport was created with multiple clouds in mind, it was only capable of showing one cloud provider at a time. Since our users had two or three OpenStack providers to choose from, this meant selecting a new cloud provider and waiting for a page refresh to keep track of their resources across clouds. Additionally, we realized that our image catalog was starting to grow, but that our users didn't have enough information to figure out which image they should be launching. So we addressed this in 2014 by creating Troposphere, a single-page app built with React and Backbone.js that had a detailed image catalog with support for versioned images so that users could see the established history of an image and how that image has changed over time. Troposphere also focused on grouping instances, volumes, and images into logical projects rather than based on the cloud provider and the credentials that created them. Here's the project details view in Troposphere. You can see that the multiple OpenStack clouds project has three instances, each from a different cloud. And here's an example of a versioned image as displayed by Troposphere. Each version has a description that explains what has changed and represents a glance image on one or more OpenStack cloud providers. With the introduction of Troposphere, we were able to change our focus from making cloud computing easy for end users to making cloud computing easy for OpenStack site operators. And in early 2016, we became a self-hostable platform so that other organizations could host their own copy of Atmosphere and Troposphere and manage their own clouds. In February of 2016, JetStream Cloud became the first organization to use Atmosphere as a platform. And in September of 2016, Massachusetts Open Cloud became the second organization. Every organization that adopts Atmosphere installs it with a different end goal in mind. And in order for us to become a more effective platform, Atmosphere and Troposphere had to become more flexible. This meant implementing a custom theme for our interface, making authentication a plugin that could be easily swapped out for other implementations, and converting our instance deployments to Ansible, enabling site operators to choose what they wanted to deploy on an instance before they handed control over to the user. So that's Atmosphere in a nutshell. If you have any questions or are interested in using Atmosphere for your site, please come see me or Andy Lennards, the lead developer of Troposphere after the presentation. And if you're looking for a job we're hiring, so check out the link below for open positions. Thank you. Thank you, Steve. From that description, it is obvious why we selected the Cyverse Atmosphere Troposphere project as our starting point. We do have some significant differences. For starters, GG's target audience is different. We have a combination of academic users and industrial partners who are also using it. Also, we only support OpenStack. This drives our requirements to work with Horizon. Horizon, I would say, so Atmosphere, another key difference is that Atmosphere needs to work with multiple clouds. Now, to work with Horizon, we need to make sure that users are defined in OpenStack. Our users are defined in OpenStack whereas in Atmosphere the users are defined in their middle layer. And projects are also, in Atmosphere, our collections of cloud resources whereas in GG projects are defined in OpenStack. Atmosphere needs to have a model of authentication, authorization as well as multiple layers of authentication, authorization for each of their cloud that they connect with, whereas GG can just use OpenStack's model for authentication, authorization, which is Keystone. GG does not need to act on behalf of its users. And we are exposing other cloud, other OpenStack cloud and MOC services such as Cloud Dataverse. To summarize the modifications that we have made to GG mainly involve interoperation with Horizon. To highlight the differences on the left is what we are inheriting from high-verse Atmosphere and on the right is where our current architecture. The major point here is that the architectural differences are minor. Right now we are a fork, however it is feasible that this could evolve into a single code base. In order to work with Horizon we moved the primary authentication authorization to using Keystone in OpenStack so that that sort of pinkish color is moved down to closer moved out of the middle layer. And this was done in GG using the mechanism described earlier by Steve involving his plug-in architecture where we just took the plug-in and passed the credential straight through to Keystone. We are using the catalog returned from the unscoped token to get the project definitions. And the catalog returned from each scope token to get the instance definitions. So our projects effectively in GG become defined by the projects in OpenStack. This way we can maintain a consistent view of each project using OpenStack's access control mechanisms without explicitly building it in to GG. We are also working to bring online other MOC services, OpenShift and Cloud Dataverse. And currently these are being loosely integrated as you will see in the demo given by Han Chu. Okay so this is the landing page of GG. It basically tells you about what GG is and what services that MOC currently supports. As you can see here we support OpenStack, Cloud Dataverse and OpenShift. Let me just log in, use my MOC OpenStack credentials. Just one second. It's the same as Horizon. We use Keystone for user authentication. It's going to take, yeah that's fast. Okay so on the top you can go to different component pages by clicking this. So let's go to the marketplace. In the marketplace we have MOC services and GG enablements. For the GG enablements they are the tools that enable GG to become a MOC marketplace. Robin and I are going to work on this over the summer so I won't show you guys the details here today. In the services we have a launch a new instance tab that I will show you in a minute. And the second thing here is Cloud Dataverse. So click on this you can go to the Cloud Dataverse site and then from there you can select the data file that you want to compute with and then you can go back to GG to do some data processing job with OpenStack Sahara. My colleague Jeremy, which is here, I'm going to give a demo about this on Wednesday morning at 11am. The third thing here is the Red Hat OpenShift. Currently it's just a pointer to our OpenShift dashboard with having single sign-on in the future so our user don't have to really tap in their credentials again just to be able to see that. So let me just log in with using the same credentials that I used for logging to GG. I won't do more. Now let's go back and launch a new instance. So if you want to launch a new instance you just click on this and you will see a list of images that we have. Let's say if we want to launch an instance with R pre-installed and it's over to 16 so you just click on this, you will see a launch button right here. All you need to do is just click on this launch button, you will see a form that is pretty much the same as the Tropor Sphere has. That's all you need to do before you launch a new instance. If you don't care about the name you can just leave the way it is but I'm going to change that to Monday. And you don't need to worry about this. You just need to make sure the instance size is big enough for the image. Let's use the median and click. So here you will see a list of all the instances you have in that project and the one that you just launched. Now from here by clicking on this icon you can go to Horizon and check. Again in the future this will be a single sign-on so you don't have to your credentials again.  I just launched. Zero minutes? Okay. If I refresh I will have a floating IP. Yeah there we go. We have a floating IP here assigned and you can just use the IP to SSH into the instance. And as you can see here all the instances have different status. So for example, shut off, suspend and you can go here and check it's pretty much the same mapping between each interface. I think yeah at the end of the demo I would like to show you guys a video that is basically a comparison between Gigi and Horizon for launching a new instance at the first time. So you get an idea about how fast Gigi could be. This is not the one that I want to show. Okay. So I have this new user called OpenStackDemo. It's the first time for the user to log into both interfaces. And as we know in Horizon you need to set up the network, router, subnet, to really before launching a new instance. But in Gigi all you need to do is to select an image and upload your SSH key and you could have that instance to be launched. So in Gigi we're about to launching a new instance. It takes about 54 seconds. And in Horizon you still need to make sure you set up the network correctly and then upload the key that you want to use. So I think it's taking about 124 seconds. Yeah and see here in this form you have to go through all the tabs that you have to make sure everything is right before you launch the instance. Yeah it's 126. Okay. So coming next we're going to talk about the future features that Gigi is going to have another conclusion. Thank you Hanzo. In the future we're planning to have single sign on so that we only have one account that someone has to use to sign on to their BU account for example and all the other applications will use that login. We are also in the process of working on an open cloud exchange at Marketplace, a federated cloud. And as you saw in the user interface during the demo there's a series of enablements, things that have enabled us to be able to federate the cloud and a number of features. We are specifically working on bringing up open shift. We expect that sometime at the beginning of summer and we are also working on cloud dataverse which is mostly there as will be seen in the demo on Wednesday. Take home message is that we are working on improving and simplifying the user experience. Our GUI will be interoperable with Horizon. We are not planning to replace Horizon. And we are planning to use have Gigi, our GUI, be a gateway to all of MOC services. And here's the two reference talks. Thank you for your time. Okay. I think what you're... Let me rephrase the question. You were commenting that in the one slide we were showing instances from different open stack versions. And later on I'm mentioning that we are using Keystone, hence we are only using... We can only show things from one project, one set of instances from one Keystone project. Right? And that is one of the key differences between Atmosphere and what we're trying to do with Gigi. Because if you did... If we did something like that in Gigi, in our GUI, when you switch over to Horizon, you wouldn't see all of your instances. Right? And so that's one of our key differences. And one of the things that we've changed is made the projects come from OpenStack. No, no. We only have one Keystone. We have a federated cloud. And so we have one Keystone service that we're intending to hit a proxy service that allows the cloud to be federated. And so between Keystone, the proxy service will handle the Keystone to Keystone authentication. So one login, one identity provider, multiple clouds. Any other questions? So I was curious, have you gotten any interest for the cyber stuff from a community outside of scientists? Do you see it more broadly applicable? Yeah, definitely. Because it was an NSF-sponsored project, or NSF-funded project, our main focus and driver was the research and science community. And initially we started as the I-Plant Collaborative, and that was focused only to plant scientists. Since we've become cybers, we have expanded that audience to be generally all data science, and we have seen great success in that area. Looks like that's it. Thanks, everybody. Thank you. Thank you.


Thanks Beijing hackfest reminder to register Todd I don't know what the registration is I don't think I've registered I know I'm going but So we want to do that and then again, you know as we usually say, you know Feel free to go in and add things to the agenda and well We obviously we run these as sort of an un-conference When we get there and see who's there and who wants to discuss what but it helps to put things out there And sort of help to spark some discussion Bad certification update we now have Sawtooth and fabric at 100% and a Roja very close at 97 and I know Dave is is working with the teams there And so we have two discussions the first is For Dave to review his revised draft process for security handling CVs and And then there's the top-level versus sub project discussion. I don't know if Brian is on I Don't think so I don't think he is so if he's not on then I guess we're gonna defer that which means we just have the one discussion Dave All right, I'm trying to see if I can share my screen If not, you guys have I have to pull up the draft on your own Sorry, I might I was delayed three hours getting out of New York last night. We didn't take off until almost midnight eastern time Which means that I landed about three hours ago So Dave oddly it will not allow me to give you presenter rights I've not seen that before so I don't know Yeah I'm I'm calling it what I'm accessing it from my phone here, but I was trying to do it for my laptop as well So there now I'm in says you don't Posting a link to the draft in chat Yes Hold on a second. Why am I a game reporter twice? You're echoing Something has to be muted There, okay It says now that it's waiting to view your screen, so maybe you can share now Yeah, except I'm on a Chromebook and this isn't We'll get the link yeah Links in chat now. All right. Thank you. Sorry Dave. I know. All right, so This ties back to the earlier point that the CII badge as in process for our three main projects our graduated projects Part of the security section for getting your Co-infrastructure initiative badge was that you needed to have a documented process for handling security bugs and The teams that are at a hundred percent I have advised them to just point back to This document and the wiki that say we are we have a process or you know, we are going to follow the process And then I told them that as long as we got this process into place before we went to 1.0 that everything would be fine so this The security bug proposal is nothing new that this is nothing I invented Generally the philosophy behind this is that we just wanted to all agree on One way to cooperate on the security bugs It doesn't make sense for all of us to have our own committees our own groups of people handling security bugs Mostly because I wanted to spread the load out One of the CII badge proposal requirements is that each team identifies one engineer that has secure programming experience and Would I think that's all it says secure programming experience I want to leverage that list of engineers to build a committee that will review the Confidential security bug reports the plan being that as they come in We would all get together. We would triage them anything we thought was We would probably investigate them and anything we thought was a real Serious security flaw we would then pull in other engineers from the effective project on the need to Know basis and work with them Quietly and quickly to come up with a fix for them Then the next round of once we have a fix that we all agree on then We would reach out to any vulnerable large installs and give them a heads up so that we could deploy the fix before it's announced publicly and then Once we have all that in place then we will go through the normal CVE process announcing the The disclose or yet disclosing the vulnerability as well as cutting a new release that includes the fix as you can see most of this document is Basically out the Apache projects vulnerability handy procedure handling procedure. I went through all of theirs and I am I'm exceedingly happy with how it is. It's essentially the same as what we did at Mozilla and it's also pretty much the same. We did at linen lab. So I have lots of experience with these processes I just really wanted to put it in front of the technical steering committee because at some point the TSC is going to have to approve this The key highlights here are that we will have team members from each of the major projects Bug reporting is confidential. I have we have already set up the security email The security at hyper ledger org email reporting I'm also working with rye to enable security groups In Jira so Security groups in Jira allow The broader community to report a Jira and to flag it as a security critical bug and when it's flagged as a security critical bug it is kept confidential The only people that can access it would be the members of this security triage group and I'm working on a solution for github for the teams that are on github and I'm still looking at All of the projects to see to make sure that they're either on github or Jira. So Let me see. Let me distill it down to the points of discussion one There is I would like to have a standing Committee of security oriented engineers where we meet on a regular basis To triage incoming security bug reports. So that's gonna be TSC report approval to I've already put into place or I'm putting into place confidential bug reporting and handling and Three this document here is going to be the Document of record for how we are going to handle things which includes Which includes the process for responsible disclosure of vulnerabilities so Now that I'm at that point, I guess I'll open it up for discussion So this is Chris You're you're looking for just one or a minimum of one from each project a Minimum of one Ideally, I'd like to keep this committee as small as possible. It hopefully we're not getting a lot of security bug reports Really only It all really needs to be three or four, right?  I I don't want it to be a big Yeah, no, I Understand and you got eight projects now and more coming. I'm just suggesting that there be some sort of a phone tree at least to That's actually really good feedback. I'm that's actually a good idea I think we should do that we can at each of the teams can identify a primary and an alternate and The idea is that we would meet on a regular basis, but obviously if a report comes in that looks really scary I will I could potentially call a meeting on a short notice And also, I don't want to be the leader of this meeting. I will be a part of the meeting but I Will I would like that the security triage group to elect elect somebody to be The moderator the person who calls the meetings and runs it And we will also take Extensive notes as we go through the the bug triage process, right? So it'll probably be recorded in the confidential bug handling system for full transparency once it's disclosed Okay, and part had a comment part Yeah, sure. I was just curious what exactly we were defining as security bugs because for something like an OS, right? It's relatively straightforward. What's a security bug and what's not for a piece of blockchain software? It's not necessarily so clear It's something that Impacts certain aspects of the performance might be might be, you know disastrous for some applications Do you have kind of a guideline as to what you might consider a security bug and and what wouldn't be one and my Question there was a bug in a consensus algorithm. Would that be a security bug or not? Um Well, I think the rough definition is that any bug that allows some non or non-trusted actor or you know I guess even a trusted actor in a permission network to Adversely affect that functioning of the network that would be considered a security bug So yeah bug in a consensus algorithm that's preventing it from coming to consensus for sure would be a security bug now the the triage committee would look at these and decide whether it's a critical security vulnerability or not and For something like a consensus algorithm problem You know, it's really up to the committee to decide it could be something where it's like, oh well We're we're not able to get our throughput that we want because there's a problem in the algorithm So maybe we'll just kick this out as a critical bug and and let the project handle it But if there's a bug in the consensus algorithm and allows people to like DDoS the entire network and prevent it from functioning at all I would consider that to be a critical security bug and so we would We would deal with that quickly and Confidentially because we wouldn't want to reveal the ability to shut down and establish to credential network Okay, sure. I see what you're saying. Thanks. Yeah I mean in just a few if you define things really liberally then kind of any bug on a blockchain practically Can be a security bug But if we have people who are following them very quickly and kind of measuring the impact then we shouldn't be overwhelmed by Security bugs at least that's the hope Yeah, I think it'll be pretty clear. I think the vast majority of these bugs are going to be bugs that are remote code executions, you know, they're gonna be attacks on the IPC layer You know remote access attacks those kinds of things But you know, we will deal deal with bugs on Things like consensus algorithms and even smart contracts as well I think this is why we have a committee and this is why we meet on a regular basis And as we move forward, we're gonna get good at being able to spot what is it isn't a security bug It's hard to define it right now. Obviously, right, but it's general rule of thumb is is there It does does this bug allow the network to be shut down or to be adversely affected by somebody Who hasn't been trusted with the ability to do that, right? Would it be helpful to look at what Ethereum and Bitcoin have done in response to those in order to get an idea about what? Kind of appropriate response to algorithmic bugs would be Yeah, that's actually a good idea Yeah, so the Ethereum one and specifically right the Dow was a really interesting test case for smart contract bugs, right, so I Guess we could go through I I could go through it and I can put in references to that in the notes To help give broader definition or a narrow definition to what a security bug is Okay, it just seems like you know building on somebody else's experience specifically with with the kind of problems We'd see with the blockchain might be useful It's Marta here. Also, I think that we are very early stage in general with blockchain and We haven't seen attacks so we will just learn as we go It's it's hard to define what a blockchain bug is a lot of it will be just implementation problems with As we move forward, but we'll just respond bugs because they we will see attacks so Putting definitions today will be hard because well, some of them are easily defined. We know that There is a potential for DDoS or potential for 51% attack But some of them will be just well, we'll just have to face it and as Brian said yesterday We will be what we will know that we're doing a good job once people will start attacking us because that means that we're interesting Yeah, I agree with that. I think largely what we're gonna see is implementation errors at first And then we'll later on be become experts on smart contract bugs. I think as we start finding more and more of those To augment this process I we are also putting into place security scans security audits and continuous fuzzing For the various projects to try to get out ahead of any implementation errors The reason it Roja is only at 97% with their CI batch is because they are a memory unsafe language C++ And I'm working closely with them to get American fuzzy lock in place which is Which is notorious for finding Bugs, you know implementation bugs in memory unsafe languages If you look at the trophy case for American fuzzy lock, it's things like Libf. So the Apache web server the Linux kernel like previously undiscovered Implementation flaws that had been in the code bases for many many years. So That's the fuzzer that I've been going with with them and I'm exploring options for Sawtooth and fabric as well because there are Python and go adapters for American fuzzy lock as well So hopefully we're I mean we're taking a proactive stance on security here we're trying to get out ahead of it and It's about time we start standing up the the committee to deal with Security bugs because we're gonna start finding them from the fuzzing to so Yeah, are you gonna be able to deal with Or will the committee deal with like a SSL bug that that's not in our code per se but can be used to To do something malicious to us But we have to address, you know, we'll sort of like a gray area, right? Yeah, so the answer to that is absolutely if we find a security vulnerability and we trace it out to An external library like open SSL We would immediately contact the security team on open SSL and we would work closely together with them we would make the report to them and then the way it's always happened in open source is when you have an external security report that person becomes sort of The primary resource for investigation. It's like okay walk us through the you know, how you did it, you know walk us through How you can trigger the flaw that kind of stuff So we would work very closely with that external team security Team to do it now not all open so open source libraries have security teams So in those cases, we would become the de facto security team for that open source library So we would probably try to fix the solution or fix the problem and then it feed it into their community in a responsible way Right, but I was actually thinking of the other case if like, you know, somebody else reports outside of Hyperledger, but you know open SSL bug is reported You know, does the committee meet to figure out the impact? Yes, yes, that's the answer to so yeah if we're affected by something. It's not responsibly disclosed for sure We will have to come up with a response on a quick notice but most of these foundational libraries like as open SSL have a Confidential security reporting process for responsible disclosure and it's likely that we would be what you know It was likely would be included in the confidential reporting because I part of this committee would be to reach out to those core pieces That we do rely on and let them know that we are a major install of their software So if they get Something that we should know about, you know that they're trying to handle responsibly let us know so that we can respond With that sorry, this has been Borough we have an obvious source of our teams but in two and the consensus engine is built by tenement Would that work in two directions that we would also report to tenement? If bugs would be found there. Yes, or how would you envision that relationship as to be structured? I mean, we have a close relationship, but there's probably some value in thinking of how that Well should be structured security response teams are kind of like a It's hard, you know for lack of a better term like a secret society They tend to be very small and we all tend to know each other And so it's very much like you want to reach out to the security team that Manages major pieces that you rely on and vice versa offer yourself up Like, you know, if there's gonna be a major install of fabric somewhere and they have in-house security say hey We'd like to get our security teams in touch and to establish some kind of you know understanding that will let each other know Security's gotten me such a big deal in the last ten years that this is not new right most security teams all eventually start to know each other and we have Secure back channels between all of us This is just us forming our committee and then joining that broader community that already exists I know from my experience at Mozilla We had back channels from our security teams to you know, probably two dozen other groups both libraries and Users like the Tor browser project for instance was the one I was most heavily involved in we traded Security vulnerabilities back and forth, right? So yeah This is us forming our committee and this is us You know stepping up and joining the broader community that exists so that we can be part of the responsible disclosure process On the question of how do we classify security vulnerabilities, you know, are there any other Examples where threat models or threat frameworks are put in place to kind of analyze You know More proactively, you know, what part of the system would be vulnerable Now this is Conversation we've had, you know hot and others You know, how do we kind of get a little bit more proactive from a security analysis? perspective given that you know For distributed ledgers, that's a very important in enterprise applications. That's going to be a very important consideration So to answer that question, that's what I was hoping to get out of as a consequence of the outside security audits that are under way with some of the projects or at least will be shortly a lot of outside security auditing firms are very good at doing Threat modeling and doing analysis on Identifying the pieces that are probably the most vulnerable or the you know pieces that need the most scrutiny That's not necessarily the security committee's job, although curating those As we go forward would be part of that And it would actually fall more under the secure programmer the secure Programming expert that each team has identified. I think that role for each of the teams would be curating the Threat model and doing more analysis on the code base. I mean, that's what it means to be a secure programming expert That's part of that job. So to bootstrap us into having done the analysis I was going to rely on the outside security auditing teams and to work closely with them to come up with good threat models for these applications and then moving forward just having the expert on each team help curate it and I believe the core infrastructure initiative badge requires Some major analysis and review for every major release. So Going through the process again, not necessarily with an outside security audit But going through the threat model and and making sure that you know all the new stuff that has been rewritten gets a full Security review on it before it goes out the door Does that answer your question? Yeah, that does, you know, I think it'll be good to kind of see whether we can capture the learnings from the threat modeling That can be shared between projects as well, right You know, maybe Longer term we can have a You know a common framework for the threat models for Distributed ledgers perhaps, but you know, it'd be good to kind of figure out how we can Consolidate the learnings if you will. Yeah, I'm the I don't there's I don't think that there's any reason to keep the threat modeling secret so I see all of this as being part of the public documentation and I guess the Security triage group could facilitate that but the way I view it is there's two sides to this, right? It's like we're kind of like the fire department. There are fire inspectors, right? That would be the people doing the security audits and the experts for each of the teams Doing the analysis work And then there are the EMTs and the first responders the people who go to a fire and try to put the fire out that would be the security triage Group, okay, so they're they're very distinct Very distinct set of responsibilities the triage group is really just a an emergency response team And it's kind of like a volunteer fire department Whereas the other group that takes a lot more work are the fire inspectors, right? People going through the code making sure we're not introducing you bucks Got it Yeah And the secrecy levels are different, right because of the different posture they take So I mean any other questions because I don't I don't intend to Call for a vote today, but in the very near future probably next week or the week after I'd like to put this to the committee for approval both to create a standing security triage group and to adopt this as our process for handling security vulnerabilities What is outside the scope of this is Mandating the threat modeling because the CII badge requirement mandates that as part of the security review I don't think this is that's within the scope of this proposal But it is related so It's good that we had the discussion here. I'd encourage people to comment in the the google docs Because over the next week or so we can shape the languaging of it before it goes to the committee for approval But that's it. I mean if nobody else had any questions, like thanks for your time That's some sleep So do we have I guess we don't have a quorum right Todd? No, no, we're we're quite shy from quorum Okay, so And what I would suggest since I didn't hear I mean, I think there was some good feedback there Dave I think there's maybe a couple of nits that you can do to tweak the proposal for And having a backup and so forth and for sure you know defining what You know what we mean by a security defect um, yep, yeah precisely and then Since next week is also a holiday week in the u.s. Todd I would suggest that we Dave that you just send it out and Todd you just call for a vote by email just so that we can Get this moving. Okay for next week Yeah Okay So I just I'm worried that you know because of the hall. I think that's why we're shy this week as well but you know, we have a holiday in the u.s. Coming up on Monday and um Many people will be you know going to the cape or whatever for their yeah Memorial Day weekend and I So we may we may be shy next week as well as all I'm saying so I would just suggest that we just do this by my by mail as opposed to waiting for us to get quorum on Okay, sounds good. I'll make the tweaks. I'll put in some more references um of all the things people had suggested and Yeah, it'll hit the mailing list soon awesome. Thanks Dave for all the effort and um give every actually one thing to mark that you're joined the call and and um I think might be worthwhile to give yourself an intro give the the the tsc and others on the call an intro Was it for me? Yes, yes for you Marta. Oh, sorry. Yeah, so well, I guess I'm at some of you or most of you during Consensus, uh, but just to give give a quick intro. Uh, my name is Marta Picarska. I'm the director of ecosystem for hyper ledger I was announced on monday, but I've been working with hyper ledgers for the last three weeks uh, brian hired me to do three things Though pretty big ones For uh, first and foremost, I'm responsible for Managing and building relationships with our existing members and reaching out to new members. What that means is that? I would like to launch a program where I help our existing members to better navigate our projects our ecosystem and help them um figure out and uh, understand how they can uh Get the best The experience with hyper ledger projects and uh other members So I'll be reaching out to all of our members to Have a quick chat with them. Uh, understand what were what was the motivation? uh to join hyper ledger and understand how can uh, we We can get uh involved Uh in what they're doing and how can they get involved? In what hyper ledger is doing uh looking at you know building connections between members building connections Uh with the projects and introducing them to the projects is quite often We see that they only you know about one or two out of all eight projects and uh, I'll be also responsible for Overlooking the working groups that we're uh launching. So we already have the identity working group the health care working group we are working uh to build and soon announce the Uh insurance working group and that that is the model that we will be pushing forward to kind of Make sure that members are working together on new projects Second thing is I'm responsible for building relationship with our community Uh, so the open source developers Uh organizing meetups making sure that people all around the world understand that we are very proud of Our community and we know that uh hyper ledger would be very different if it wasn't for the volunteers that developed for us um And uh this foundation of open source And then the third thing that I'm doing is I'm Brian's the substitute and backup I'm humble back up when it comes to going to conferences and giving talks So yeah, and I'm based in Cambridge, UK So if you ever would like to meet me just uh reach out on merlin at lenticfoundation.org and um, I would be very happy to meet you Meet you in London or Cambridge great Oh and I have background in security and privacy If you ever wonder if I can code. Yes, I can code and I understand security and privacy So when I sometimes back up Dave on his comments and security, that's why Sign her up Dave I I can actually vouch for that Because uh martin I did work very closely together Back when I worked for mozilla and she was um a phd student at tue berlin working for dutch telecom doing Research in privacy. So we've known each other for a few years and I I plus one everything. She just asserted Thanks and welcome Marta Everyone else Give you 24 minutes back So thank you. I am already asleep. Bye guys Cheers


Hello, NJRoot22.com here with a quick break from the supermarket roundup. This is not a supermarket, it's a pharmacy. Rite Aid in particular. Here's my promo, I'm going to get rid of it. I want to talk about this real quick because we don't really notice these things too much, but we picked one up at the store and I guess Rite Aid is up there as one of our preferred pharmacies of the three. I mean Walgreens I hate, even though it's the sort of the same company, I don't even know what the deal is. And CVS, I'm not a huge fan, I don't know. I have a whole idea about pharmacies in general, it's kind of weird how they're a pharmacy and sell medicine to help cure you, yet they have tons of junk that make you sick and probably part of the reason why you need pills to begin with, diabetes medication. I don't know. It seems like a self-fulfilling business model. Here's the junk that you're going to need to eat or want to eat and then here's the pills you need when you get sick, I don't know. Anyway, I noticed something interesting, they have these sales and we typically try to only shop there for most things when they're on sale, like for instance vitamins. They have a buy one, get one free. That's not a bad deal, although I'm not a big fan of their brands. Nature's Bounty is okay, that's probably the best of their brands, I'm not a big fan of Sundown Naturals, I think it's kind of something's going on with that. May not be the ingredients they say are in there, I've noticed minimal effects from the vitamins I've taken from that company, but anyway, I like Nutrition of the World now. Now vitamins seem to be, or supplements seem to be the best in our experience. But what I've noticed is that Rite Aid is kind of helpful here. They tell you where you could find coupons in the Sunday paper, I don't know who buys the Sunday paper anymore, I guess a lot of the couponners out there do. And Rite Aid has coupons in their own flyers as well, but I mean I wouldn't buy this fluoride injected stuff, but it's interesting, but Rite Aid seems to be a makeup company, I mean a store, they sell so much makeup and all these lotions loaded with chemicals and stuff. The percentage of their healthy and natural stuff compared to the, you know, chemical lab products is like 10 to 1. Anyway, there's something interesting this week, there's this company called Hello that sells this charcoal toothpaste, and this is a good deal if you have one of those wellness cards. This sells for like $8 at Amazon, a two pack, I mean $16 for a two pack. Here you get this charcoal fluoride free toothpaste for $5 with your card, and you get $5 back to spend on something else. So this is a good deal worth picking up this week, and you get two, buy two for $10 and then you'll get $10 to spend on other stuff. That's almost a no-brainer. And we like toms also, they're fluoride free stuff, but it's not always easy to find, believe it or not, and you get $2 back with that, two for eight, so you end up paying $3 a tube. The right date to add, believe it or not, it's very well laid out. I like it, even though most of the stuff we wouldn't buy or don't need. I don't need sickness medication, I don't need eye drops, I don't need allergy, you know, for pain. We don't ever experience pain. We don't need Advil or Tylenol. We use hyaluronic acid and turmeric, and we never feel pain, so that's something you ought to consider if you want to do some research about the healthy alternatives to OTC medicines and remedies. Again, a lot of the stuff, like I said, I mean, most of the items I wouldn't buy, except for Nature's Bounty, and even that, God knows, there's probably someone out there that found something nefarious about that company as well, but I guess I'm walking blindly down that path right now. If you look up online, their biggest selling product at right aid are feminine products, tampons, and stuff like that. I think that's all I wanted to talk about this week. I need a new monitor for my video setup here. I'm using this massive, like, 30-inch screen. It's like, totally in the way.  I don't know. I mean, I might try to find a used one on Amazon for like under 50. I don't need a fancy thing. I just need a display so I could see, my display is off to this side so I could see what I'm looking at here. I think that's it.  I mean, they have, like, two coolers worth of food at this place, frozen or refrigerated, but they actually have a good deal on Oscar Mayer Bacon this week, two for seven. And that's under the threshold. We don't like paying more than $4 a pound for bacon. So that's actually 350 a pound, and that's, that's a good deal if you like Oscar Mayer Bacon with the Sulfites. I think I mentioned last week in my Super Mark 5, Hormel makes a low sodium bacon that has sea salt and instead of a refined salt. And that's been my go-to bacon. Whenever that's on sale, that's usually on sale for $3.99. I buy multiple packs to last me until the next sale, maybe a month worth, like four or five packs of bacon. Watch the ingredients. Avoid plain old salt. If you see a sea salt instead of salt, that's a good, good, good score. And again, more junk here. Mints, candy. It's just a fascinating operation, how they can play both sides of the aisle, so to say. Here's the candy you're addicted to, and then here's the pills that your doctor says you need. I still find that fascinating, and that's, that's about it for this quick, well, not quick, it's over six minutes now. But yeah, that's, what do you think of Rite Aid? It's a, it's an interesting, interesting place. So I don't think I'm going to do too many of these flyers unless I see another interesting deal like that charcoal toothpaste. That's, that's interesting. Apparently the jury's out on that too. They say if you use it too often, it may rub your enamel away. So I don't know why. I have charcoal that I use, FYI, maybe once or twice a week just to clean off the coffee stains. It does a good job. All right, have a nice rest of your weekend.


In this video, we will identify and explain security services that are relevant for internet security. Access Control is a security service that protects resources against unauthorized usage. Such resources may be end systems, such as servers and PCs, but also network systems, such as routers and switches, as well as network links. Access Control at the network level is often achieved using firewalls. Access Control within systems can be achieved by using access control lists. Access Control is one of the services needed to protect against masquerade attacks. An audit is a service formed by independent specialists. Such specialists review and examine security-related information to ensure compliance with the accepted security policies and procedures. Examples of information that may be investigated are access logs, firewall logs and the output of intrusion detection systems. Nowadays, banks and other organizations that hold sensitive data also store network traces, such as collected using NetFlow or IPvix, as part of their security audit trail. Availability is a security service to protect against denial of service attacks. Depending on the precise detail of such attacks, different mitigation strategies may be possible. For example, companies may rely on DDoS protection services that reroute all traffic via this service and filter attack traffic. DDoS protection services can be obtained from commercial companies, such as Cloudflare and Incapsula, but also from non-commercial institutions, such as the National Washing Street, abbreviated as NAVAS in the Netherlands. Next to relying on DDoS protection services, it might also be possible to quickly upscale server capacity. Data confidentiality is a security service that protects against message disclosure attacks. A common mechanism to implement data confidentiality is data encryption. Encryption algorithm can be divided into two categories. The first category is symmetric encryption, where both parties share the same encryption key. Examples of symmetric encryption algorithms include DES, DDoS and AES CBC. The second category is public key cryptography, where two keys are needed, a public and a private. Examples of public key algorithms include ECC, Diffie-Hellman and RSA. Symmetric encryption is much faster than public key encryption, but has its main drawback key management. Therefore, security protocols such as IPSEC, SSH and SSL usually start with using public key encryption, but switch to symmetric key encryption as soon as a secure channel has been created. Data integrity is a security service that protects against message modification, insertion, deletion or replay attacks. It relies on the inclusion of a hash-based message authentication code, abbreviated as HMAC, to each individual message. Such code is calculated by a hash algorithm by feeding it with message contents as well as a secret key. Each message therefore includes a unique code. To detect insertion, deletion or replay, also a sequence number must be added to each message. Data integrity is provided by using authentication algorithms. Well-known examples of such algorithms are HMAC SHA-1 and HMAC MD-5. The second one has some theoretical weaknesses, however, and will therefore likely be avoided in future protocols. Data authentication is a security service that protects against masquerade attacks. There are two forms of this service. The first form is peer entity authentication, which is used whenever connections or associations can be established between both communicating parties. The second form is data origin authentication, which is used in connectionless environments. Like data integrity, authentication services rely on the use of hash-based message authentication codes. Non-repudiation is a security service that protects against false denial of involvement in an association. Two forms should be distinguished. The first is non-repudiation with proof of origin, which protects against senders that deny that they have sent a certain message. The second is non-repudiation with proof of receipt, which protects against receivers that deny that they have received a certain message. For non-repudiation, there are no specific algorithms, since it can be achieved a side-effect of encryption mechanisms, since private keys should only be known to the sender. Finally, system integrity is a security service that protects system resources in a verifiable manner against unauthorized or accidental manipulation. There is not dedicated protocol or mechanism that guarantees system integrity, although it is somehow related to access control.


First, launch disk speed up, then click on the register now button. Next, go to your email account that you registered with disk speed up. You can find the registration email by searching for sys2econ search menu. Once you've located the email, open it to find your registration key. Copy the registration key from the email and go back to disk speed up license key window. Paste your license key and click on activate now button. Congratulations, you have successfully registered disk speed up. If you need more information or have any questions, please drop your queries at support at sys2econ.com.


We're here today to open the Robson Square skating rink for the winter season and it's free for school kids aged grades 4 to 7 and you can see we've got about a hundred of them here today to open it up. They've come from Elsie Roy Elementary which is nearby for the first block of their afternoon and they're going to learn about fitness and having fun and come back again soon. A little known fact, I grew up in Winnipeg, Manitoba and some of my fondest winter memories from childhood are grabbing my skates, joining my brothers and heading down to the pond to skate whenever we wanted to. I think of Robson Square ice rink as the urban equivalent of that community pond. As a representative of the downtown community, we don't undervalue this wonderful free amenity that brings back fond memories for some of us and will create new memories for others.


Hello, it's Rob here and today I've got extremely exciting video because I am going to give you a sneak peek at the Upcoming halfling sprues. So we've had a lot of people wanting to get a closer look at the halflings So I'm going to give you a look at the sprues. I'm going to sneak down into the warehouse and get one off of Zach It's now there's not one not two But three of the sprues in the set and that makes up the full battle group So let's have a look at what's on the first one. So you can see you get quite a lot of options On the sprues and you start off with the 10 infantry So you've got a mix of bodies and then here you can see the cavalry and then at the top You start to see all the different weapons. So you've got a mix here of the spears the spear spikes Spears pikes You've got the braves and You've also got the rifles as well. So lots of different options Obviously when you've got the sprues you can decide which ones you want to do So these are the rifles and then you've got the hand weapons there for the braves We'll also be doing upgrades as well so resin upgrades if you want to make some of the other units like the Rangers You see the back there So you've got five different bodies For the infantry then obviously by mixing them all together You can make a lot of varied options actually on this one. It's a lot of variety on the spring Again, it's a final look at that one And now we will move on to sprues number two So again, you can see these are actually the Arales. So this is an unusual Mix for us because you've got infantry and cavalry. So you've got the five dogs there You've got two of the bodies on this one in the top. You've actually got 15 different heads for the halflings So you can give a real good mix and there's a mix of female and Male heads on there as well, which is nice It gives you plenty of options if you want to bring some variety to your unit underneath there You can see the Arales the different dogs and there's the final cavalry That's the dogs So at the bottom of the sprue These are the arms that you'll use for the rifles. So you've got one arm Holding on to the gun and then the other one is used to support it And then you've got a couple more weapons for the braves at the bottom there's hammers and some axes So the nice real mix of weapons particularly for the braves. They sort of you know, some of them are Not quite farming equipment, but they've got that little sort of vibe to them, I guess And now you can get a bit of a closer look there at the shields So again, these are for the braves and also for the cavalry as well If you wanted to do because you can do the mounted Cavalry can do the melee map cavalry or you can do the ranged cavalry So again, lots of options on this sprue and there's a shield again just at the bottom and then we finish with the remaining aralas so again, you get five on a Sprue on the cavalry so for every ten infantry you get five cavalry So if you've seen the army in the mega army, you'll see that gives you a lot of models in those boxes And then in the battle groups, so rather than a standard regiment what we normally sell you will get 10 So 20 infantry and then 10 cavalry in those So you can very quickly show out an army So just a final look so you can see them all here. So you get three sprues in a set And they are coming in August so in the mega army and the army And then in September we'll be selling the battle group separately So if you want to add a few more troops to your army, you can but yeah, really excited about these And they will be coming soon so pre-order now for mantik or from your local game store quick Because I think they might even sell out