So my name is Matt and my handle is spelled S-Y-K-E and I'm a member of New Hack City which is a hacker collective in San Francisco and J-Roo which is right here, he's also going to attempt to speak hopefully with a video projector in place of some kind. What else can I say? So I worked for two years for a commercial vendor of security software. It doesn't really matter which one and I prefer not to say because I hate to think that people think their products are better because of my knowledge anyway. We have t-shirts for sale out there and I'm going to be giving out t-shirts. New Hack has already sold out before anyone even knew who they really were. Before we just jump the gun, I think the inspiration was AdStake selling out so fast, or Roth selling out to AdStake so fast. So here's the basic deal is that there's four major areas I'm going to cover and I posted an outline to, Jeff posted my outline to the DefCon web page and I've changed it a little bit since then because I thought it would be a little bit more interesting to look at things a bit from a bit more holistic perspective. So I'm going to cover four areas and those four areas are what user expectations of IDS's and firewalls are. Like why do people buy these things in the first place? And then the second thing is how to test for those expectations to make sure that people are getting what they want hypothetically. And then the third section is common coding problems that sort of come up, that sort of bubble to the surface when you actually start doing this kind of testing, testing. And then the fourth thing is what designers and people who are writing these things like right now, like from scratch, can do to avoid a lot of the mistakes that I have seen in the last couple years, code-wise and design-wise. So the first thing is users. Why do people buy IDS's and firewalls? And like why is it such a popular market right now? Or like the last year, it's up to a couple billion dollars or something? It's like crazy that people are actually paying money for this stuff. Well, I think the main reason is people basically don't care. Users really don't care if a proxy firewall or a packet filtering-based firewall or a hybrid firewall is going to make them more safe. Or if a network-based IDS or host-based IDS is going to make them more safe. All they care about is they have a topology and an infrastructure. They don't want to change, and they will put in whatever is going to fit in what they have right now. Whatever is the easiest thing to implement is what they're going to end up implementing. And that's basically what it comes down to. So this talk has nothing to do with arguing over which is better or any of this complete nonsense. So because you have to make both because people want both or need both or have been convinced that they want or need both kinds in either the firewall or the IDS space. So yeah, people just want to deploy and not have to deal with anything. I think most people actually are aware that IDSes don't make you safe. I'm pretty confident of this. I know a lot of people think a lot of, I don't know, hacksawers and security consultants over, think that like general, I don't know if you call them consumers or not, think that IDS is making you more safe somehow. IDSes just give you time to react, and that's all that they do. And I think that most people are aware of this. I think that most people don't think that IDSes are going to magically stop you from being attacked. So I don't think that there's a misperception there. Firewalls, this is kind of weird because real purists will say, you know, firewalls and IDSes are fluff and crap, and they just need to fix the real problems and like make the code in the OSes better and in the FTP dams and whatever. That's not really practical. So from a certain standpoint, firewalls do help you reduce and manage risk. If the firewalls are implemented properly in both code and topology, if the coding is solid, like they've done everything properly, and you've deployed it properly in your infrastructure, and you've configured it properly and everything, hypothetically speaking, it will reduce the ways people can get in, hypothetically.  But hypothetically, from a certain perspective, it does reduce risk, and so vendors have convinced people, of course, that since some bullshit percent number, let's say 80% of all intrusions come internally, and your firewalls are going to protect you from those, you need to have an IDS anyway. So you need to have your IDS to protect you from the outside problems, and you need an IDS to protect you from the problems that the firewall can't block or use, can't deal with it or whatever. OK. So people expect firewalls to keep packets out, and people expect IDSes to tell them when they're being attacked with whatever signatures. Oh my god, is that a video projector? Be still in my heart. So this is what people are expecting. So section two, how do you test for these expectations? I have three favorite tools, basically. They are Nmap, Whisker, and ISIC. And ISIC is a suite of utilities. And I think Mike Franson, who ISIC is here, he's right there.  This guy's tools have helped me find so many bugs. We released a new hack, released a NetBSD advisory two months ago or something. Yes, you do get a t-shirt. Promise. Here's a t-shirt. Oh, by the way, here's what they look like. ASCII art. Let me see if I can look at the bottom. Let me see if I can throw it that far, eh? Oh, pretty close. There you go. Yeah, so Nmap, Whisker, and ISIC. Basically, here's the deal.  Please understand what these tools are doing. Even if you can't read code, read the docs and figure it out. Like, I don't think I'm that smart. And yet, I can sort of know how this stuff works. And if you actually read the docs and understand how works, you'll understand that when you're using ISIC or ISIC that you should disconnect yourself from public networks so that you don't like DOS every box on the subnet plus, which people still do. Yes? ISIC, oh, I'm sorry. It's IP Stack Integrity Checker. And it's actually a suite of utilities. And I'm going to go through each of them individually and how they should be used. And I'll say to URLs at the end, it's really pathetic I have all these URLs memorized. So, I understand the tools.  That's odd. OK, what do the tools do? I'm glad you asked. I think everyone knows what NMAP is. I think it's pretty ridiculous how popular NMAP is and how much everyone uses it for everything.  And it's like, well, that's great. Thanks for telling me something I didn't know. So NMAP is really good, not as a port scan or anything like that. NMAP is really cool for testing a couple of things in firewalls and IDSes. In state-based packet filtering firewalls and NAT implementations, and even IP sect tunnel implementations, NMAP is really, it's so simple. It's really elegant.  All these tools, by the way, the focus is firewalls and IDSes, but testing IP-seq tunnels, like if you go to your VPN bake-offs in your area or whatever, take these tools with you.  Icic found so many things, so many bugs and IP-seq implementations. It's not even funny. So anyway, NMAP. So just doing a simple port scan with NMAP will usually suffice. So because I don't have my slides and my pretty pictures, I'm going to use my hands. So I have an untrusted network, the Big Bet internet over here.  And then I have my trusted machines that are protected by the firewall and whatever else. So the interesting thing to do is to run an NMAP scan through all 65,535 ports. Just to really give the state table, shall I explain this? So in an IDS, when you make a connection, when you send a SAM like, there's a state table structure. Generally, I don't know if everyone's implemented this the same way, but I don't know how else you do it. There's a state table structure. Then it adds your source and the destination like this. Yes? Whoa! Oh my goodness. All right. Where is that at? Right here? Awesome. Oh. What? Do you actually expect me to use Star Office? Whatever. In an introduction, run-down user expectations testing for most users are aware, most have both anyway in NMAP and in NMAP Whisker. Oh, I'm sorry. So I'll start here. So here's a so in NMAP Whisker ICIC, IPC intern checker. Don't just use these tools blindly.    I ran NMAP a thousand times and then when I came back in the morning, the box crashed. That doesn't help anybody. It really doesn't. The vendor's like, well, where's your configuration? It's like, I wiped the box already. Like, you really aren't helping anybody trying to solve the problem that you've found. Configuration can make a difference, especially on fireballs. Like, let's say that you do an NMAP test or you run TCP sick, route it through the firewall, and you have one deny rule. I've seen situations where you add an allow rule or you add an absorb rule or whatever or you add two deny rules or something and then the machine will crash or then it will leak packets or what have you. So if you're really interested in finding problems and stuff, just be really diligent if you have the time and the resources and whatever. Oh yeah, so here's the network idea.  And so usually in my examples I say go from untrusted to trusted, because that's what usually what people do when they're doing penetration testing. But if you're looking for crashes or packet leakage or whatever, you can find it the other way as well. And people usually miss this from a couple of bugs in the software I was testing by just going the other way around, especially with NAT. If you have a NAT at firewall or IP masqueraded or whatever links people call it, and you send like from trusted to untrusted or the other way around, that gives the code that maintains the state tables for NAT a really good workout. Give an example of a bug that I found that worked like that. When you sent thin packets through NAT from trusted to untrusted, the firewall made an entry in the state table for that thin and then never removed it ever. So if you did a fin scan or flooded it with fins or what have you with like from random source addresses, basically you're testing to see if there's any unchecked mallets. And if there's an unchecked mallet and these other stuff is in ring zero, you've got a blue screen or an oops or whatever links cause it or a kernel panic or what have you. Put your firewall down. Huh? Put your firewall down. Put your firewall as well. Put your firewall down. It doesn't matter if it's been fixed. Next, right. OK, so end map. Yeah, state table code and packet filter and NAT implementations from untrusted, from an untrusted machine, net map, end map, thin scan, ports one through 65, 535. A really cool thing to do by the way that end map will let you do is send stuff from port zero through a firewall. That gets interesting results sometimes. Same way with an IPsec tunnel, et cetera, et cetera. And so what you can see when you do this, if you know how to look, by the way, if anyone knows how to see non-paged kernel memory usage in Linux, could you please tell me programmatically or otherwise because I couldn't find any information on the net at all on how to do it. But if you were able to do that, like you are on NT in about one second, what you'd see is that when you do that, you see non-paged kernel memory increase because what's happening is the state table is growing because you're doing a lot of connections. And so like I said, what this test for is one unchecked malloc. Like most operating systems impose a hard limit on non-paged kernel memory, like 16 meg or 20 meg or however much it is. It depends on how much physical RAM you have. And for you non-OS architecture people, a non-paged kernel memory is memory only accessible to the kernel that never gets paged out, ever. Because for whatever reason, the data structure that's holding it couldn't handle a virtual memory fault or a page fault of any kind. And state tables happen to fall into this sort of category. And so if you make the state table grow large enough, eventually it's going to hit that hard limit of non-paged kernel memory. The OS is going to say sorry. And I've seen it time and time and time again where I don't know why, but people don't check the return values of sys calls, not just malloc, although malloc is like the most common, all the other malloc calls as well. There's been a couple vulnerabilities now like people weren't checking their return of set GID. Like if that failed and like defaulted to zero or something, I think it was a weird or something, it's the echo pic show. So that's basically what you're testing. And if you're looking for stuff like that, like you're looking for DOSes where they run out of memory and then they fuck up because they didn't check in malloc somewhere, both in Linux and in NT and probably VSD as well, you can limit the amount of physical memory the OS will use. That will help you greatly in finding these bugs faster.  And so if you just kind of lower it just a little bit, you'll hit these conditions a lot easier. Wait, I don't want to go to the whisker. That's a five. Go back to me. There we go. Different scan types, like I said, fin packet and a certain implementation of a Safefield packet filter firewall didn't remove fins. If you just sent a fin, it was really odd. I don't know how the thing ever worked. It probably didn't ever work for it. Acts, gants, et cetera, et cetera. So tiny IP frags. This used to be an interesting way to leak packets through firewalls and to make firewalls crash.  For a Safefield packet filter to do its job properly, if I've blocked port 80, I'm assuming I'm going to assume some knowledge of TCP-IP here. If I block port 80 and the TCP header is split up across multiple IP packets. So when I get my first IP packet on the firewall and I'm analyzing it and I'm looking at it, and I'll say, OK, is this allowed on the ports that I'm allowing to pass through me? Well, I can't see the port because the port information in the TCP header is in the next IP fragment. You can do one of two things if you're an implementer. You can either reassemble it to get the full TCP header, in which case you're opening yourself to DOS with memory usage, with people sending a whole lot of frags, and you're holding them, waiting for the next fragment to come so you can get the full header. Or you can just drop them. I'd recommend dropping them because the likelihood that an MTU is that small that a TCP header would be split across IP packets is very, very, very, very, very unlikely. In fact, if anyone can tell me a configuration in which that would really happen, I'd really like to hear it. So if you're an implementer, drop tiny IP frags.  It's not even worth any trouble because it doesn't happen in real life.  So the neat thing tiny IP frags does now is that state-based IDS is the key track of connections and whatever else. If your IDS is like a logic tree like, they're not just doing the flat sort of packet gripping, and they actually check to see that, OK, there's a SIN, all right. There's an ACK, OK. And then I look for my GetPHF, all right. Stuff like, excuse me, IDS is they do stuff like that. You can actually, this sort of stuff kind of works. Because for IDS is that don't do IP fragmentation reassembly. Like it says the same problem that the state-based packet filtering firewalls do in that they can't get the full state with the first packet, so it's like, what do I do? I can't do reassembly either, so I guess I'm not going to pay attention to this stream unless it matches like my packet gripping. And because you're fragmenting that small anyway, it doesn't really matter. And you can do tiny IP frags with another tool that I almost mentioned called FragRouter. And FragRouter is a fine tool. I think it's written by Doug Song. Maybe he's here. And that can send tiny IP frags with just regular traffic. It's sound, it works just like it sounds. It's a router that fragments packets to whatever interesting configuration you want. So, since scan Portland, like all the ports, basically doing a third port sweep, like, expanding in tracks, state tables if they're implemented properly. So this is pretty evil because this next example here, Nmap, send scan, all the ports, decoy scan. I love decoy scan. Let me tell you why I love decoy scan. And with decoy scan, you can fill up state tables faster than anything.  But it might not be practical. So, F3, can I go back now? So see here, this network here is 192.168.2. And the one I'm sending from is 10.0.0. Can you go back again? Oh, thanks. Does it work? This thing here? Yeah. So I'm using the loopback address of the destination network, the broadcast address of the destination network. And then the loopback and the broadcast of my network.  I've found interesting packet leakage problems doing stuff like this. Whether or not these packs can be routed through the actual internet is a whole another question. But if someone owns your ISP and they're one hop away, it's a completely feasible scenario. Yeah. So decoy scans are actually pretty neat. And actually, I don't think that they're really useful for reading IES detection at all, because that's what the original purpose was. Was that you do so many parallel scans that the IES logs flood, and they can't tell what's going on, because they see so many source addresses for the voice canceling. They can't tell which one's the real one. And so Nmap can be gotten from http.com. Insecure.org, slash Nmap, I-N-S-E-C-U-R-E.org, slash Nmap. I think everyone knows that. Whoever doesn't know that shouldn't be here. Next. Please. Next please. Thank you. Whisker. Whisker is really cool.  Probably your Palm pilot can run a Whisker if it runs Perl. Yes, sir? I'm sorry. All right. That would be nice. Do what? Turn up the volume? Like this? All right. So I think everyone knows that Whisker is basically made to... It's an HCP scanner, but Rainforest Puppy blesses heart at a whole bunch of IDS evasion functionality, which is really cool. If you see him, give him a big hug and a smooch because he really deserves it. Because this gets passed. These things, I think... I have not seen an IDS that one of those evasion techniques does not get passed. If you can show me one, I'll blow you or something. So Whisker basically... What? Oh, thank you. Let me take it real quick. So Whisker works like this. You have Perl installed. Oh, you have Perl installed. I'm sorry. You have Perl installed just Whisker, dash H, your target host, and then dash I goes through all of the various IDS evasion techniques. Dash I1 is URL encoding, which is a very popular one to do, which lets us face Robert Kramp from Network Eyes Blasted, Network Associates' Cybercop Monitor for not doing when it really does. So I think everyone knows Whisker is good for doing this stuff, but here's an interesting point that I don't think you need to use what I thought it is. HTTP proxy is a block-by-url.  How much do you want to bet that they're all susceptible to URL encoding?  So a lot of people think proxies are just deployed so that users on the inside can browse through this proxy. Actually, sometimes it works the other way. They have a proxy so that people coming in from the outside like are limited access to certain URLs unless they belong to a certain IP range or something like that, or they authenticate first. And this gets passed that. Something else to test for in HTTP proxies. I'm not going to talk too much about this because Whisker has great docs.  So the URL is http://www.yotrip.net-rfp. You can go in there and choose your theme and then find the Whisker docs. That's www.w-i-r-e-t-r-i-p.net-r-f-p for Rainforest Puppy. Next. Isic. Okay. I'm sorry. I can't get over it. These are my favorite tools ever for testing this kind of stuff. It's not necessarily a new idea. It's just something that finally did it. Isic is a suite of utilities. There's Isic, which is IP stack integrity checker. TCP is stack integrity checker. UDP is UDP and ICP is ICP. And Isic is Ethernet, which is actually really cool. We found some interesting problems with that that we'll probably release sometime in the next millennia, hopefully. Great for testing protocol implementations on all of these, all of these. So we found the NetBSD bug, the remote crash, with an IC&P packet using... I'm sorry, it was an IC&P packet. It was unaligned IP options across an unaligned memory access using... Ah, it stopped working. There it goes. Using IC&P-SIC and the steps which were reproduced from the advisory. ICP... Or, I'm sorry, Isic. All the utilities are used libnet by route, which is also a great library. Beautiful code to read if you're into that kind of thing. State-based IDS is a packet filter. Wow. Basically, what these... I'm sorry, what these tools do is they send sort of controlled random packets. It's kind of interesting. So basically, you seed it with a random seed.  Works kind of like that. And so basically, if you enter the same random seed, you'll get the same random results. And it, you know, does IP options. It changes all the IP options. It changes the length. It changes the header length. Lies about the header length.  Basically, it throws a lot. It just pukes all over the protocol stack and sees that the protocol stack can take it. Because state-based IDS is a packet filter, or sort of kind of implementations of TCP-IP to an extent. God, it's hot. Our implementation of TCP-IP to an extent, this sort of vomiting works as well. And it's just like in-map with the state-based IDS, where from a certain IP I go a state-based IDS. I go SIN and wait a minute. I don't get an act. I get a fin immediately. You know, God, I'm screwed in an IQ. Same way with state-based firewalls, small IP packets, not necessarily tiny IP effects, certain fragment offsets. That's what else this is good at finding. Some things are sensitive to just certain fragment offsets. And if you run these tools for long enough, eventually you'll hit all of them. So, IP sect tunnels, same thing. In fact, I would, if someone would take these, Hugh Daniel and I talked about this a couple months ago. I don't know if he's done it yet. But he used to take HPING, some utility called HPING, to loopy and bake-offs and try and get other people's IP sect implementations to crash at the bake-offs. And I pointed out an ISIC, and I don't know if he's actually used it yet. I really hope he does, because I'm sure that it'll just make a whole lot of people's IP sect implementations just puke. And NAT as well. NAT once again. Testing from both, routing from both the trusted network to untrusted and untrusted to trusted and everything in between. Also firing directly at the untrusted interface of the firewall and at the trusted interface of the firewall as well can yield some different results. And also before, like I said, try all kinds of different configurations, one with the denial, one with an allow, two to allow, two allows and absorb, whatever. So here's the example. TCP SIC-S, which is the, specifies the source IP, RAND. If you specify RAND, it will pick a random IP for every single packet it sends out. It's pretty cool. Sometimes though, you don't want to do that because the firewall will just drop things that, like if you're testing from the trusted network to an untrusted network, for instance. I'll do questions at the end. If you're testing from the trusted network to an untrusted network and you aren't sending from the subnet of the untrusted network, the firewall will be smart enough to just drop your packet and you won't go all the way through the code pass that you need to to test them properly. So Dash-S RAND is a good way to do things. When you use Dash-S RAND unplug yourself from the public internet. All right? When you send, it's at a host. It's going to reply back to the source address, right? And if you hit some dot nil by accident or something and people come knocking on your door, that's why. Especially when you're using ESIC, because ESIC by default sends to the broadcast Ethernet address. It kills networks, okay? If you can hide a laptop store in an ESIC that's broadcasting, that's sending like Ethernet frames to the broadcast address, you will kill a network. That's not a legitimate testing though. It's just on the side. So, and then Dash-D is the destination. Trusted. So if we're going from untrusted. And set, be sure to set your random seed. If you don't set it, it uses the process ID of what it's running as right now. And so when you don't use Dash-R, like your PID is incremental or random and open BSD or whatever, you won't get consistent results. And I've seen this mistake happen with people who didn't understand the tool basically. They just, you know, they did Dash-S RAND, Dash-D trusted, and then they just went to town. And then like, they got something to crash and then they could never get to crash again and they were like, what was your random seed? I don't know. Well. Oh, well. So I usually use 3-3-3-7 or 6-6-6.  If you can't get like anything to happen in like the first 5 million packets or so, try changing the random seed to something else. Dash-M 700 limits, it's like the maximum, maximum not a package. You can pump out on the network kilobytes per second-wise.  Like, 4 meg per second, really fast. But as we mentioned in our NetBSD advisory, Linux mangles packets and doesn't tell you.  And so we tested it from BSD, it worked. Problem with BSD is that because for whatever architectural reason, it's not slower at sending packets. It has these things called NMB clusters that fill up very fast for whatever reason. So you can't send them as fast. If you send them as fast, it will drop packets. So instead of sending mangled packets, you still send the packets at all. And this can be a problem. So Dash-M 700, when we were sending from some ARM32 boxes, running NetBSD and also from OpenBSD and like some Pentium 2s or something, that seemed to be about right. And I don't think it has anything to do with how fast the machine is. I think it has to do with the drivers and how they're written.  Don't ask me how. I don't know anything about Unix. So the URL for ISIC, the suite of utilities, is htgbcon slash hash expert.cc.purdue.edu slash tilde f-r-a-n-t-z-e-n, that man's last name right there. So ex-p-r-t.cc.p-r-d-u-e.edu slash tilde fancy. And so that's slide eight. Next please. I was going to have a code example, by the way, but it got lost in the ether. So I can't do it. Define the, okay. So this is only loosely related, but as far as the kind of, the point of this is this kind of testing brings about certain problems, certain problems with memory allocation, not checking syscalls, not checking the return values of syscalls, various other problems. So just some suggestions for dev managers, for whatever else. For the love of Christ, don't just start coding if you're going to do something serious. All right, if you're going to write like a 200 line program, fine. Like get stoned, drunk, and like code until your fingers bleed. But if you're going to do something serious, define your interfaces first, plan first, try and maintain consistency in the interfaces. God, it drives me crazy. I really, really hate code that's just a total rat's nest. There's no consistency at all. So this is always a good idea, and if you're in a professional environment, modeling tools like UML, what else are in UML? National Rose, whatever, can maybe help you with that kind of thing. Writing well, writing clean, a well-documented code, I mean, like well-formatted, like you can read it, good comments, stuff like that. We'll save you time and anus later. A lot of people think it's a waste of time. A lot of managers think, no, we don't have time to clean it up, whatever.  When you think the code is going to be used for three months, you're going to rewrite it. It's going to last three years every single time. Have never seen it not happen. All right, this is a real pet peeve. All right, anybody tried to compile in-map like 2.08, or in-map anything pre-2.5?  Linux, GNU, not so much BSD, like GNU programs just all the time, or like the compiler gives you warnings for a reason, okay?  Please fix warnings if you see them. It's like the most simple thing that's overlooked every single time. Everything is source and runtime analysis tools. If you have loads and loads of cash to spend on Purify, but in SharePlus Plus and FlexAlent and stuff like that. If anyone wants to talk to me further about this stuff, I can talk about it at great length, but it's nothing to do with it. Who is supposed to be here? No, go back. I'll embellish and I'll name this for a minute. I was supposed to be here and I was going to ask the crowd for like, to tell me what was wrong with it. And so I'll put it up on the NuHack page or off my page off of NuHack and along with these slides and hopefully recording the talk and you all can send me mail saying what you see and be like, where's Maldo? Of land coding. So what I was going to do was for every guest that got right of what was wrong I was going to hand out a shirt.  For designers designers and coders if you're implementing on NT and you're interested in application level stuff use TDI transport something interface I can remember it as transport data transport driver interface, thank you. You can stuff pre-IP assembly so you don't have to duplicate work of the IP stack and further slow your IDS down. However, comma this only works on host-based IDSs which could be argued here IDSs doesn't really work. On and it works on Windows 95 98 whatever NT and Win 2K so if you write code it's going to be portable for the most part. The other thing you can use I didn't mention here on the slide is IP helper functionality is kind of interesting instead of like seeing maintaining your own state table. Excuse me. Just use the OSes in Windows 98 and NT starting the service pack for NT 4.0 starting the service pack for which is IP helper functions where you can actually get the connection table. You can see who's connected and not have to deal with maintaining your own state and duplicating your work.  In Linux 2.4 you can use net filter interfaces like the Linux crew actually has proper interfaces for something if you can find them such a thing. You can use the net filter interfaces to read yourself at whatever point in the stack you want to get data much like TDI slash and this on Windows. And this is what I highly recommend. I wouldn't bother re-implementing IP5 re-assembly, TCP3 re-assembly. It's just dumb, okay? Seriously. Seriously, okay? Because when you re-implement things there's those other things. Don't re-implement things, okay? Don't rewrite the libc calls.  When you write code you're going to make mistakes. When you rewrite code that's existed for 10 to 15 plus years it's been around for that long. People have probably found a lot of the bugs. People aren't going to find the bugs that are in your shitty code. Don't rewrite libc calls. If someone can argue with me later and prove me wrong on this great. I'd really like to be proven wrong.  Oh, and also when you're doing NAT and IP stack stuff use the free stuff. There's no reason not to. Try and find someone else who has a NAT implementation like Cisco. Like everyone in the world used Cisco's first reference implementation of IP stack. And it's a camp. And that's why they're all vulnerable to UDP garbage appendage bugs. But if it's a mature code and you're reusing it that's a good thing. You aren't wasting time. It's a really good thing. I can't stress this enough. If you have to argue with your manager about it tell him send me mail. I'll gladly argue. This is something I love arguing about. So there's a New Hexity webpage www.newhexity.net. There is not a whole heck of a lot there right now. I'm sure there will be in the future. We'll be able to buy various memorabilia and that's my email address. S-Y-K-E at newhexity.net N-E-W-H-A-C-K-E C-Y-T C-I-T-Y.net And that's it. So Q&A. If you're running Isaac and it sends like five million packets at your IDS and one of them crashes it how do you narrow down which one did it? Excellent question. Excellent question. It was something I overlooked and I forgot to add in. Isaac has two options. Dash P which says send this many packets and dash K which says skip this many packets. Mike should really be doing the talk on Isaac at this time. And so what you do is if you don't let it run overnight like try and pay attention like look every 500,000 packets or something and see if it crashes. J-R-U actually wrote a patch that pinged after every so many packets and I think maybe it was Mike told me someone like wrote a shell script or something that would send X number packets ping the host and like sort of incrementally go. Okay. He says there's one included in the tar ball. So if you get the if you go to the webpage export.cc.purdue.edu slash tilde F-R-A-N-T-Z-E-N it's in the tar ball. But to answer your question so you understand what's going on so what you do is like you know it crashed sometime between packets 2.5 million and 3 million sake of argument. So what you do is you do Isaac dash S whatever dash D whatever dash R whatever and then you do dash P for sending and you say skip the first 2.5 million when it skips packets it takes a really long time because it has to go through with the random things so you get the same results if you use the same random seed and then from there you do binary search it crashes again you say otherwise you know you expand your search a bit and so once you have the range you know the range you just start doing the binary search and you say okay it's between 2.5 million and 3 million right it doesn't do it that you know it's the other half and you just like you know I don't have to two hours to do that with a net BST exploit except I was lucky there where it didn't happen at 3 million packets it happened at like 30,000 something so that's how you do that that's an excellent question you get a T-shirt anybody else Mr. Balkan would you like to come up and how many intrusion detection did you test? how many he said how many intrusion detection systems do you test with whisker? with all these tools we're testing five five professionally or in my spare time huh huh together seven huh I really don't want to I would rather not advocate anything I don't work for vendor by the way as I'm sure you will all find out you're burnt out on this crap after a while and you just don't deal with it anymore you should that's why I'm doing this so people can test the stuff themselves so admins can go a vendor says it detects everything under the planet you know and then you can just you can test for yourself and if you really feel like it you can post a bug track and get you 255 T-shirts of fame huh so that's probably the reason for this talk I want to do this so people to enable people to do this themselves


