BENEFITS AND DRAWBACKS OF ADOPTING A SECURE PROGRAMMING LANGUAGE: RUST AS A CASE STUDY Kelsey Fulton, Anna Chan, Daniel Votipka, Michelle Mazurek, Michael Hicks 1 Memory safety vulnerabilities Google / https://www.zdnet.com/article/chrome-70- of-all-security-bugs-are-memory-safety-issues/ Case Study: Rust ■ Attempt safety and performance (e.g., no GC) ■ Useful where C/C++ are hardest to like? ■ What benefits (if any) accrue after the adoption of a secure programming language? 3 Case Study: Rust ■ Semi-structured interview with senior developers (I = 16) ■ Survey with Rust community

Manage Edge Nodes with KubeEdge and Case Study Yulin Sun, yulin.sun@huawei.com; Li Xing, Li.xing1@huawei.com; Seattle Cloud Lab, Huawei R&D USA, Bellevue WA Agenda • Edge scenarios/characters • KubeEdge KubeEdge Architecture • KubeBus • Edge metadata service • Kubernetes extension • Case study • Water utility management • Campus surveillance system Edge Scenario/Characters (vs Data Center) • Similar Reports Edge nodes status • AppEngine: Control containers Kubernetes edge extension Current Kubernetes Case Study#1 --Water utilities management • Device • Liquid level sensor • Water pressure sensor • Valve

Windows system use semicolons as the path separator instead of colons.) Each path in the list (in this case /home/user/ext or /home/user/mygo) specifies the location of a workspace. A workspace contains Go the visibility of a name outside a package is determined by whether its first character is upper case. It's therefore worth spending a little time talking about naming conventions in Go programs. Package the package name should be good: short, concise, evocative. By convention, packages are given lower case, single-word names; there should be no need for underscores or mixedCaps. Err on the side of brevity

let vegetable = "red pepper" 2 switch vegetable { 3 case "celery": 4 let vegetableComment = "Add some raisins and make ants on a log." 5 case "cucumber", "watercress": 6 let vegetableComment vegetableComment = "That would make a good tea sandwich." 7 case let x where x.hasSuffix("pepper"): 8 let vegetableComment = "Is it a spicy \(x)?" 9 default: 10 let vegetableComment = "Everything tastes good the default case. What error do you get? After executing the code inside the switch case that matched, the program exits from the switch statement. Execution doesn’t continue to the next case, so there

vegetable { 3 case "celery": 4 print("Add some raisins and make ants on a log.") 5 case "cucumber", "watercress": 6 print("That would make a good tea sandwich.") 7 case let x where x the default case. What error do you get? Notice how let can be used in a pattern to assign the value that matched the pattern to a constant. After executing the code inside the switch case that matched switch statement. Execution doesn’t continue to the next case, so you don’t need to explicitly break out of the switch at the end of each case’s code. You use for-in to iterate over items in a dictionary

simple MVC value types) * UnsatisfiedDependencyException preserves full nested exception stacktrace in case of a BeansException * added overloaded BeanComponentDefinition constructor with aliases argument * warn log when called in unconfigured state * restored BeanConfigurerSupport's silent skipping in case of no BeanFactory configured yet Package org.springframework.context * factored out MessageSourceSupport shutdown, allowing for smooth reinitialization * DefaultMessageListenerContainer performs lazy setup in case of any connection exception (also JNDI lookup failure) * DefaultMessageListenerContainer is able

exposed public "copyRegisteredEditorsTo" method on ConfigurableBeanFactory interface * fixed corner case in AbstractBeanDefinition where a ClassCastException could arise in "getBeanClass(Name)" * Defau information when destroying a bean * AbstractBeanFactory rejects getBean request with arguments in case of a pre- existing singleton of same name as well * AbstractAutowireCapableBeanFactory preserves possible (allowing for statement caching) * JdbcTemplate passes full Calendar argument to JDBC driver even in case of no SQL type specified * JdbcTemplate does not call the costly "Statement.getWarnings()" unless

exposed public "copyRegisteredEditorsTo" method on ConfigurableBeanFactory interface * fixed corner case in AbstractBeanDefinition where a ClassCastException could arise in "getBeanClass(Name)" * Defau information when destroying a bean * AbstractBeanFactory rejects getBean request with arguments in case of a pre- existing singleton of same name as well * AbstractAutowireCapableBeanFactory preserves possible (allowing for statement caching) * JdbcTemplate passes full Calendar argument to JDBC driver even in case of no SQL type specified * JdbcTemplate does not call the costly "Statement.getWarnings()" unless