Network TFNN headline news update. Good afternoon folks Steve Rhodes coming to you live from sunny Delray Beach Florida. This is your 1pm update and currently we've got all the markets trading to the upside. That was up 190 points about three quarters of a percent. Same with the S&P which is 25 points. NASDAQ 100 up one and a quarter percent 134 points. The big winner winner chicken dinner that goes to the semiconductor index up nearly two percent one in seven tenths percent 35 points to the upside out there. So we got a nice little rally going on counter trend rally right now you got the spot fix index trading out at 2848 and that is below it's a 50-day exponential moving average. Let's go ahead and start there take a look at the spot ball utility next trading right now 2848 50-day exponential moving average is 2673 that is where the spot ball utility index would have to close below for two sessions in a row to say that anything that is going on right now is anything more than a counter trend rally. At this stage of the game just a counter trend rally. Now you were to expect a counter trend rally to unfold today tomorrow why. Well if we take a look at the advanced decline oscillator for the New York Stock Exchange it managed to get down to nearly the minus 250 level on a closing basis. When you close at or near minus 150 that is technically oversold territory and you expect a bouncer bottom to form inside of the New York Stock Exchange. Right now we just have to call this a bounce that's all that it is at this stage of the game as time goes on the market will reveal more and more to us now. If we take a look at probably the key today is actually going to be Apple taking a look at looking for a message of the market so I'm going to expand this chart out here this is the daily time frame number two holding I believe inside of the NDX100. If this is just a counter trend rally that it ends right here right now right now one o'clock one o'clock one in the afternoon just kidding about the one oh one but it ends right here at one oh nine thirty eighty if we take a look at the brand new profile formed yesterday bullish and structure the center line is one oh nine thirty nine we're trading right now one oh nine forty one price closed below bullish structured profile yesterday if this is just a counter trend rally in apple then price will stop right here the center of that bullish structured profile so if apple closed above one oh nine thirty nine I'm not talking one oh nine forty but nicely closes above that then you can expect this to be at least a two-day rally because then that would signal that apple should make its way up to one seventeen twenty six isn't that a wonderful thing we're able to just narrow down the markets to just one stock and watch what it does to answer the question hey what's price going to do the rest of the afternoon and tomorrow folks stay tuned for two more great hour three more great hours of of shows out here if you're off to start your thursday have a thirsty one and we'll see you soon


Biden wants to avoid direct conflict with Russia over Ukraine. Since the very outset of the Ukrainian crisis, U.S. President Joe Biden has been trying to avoid a direct conflict with Russia, U.S. Secretary of State Antonin Blinken said, at Rice University's Baker Institute for Public Policy. From day one, President Biden had two North stars in mind. One was to make sure that we are doing everything we possibly can to support Ukraine and to bring other countries along to the same thing. But the other is also to avoid being in direct conflict with Russia, because the potential where that conflict could go is not a place that anyone wants to be and not a place that's good for the security of the American people, Blinken said during the conversation broadcast live by the Department of State's website. The top U.S. diplomat reiterated that it was up to the Kiev government to decide on its combat operations, but in his words, Washington has never encouraged strikes beyond Ukraine's borders. In his opinion, the best way to stop hostilities would be to strengthen Kiev's positions. Russia has repeatedly expressed its stance regarding the conflict in Ukraine at various levels. Russian Foreign Ministry spokeswoman Maria Zakharova noted that Moscow has always been and remained open for a diplomatic solution of the crisis and is ready to respond to truly serious proposals, while the Kiev regime cut and prohibited all negotiations with Russia.


Today I want to do something a little bit different. Now normally when we do a retro dojo episode It has been in the context of you know reviewing an old martial arts video game from the 80s in today's context I want to use retro in regards and in context of the actual martial arts and in terms of old martial arts footage and There's some really cool stuff out there and that's been one of the Unexpected benefits of doing research for this channel is over the past couple of years whenever we're researching the topic You know most likely in our usually historical videos We come across a lot of old footage and some of it is fascinating for various reasons And that's what I want to do today is kind of go over the appreciation of these clips and talk about what benefit Can we draw from them and what reservations should we have about them? The first thing is what I think is fascinating is it's an Absolute window into history. I mean we're talking about footage that existed before most of us were even born and It's like open up a window and just seen right back in time what things were like in early days of martial arts One cool thing is we can see the cultural impacts a lot of martial arts are the way they are because of either political Situations or religious situations or just the way arts developed So when we see these clips, we're seeing things from a more traditional times So a lot of times we'll see a lot more cultural aspects in them Which I think is fascinating now I know a lot of you out there might not like the idea of romanticizing the old arts or glorifying these old Arts because I know there's always a debate about what's better traditional and modern whatever that's a little relevant in this case But I have to admit and we all have to admit there is kind of a Mystique to see in some of this footage Especially when you consider that when this technology came out, you know the technology of moving pictures came out was at Or near the beginning of a lot of popular martial arts karate was fairly new Taekwondo was new or not even around yet when some of this technology came out You know Brazilian jiu-jitsu was just getting going judo wasn't that old So we're seeing the origins or early versions of a lot of prominent martial arts today And sometimes we were lucky enough to catch a last glimpse of the masters that we hold in such high regard today as well And it's also really fascinating just to see how arts have progressed. There was a cool Comparison I saw about a year or so ago Involving dogs there are pictures of popular dog breeds today and they juxtapose them with pictures of the same breed a hundred years ago And what's weird is though, you don't think there'd be much difference But there really was you know, you know legs were longer snouts were longer if you look at the hundred year difference in dogs You can actually see a progression a difference and it's the same thing when you look at this footage the martial arts I look at it and this is like wow so much has changed while you can see the roots are there But you can definitely see how things have progressed especially when you consider that fighting itself does change You know street fights that happen today don't look anything like the street fights that happened a hundred years ago You know tactics are different Moralities different environments are different clothing is different and fighting styles of education were different and you can see that in this Footage but to be fair and to issue some caution is what these clips should not be used for when you look at old archive footage like this You shouldn't look at them You be like a hot look that's how it's supposed to be done That's the only way that's the true lineage that is hands down black and white the way it should be done That black and white see what I did there no But the thing though is because things change, you know a lot of martial arts at the time We're still formulating in their arts You know teaching funicoshi and muscle Yama and you know They were still putting their arts together or they were fairly new and you had little more contemporary artists like Ed Parker with American Kempo who was always adapting and changing and modifying the art and in fact Ed Parker used to say that if people were still Practicing Kempo the exact same way in 30 years then something went wrong because it should always change because you know What's popular changes, you know, Brazilian jiu-jitsu grappling is very very popular now But you go back 50 years and it wasn't so it's just important to understand that Just because it's on film and it's old and ancient doesn't mean it's the way it has to be done today Things change and I think that's one of the most important lessons to take for the martial arts is it's all it's organic The arts are organic and they always have to adapt and grow with us and one of the things that jumps out to me And this was just kind of an observation on my part that I found kind of fascinating Is that if you look at these clips, you know, some of these some of these clips are 100 years old, you know But like 80 90 years old look how fluid and detailed some of these motions are now Compare that to a lot of the movies immediately that we grew up with at least here in America back in the 50s and 60s and 70s You know, you did not see movies do martial arts to this complexity and it kind of shows you the difference in audiences So to be fair anybody watching these old clips back in the day, you wouldn't have come across it on TV They didn't air the stuff and YouTube certainly wasn't around so unless you were in the martial arts You didn't really encounter these clips. So those who saw these knew what they were looking at and they understood techniques They understood the complexity they understood, you know, the meaning behind a lot of the moves whereas The movie going audiences at least in America and the audience on TV. They didn't have that understanding So it's interesting to see that the martial arts of the 50s and 60s and 70s on TV shows and the films were very simple You know basic kicks basic ground kicks basic punches, you know The fight choreography was much much simpler and rudimentary compared to what we have today You know now movie fight scenes are almost like hyper realistic You know the stuff they do it's far more complex than what's realistic But yeah, if you go back to the 50s, the average American didn't even know what karate was But yet here is this footage of showing it alive and well now just to be fair to When I talk about it's impressive to see how fluid some of these motions are and how quickly these masters moved or martial artists move Just to keep in mind martial arts look faster on film Generally speaking than they actually do in real life. One reason is especially if it's 80 years old or around that time It was shot at a lower frame rate So what we're seeing a lower frame rate played back at our current frame rates It speeds up and that is and was a common movie trick for martial arts films Is you shoot at a slightly lower frame rate like a 22 frames per second It's so when it plays back at 24 It has a speed up and it makes the action look a little bit You know faster and flow a little bit better and also to Unless you're shooting with a high shutter rate You're gonna get a lot of motion blurs and you're not gonna pick up a lot of the speed and motion blurs also make things psychologically look faster, so Some of these customers like oh, wow, they're just like flying and that must be a blur in real life They might have been but there's also just take that with a grain of salt that sometimes old footage Appears faster than it really was. So why am I doing this topic today? Well, basically like I said I wanted to do an homage and show an appreciation to history of the martial arts since we talked so much about history It's nice when we can actually physically look at history because there's way too many arguments that happen about who is better at what they do Which art is better what works or what doesn't work and you know, it's on video It's not a video there's always debates But sometimes it's good to stop and just take a look at how it was done and regardless of what art you train or what you think System is better than not. There's a lot of archive footage of popular art today And that's including Muay Thai and Taekwondo and even Brazilian jiu-jitsu in its early days And you can see a lot of stuff has changed, but I think regardless of what art you train in I think it's worth stopping from on it and taking a look and appreciating the past because The more we understand about where we came from and what our martial arts are today from where it started The more we can understand where it's going because it's organic fighting styles change different things are popular Like I said, you know grappling is super popular now. It wasn't 50 years ago Who knows what's gonna be popular in 15 20 30 years? Maybe tricking is gonna be the way to fight We don't know but I think it's kind of interesting to think about since we have all this technology now the kind of footage That we're gathering these days. I can only imagine what they're gonna be looking at a hundred years from now I'll be like, oh wow find an old YouTube clip from 2021 whatever be like wow That's how they used to use that technique so weird So I think it's worth stopping and taking a look and appreciating our history Taking a peek to a literal window of time and seeing the grandmasters at work and seeing how people train and seeing the cultural Impact and just seeing the discipline and just understanding our past. I think enriches the martial arts So much even if it's just for a few minutes just to take an appreciation So thank you guys so much for watching today. I would love to know what your favorite clips are There's a ton of them out there if you go on YouTube and I've you know the ones I've showed you today I've got a list below in the description, but you could spend hours finding clips There's a ton of them and I think they're worth looking at just again for depreciation So let me know what your favorite clips are Let me know your thoughts below what changes have surprised you or what changes are you looking forward to seeing and Be sure to like this video subscribe and we will see you next week. Thank you so much


Hey everybody, it's Nerdiversal here with the very first video of Halloween! I know it's October and I know it's not exactly Halloween yet, but it's- it's Halloween! So for the first video for this season, because you know I gotta go hard, we're gonna be doing my top five horror Vocaloid songs. These range from disturbing to creepy, um, but I hope you guys enjoy! Let's get started! So at number five, we have Go Mende Go Mende by Kikuo. So this song is at the top of the list because it's less of a traditional horror-sounding song, but it's more disturbing than anything. I wouldn't really call it scary, but it is definitely disturbing and creepy. This song is about a girl who grows up enduring sexual abuse at the hands of her father. At some point in the song, she falls in love with another boy because he's treating her gently and pitting her abuse. She runs away with this boy, but at this point she's so abused and conditioned to believe that she's a bad person and the abuse is her fault that she returns home to her dad, likely believing that she doesn't even deserve to be treated well. It talks about what happens when she goes back home, but if you really want to know, I recommend listening to it because it's some pretty dark stuff that I honestly don't really want to say out loud. The song itself and the lyrics have some really disgusting and grotesque imagery, so if you're going to listen to it, definitely be prepared. Personally, I like this song because when I first listened to it, I thought it was just like a fun Miku song, you know, it had like a good dubstep beat and stuff like that, but I started noticing some like weird things in the sound, like some kind of creepy weird noises, and then I read the lyrics and I read the comments and I was like, oh, this is bad. This is really, really bad. And honestly, I couldn't even really listen to it after that, even though I really liked the beat, but every now and then I'll return to it and think, wow, this is really fucked up. Number four on the list, we have wide knowledge of the late madness. So this song is actually a prequel to another song on the list, which I think is why I like it so much, aside from like the eerie tune in the video itself, but we'll get into that after this. So the song is about a patient who gets taken to a hospital or a facility of some kind. It's never stated why exactly, just that the main character is there, but every night they pick a new patient to take to the pretty room down the hallway, and they start chopping off and mangling body parts, probably without anesthetics, and there seems to be an animal or creature that also eats some of these body parts. The main character is next to be taken to this room, but is excited since she seems blissfully unaware of what happens in that room. There's a video that goes with this song, so I recommend watching the video when you listen to it, but it ends the video with the next song on this list, which it is the prequel for, so let's go there. So number three, we have Darkwood Circus, and this song tells us exactly the reason they were cutting people up in the last song. In this one, a little girl goes to a circus called the Darkwood Circus, where they have all kinds of deformed people perform. If you watch the video to the white knowledge of the late madness, there's some parallels in the people they show here. For example, the one with two heads in the video is created from Rin and Lin from the first video when they both got their heads cut off to make this new person, and the creature that it had talked about that ate the body parts also comes out this Kato, the blue beast that loved to eat things cold.  And the song ends with it implying that the main character that went to the circus is actually a part of it too. This one is another one with a good video, so if you listen to it, watch it as well. Number two on the list, we have Rugrats Theory. We are getting into the good stuff personally, I think. So this song is based on a creepy pasta theory about the Rugrats, which if you're familiar, it's just an early 2000s show about babies doing things and getting into trouble. The theory goes that none of the kids are actually real and they're all a part of Angelica's schizophrenic imagination, and she eventually goes on to doing heavy narcotics in order to keep these hallucinations, and she dies from these narcotics. The theory is pretty dark, and while I know it's a little bit ridiculous and it's definitely not the intended story of Rugrats, this song is creepy as hell. If you want to read more about the theory, I'm including a link to the creepy pasta fandom in the page description. I think Reversed Audio is really scary, and the beginning of the song is just that, it's reverse tunes, and it also has some pretty creepy sounds later on as well. But god, that freaking Reversed Audio, bro. And actually, a side note to a test of the weird kid I used to be in early high school, I used to listen to this for fun on the bus home because I think it's actually a pretty good song, but I could never listen to it by myself though. I'd probably just get way too creeped out. Number one on the list, we have Secrets of Wisteria. Number one on the list, oh boy. This one deserves its spot as number one.  This one is another one that has a video to go with it, and I definitely recommend watching it. It's very well animated and adds some creepy imagery to the already existing story. But for those of you that don't know, this song is based on the real story of Albert Fish, also known as The Werewolf of Wisteria, among other names, and his victim 10-year-old Grace Budd, who, by the way, was the girl whose murder got him convicted.  He was a suspect in at least five murders, but only officially confessed to three of them and stabbing two other people. There's a lot of really awful things about this guy, which if you're interested in, I'll include a link in the description. But the most important thing to note is that this guy preyed on so-called easy targets, such as mentally disabled orphans or homeless black children. People he assumed wouldn't be missed. However, when he killed Grace, she was taken from a family who knew where she was at when she died.  He actually sent a letter to this little girl's mom, describing in gruesome detail what he had done to the daughter.  But a snippet of this letter is featured in the song as a reverse audio.  I'll be honest, but if you see it, how do you boost it? If I did it so self-sacrifice less than you swat, it's the meat in your book. Spirits, damn, it's the gusset. It says your mom's there as a man. That means there's more to it. I choke her to death, then cause her in small pieces.  How sweet and tender the last one's roasted in the oven. It took me nine days to eat an entire body.  I could have, but I wished.  In the song, it mentions that more than just Grace Budd were murdered by him, and it gets gross about talking about their decaying bodies and stuff.  Definitely worth the watch. Also, by the way, he's been dead since 1935. Very good stuff. All right, everybody, that's all on my list. If you guys got any more Horror Vocaloid songs that you think are really cool or really scary, definitely put them in the comments below. I love hearing stuff like that, especially for the month of Halloween. And if you guys enjoy content like this, stick around for the month, because I like to go big for Halloween. I like to actually make content for Halloween. So I hope you guys enjoyed this video. Subscribe if you like it. See you guys, bye.


so i'm basically doing this video to support my brother kobi chain this is a zebra crossing right here and we have to the cast needs to stop or else to cross here in Ghana they don't even respect the zebra crossing see it's still green zebra crossing everyone is waiting for me to cross it's red so now i need to stop for the cast to move why can't we respect a simple instruction zebra crossing somebody is saying that you will never respect zebra crossing because it's not a zebra how can we live in africa i think like that man respect that zebra crossing see it's red


Good evening, I am Ifani El-Mazem. This is the news now. As the House of Representatives began its oversight on the Nigerian armed forces in the face of heightened security challenges in the country, the Nigerian army says it has recorded major successes in carving banditry and insolvency in the country. The army chief said they is doing his budget defense session with the House committee and army. Our correspondent Emmanuel Hegine completes the report. Insecurity remains a high-drill-headed challenge across states in Nigeria, but the government has continued to say it is up to the task of defending the citizenry in the face of many deaths, kidnappings and banditry. The chief of army staff was at the House of Representatives to defend the institution's 2023 budget, seizing the occasion to address various steps taken to tackle insecurity in the country so far. For the Nigerian army, it means consolidating the gains recorded in tackling insecurity in its battle sheets and the attendant challenges. It is called, it is a call not to slide, it is a call not to sleep, and it is a call to strategize and ultimately conquer the enemy. Before we proceed, let me on behalf of the committee acknowledge the vision of the current chief of army staff, which is to have a professional Nigerian army to accomplish assigned missions within a joint environment in defense of Nigeria. The vision we set us around working in full collaboration with heads of other sister security agencies, no doubt contributed immensely to the recent successes recorded by our security forces in the counterinsurgency, terrorism, operation, fighting, banditry, kidnapping and other criminal acts that threaten our collective existence as a nation. The chairman, committee on army, Honorable Abdul Rezaq Namdes, sets the tone by commanding the chief of army staff for the successes recorded so far in the fight against insurgency, banditry and kidnapping. In his response, the army chief commands the lawmakers for their support to the army but is quick to call for increased welfare packages for soldiers. These efforts require deliberate investment in personal welfare, leadership capacity building, procurement of necessary equipment, platforms and infrastructure, which are hinged on adequate funding. I recognize the need to constantly boost the morale of the fighting troops. Hence, I pay them constant operational visits to give strategic guidance. This approach has been yielding good results as observed in the unprecedented surrender of Boko Haran Therese and their families since I took over the mantle of leadership. Significantly on the human resources and lean finances available to Nigerian army. This therefore calls for a review of the current envelope budgeting system. The envelope system leads to adequate funding of Nigerian army for the performance of its constitutional duties. The committee deserves into an executive session to address all the sensitive security matters of national interest. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Today's theme is humans 2.0, designing and implementing a future-proof strategy. In the recent Brightline study, 59% of senior executives admit that their organizations struggle to bridge the gap between strategy and implementation. It's easy of course to be enamored with new strategies and great new technologies, but it's much more important to recognize that all strategic change is implemented through action plans and projects themselves. What we see today is an absolutely massive development of technology. We move technology at the lightning speed, at the lightning speed. Computers are faster, AI, VR, everything is moving. But are the humans moving at the same speed? Now, when we speak about the future of work, you have to understand really what kind of mega-trends are hitting our workforce. Number one is shifts in technology and digital productivity. So automation, AI, robotics, analytics, number two, data, access, access to people, etc. So the first three things are all about digital and this is probably the mega-trend of mega-trends. And finally, people are looking for purpose, so purpose and well-being. You don't work only for money, only to get dividends. But you work also because you want to accomplish something and bring everybody together. So as leaders, I think it's really important that we show them, we show everyone where we're going and we take everybody with us as well. I think that what people are actually thinking is that they need to actually keep themselves broad and they need to be continually learning. People are going to have to get used to training their whole life. You're not going to train for one job and stay with that. It's going to be this continuous learning. And we need to think how we're going to deal with that, both as employers and also as a society. So how on earth do you recruit people based on their potential rather than their CV? Each time you feel you have exactly the same picture. 25 years of experience, diploma or qualification and nothing about talent or potential. Collaborative, creative, sometimes team spirit or not depending on the job you will apply. But today when you recruit through a resume, you don't see anything. And that's the point. We asked 366,000 job seekers where they would like to work, what is important for their job, what kind of job preference they have. The top three had something to do with culture. Number one was relationship to colleagues. Number two was work-life balance. And number three was relationship to the boss. So one and three is the microclimate. And therefore also in recruiting, you have to let's say offer a personal touch because people will want to see how you work in your company. Number four actually was what are my training opportunities. And number five what are my career opportunities in this area. I believe it's somewhere between 8% and 13% of the workforce are actually engaged. Which means 87% at best aren't. Then we would even say some are disengaged and some are even actively disengaged which are disengaging others. Engagement is highly critical for success as an individual and as for companies and organizations. So what I found to be interesting is the continuous learning aspects that are required in the future and how engaging that is by definition. So there's a huge gap that needs to be filled. That's about us as leaders in these businesses. So I think that personal responsibility we have to take on board. I do have a question around you're talking about purpose-driven companies and best of the shift. How do companies prepare for that and work every day? I think the important thing is that you shouldn't do something that doesn't fit with the core business of your company. You need to do something that's sustainable. And so therefore you have to identify what business am I in? What value can I bring to the world? What impact can I make with that? And interestingly I was in Israel recently and I was talking to Sir Ronald Cohen and he is a firm believer that businesses are just not going to be measured by their bottom line but also by the social impact they bring and it will be a measure and it may be combined. And that a business that's generating 10 billion a year but having no impact or negative impact is not going to be worth as much as a business generating 10 billion a year but having that positive social impact.


I decided to join the Army because it is something that I've always wanted to do. I really thought that I would regret it if I didn't. I made a right hand turn into the recruiter station in my third year of college because it was something that I was so passionate about. I saw the movies, I saw the camaraderie, and it's something that I really wanted to be a part of. I continue to serve in the Army because it's something that I'm very passionate about. I love my soldiers, I love what I do, I love my profession, and I'm just thankful that I am here.


Welcome to ITU Telecom World 2018 here in Durban, South Africa, where I'm very pleased to be joining the studio today by Tim Sherwood, who is Vice President of Business Development and Mobility and IoT Solutions for Tata Communications. Tim, welcome to the studio. Thank you. Now I'd like to start off by talking about MVNOs, mobile virtual network operators. Perhaps you could tell us a little bit about what MVNOs are and what role they play in today's ICT's landscape. Sure, so MVNOs actually vary depending on different types of models that they employ. Some are very simple resellers of mobile operator SIM cards, if you will, whereas others are more sophisticated and control more capabilities themselves to operate and offer more specific plans that they want to target for their customer segments. Traditionally, the MVNOs went after the consumer mass market, targeted different types of specialized ethnic groups, low value, but what we've seen really recently is an emergence of a wide variety of MVNOs not only focused on the consumer model, but also in the enterprise space, particularly around IoT. And what are the key trends to be watching out for in the MVNO industry then? What we're really keeping an eye out is enabling anyone, if you will, to become an MVNO. We're seeing, particularly when you start talking about smart devices, the internet of things, that more and more enterprises are shifting from a product model to a services model and connectivity becomes a key embedded ingredient of that. So while they don't necessarily think of themselves as an MVNO like a traditional consumer brand, they are in essence an MVNO as part of the broader service offering that they're making. And in terms of obstacles in this particular market, how might they be overcome then? So some of the obstacles that we see really center around MVNOs that want to offer their services across multiple countries. And so working with different local operators in each country can be challenging in that the different method by which you can acquire and utilize their local spectrum, their radio access can change across. And so then you become limited to the least common denominator of capabilities if you're heavily relying on the operators. And so we're seeing a movement more towards virtualized platforms that handle different types of subscriber management capabilities, policy charging, different types of business rules that the MVNOs can operate as an overlay above all the different radio networks from the partners they use so they can offer a consistent and seamless service across multiple countries, across multiple operators. And what about regulators? What kind of regulatory landscape would you like to see? Well, I think the regulators tend to be very much of a follower when it comes to different approaches. And in some cases we're seeing regulations that don't necessarily put an advantage to an MVNO. One example of that would be in India, which is still a large degree a key market for us. And there with some of the recent regulations, they require a virtual network operator to be tied to a single operator. And what we're seeing in other markets around the world is a key differentiation of an MVNO is actually that they're providing coverage across multiple local operators. And so that mesh value of multiple underlying operators is critical for a value prop, let's say, in the U.S. where I'm from. But because of the regulation in India, you don't see that. So there are types of issues there that we see that we think the regulators could be a little bit more forward thinking and looking at the MVNO as a way to really enhance the end user value or the enterprise value. And they just need to be a little bit, play a little bit more catch up, I'd say. Talking about value, you've obviously taken the time and the distance has been traveled by you to be here. I just wanted to find out what's the value of attending events such as ITU Telecom World for you? So for us, in the MVNO space, we actually look at ourselves as both as a mobile virtual network enabler as well as a virtual network operator. Where we operate as an MVNO, we're targeting our multinational companies, our service provider customers to help them reach global scale. In certain markets, particularly in Africa and other emerging markets, we recognize that we may not have a strong local presence ourselves. And so we have and are seeking partnerships here to build a presence to kind of create a federation or a coalition, if you will. And so we see a lot of exciting things happening in places like Southern Africa with the explosion in terms of the opportunities for MVNOs, both on the consumer side and the IOT side. And so we're really looking at how can we help, how can we extend some of our capabilities? How can we can enable our partners to be successful in the local markets that they specialize in? Tim Sherwood, thank you very much indeed. Thank you.


school, and family expectations. Conference. A conference is a meeting for parents, students, and teachers. In many elementary and middle schools, parent-teacher conferences are scheduled at least twice a year. Homework. Homework is schoolwork that is done at home or after school. Homework allows students to practice what they learned in school. Students in all grades have homework. Participate. Participate means to do an activity. Students in school are expected to participate in their class discussions by asking and answering questions. Grades. Grades are the result of a test or assignment. They show how a student is doing in a class. Grades are usually given as numbers or letters depending on the school. Report card. A report card is a document that shows a student's grades. Sometimes report cards also have teacher comments. It is important that parents review their children's report cards. Expect. Schools expect students to do their homework, to come to class prepared, and to participate. Expect means to think something will happen in the future. Note. A note is a short written communication. Notes can be written on paper or sent via email. When a child is absent from school, a parent needs to send a note to the teacher. Extracurricular activities. Extracurricular activities are activities that are completed outside of the normal school day. Students can participate in extracurricular activities like sports and clubs. Standardized test. Standardized tests are tests given to all students at certain grade levels. In Washington, students take smarter balanced math, reading, writing, and science tests. Behavior. Behavior is how a person acts. Students are expected to show good behavior at school. Parents of students who do not behave may be asked to meet with the child's teacher. Absent. Absent means not in attendance. Students who are absent from school must bring a note from their parent when they return to school. Get involved. Students are encouraged to get involved with volunteer and extracurricular activities while they are in school. Get involved means to take part in activities. The end.