I'm hazy on the details but ISTR sports deriving from wardances which dervied from a desire not to have all your warriors killed just to figure out who got to use the better stream for the following month.
Almost any level of accuracy above pure randomness can be fruitfully added to the bayesion inference process. You can pretty harmlessly add the pure noise as well, it's just not going to be fruitful.
Since many people browse from poorly secured wifi segments, it can happen more than you might think. Also, since a large proportion of wired networks do not have their first-hop-security features turned on (and can't in the case of ipV6 because they lack the features) opportunities are readily available.
Yes, and while that can sometimes be funny, and more often be so stupid as to cause me to channel surf, this was bad taste in a way that was neither funny nor boring; it was just bad taste, period.
Answer: So that when someone browses to your URL they don't get malware injected into their browser by a MITM.
That said, GP nails it: the problem with SSL is not the tech, it's the that the CAs are money grubbing semi-competent boobs, and the trusted certificate lists are administered by either OS or browser producers leaving a huge open arena for politics and perverse incentives.
Yeah, really corporate liability concerns are the core of the matter here. Nations and individuals can stand up to assholes like these guys, corporations will only do so when the profit/loss projections favor it. They are truly the weak link.
Not that the movie plot wasn't in rather poor taste in the first place. I kinda cringed when I first saw the ads, as it is sort of in the uncanny valley between an absurd envelope pusher and a bland clown show.
Yeah, who's to say the AI wasn't just seeing something we can't. Obviously aliens beamed a subliminal picture of a schoolbus into the TV static and the AI said Oh, a schoolbus!
When, Lord?! When the hell do I get to see the goddamn schoolbus?
Don't try to argue with culturally instilled puritancal "work ethic" a.k.a. self-hate and victim blaming, as it isn't rational, and probably won't go away for quite a few generations yet.
Yes, we have three brands of edge switches (HP,Cisco,Aruba), Aruba wifi and Cisco routing. NAC is Extreme, Shaper is Procera. Integration is a pain sometimes, but we're well over the hump and now when a vendor walks in to sell us stuff they don't act like they own the place, and requiring standards compliance and interoperability tends to get us the better products in the ong run, IMO.
This. If you can convince some tech company to hire you as a technical writer you'd not only be able to learn a different field as you work, you'd be doing the entire industry a favor since good documentation is teetering on becoming a lost art.
No, he's definitely right. Work/life balance is definitely a factor in retention. If you can't check into your home security cam to see if your dog is chewing on the sofa, that may be worth a couple hundred in salary to you, and tens of those little things add up.
...but balefully less well documented, and full of feature sets that managers want to turn on that make it less reliable than the old gear/ware.
Really, if equipment and software providers would spend even 10% of what they do on sales on good documentation written by technical writers with priority access to engineers, IT would be 5 times simpler, and the presence of the documentation would more than make up for the lack of a few powerpoint slides and SE visits. Almost ALL my time is wasted trying to either figure out product behavior on my own or rub elbows with enough people until I find someone who can offer proper technical answers.
I have to agree with GP. SAN and virtual infrastructure isn't cheap, but neither are competent rack monkeys or business quality switchports. As long as you can avoid some of byzantinisms of managing the VMs it's better to have a sysadmin that does VM management part time than waste your network guy's time doubling as a rack monkey when he needs to be plumbing new features on the equipment. You end up with more talent at your disposal.
I keep getting marketing literature from companies promising that. But it never seems that they can deliver on their claims.
Yeah pretty much it goes like this:
1) Outsource existing application, burn out your IT staff on the migration effort, lose some IT staff 2) Try to get new application customized to a new need. 3) Remaining IT staff tied up in meetings and phone calls delineating the new need to the service provider. 4) Refresh all progress made in 3) again when your point of contact at the provider moves on to another company. 5) Eventually end up with consultants from the provider working as many FTEs on premisis as your IT staff did.
A company is rarely going to lose their shirt because someone found their marketing material in cyberspace
No, but they will surely raise holy hell when there's a BGP problem that kills access to the DNS server for their cloud service app and they can;t get any work done for a day while the ISPs bang it out.
Also some idiot will eventually drop PCI data on the cloud service, even if the service has no place to put it. They will find a way tp let their idiot light shine through.
I.... am glad I don't have your problems. Really the user base has gotten too lethargic. An occasional day-long outage due to an arp spoofing attack that the cheap-ass prosumer equipment cannot block can do wonders for an IT budget. Of course that's a lot of firing/hiring musical chairs because they won't remember that you told them the crap stuff wouldn't cut it.
Have fun with that "backplane" capacity:-)
(BTW these days you'd be looking at a 6800 not a 6500 unless buying used, and the Nexus only if you've got some majorly complex things going on in the server room. Also we gave up on paying the cisco premium on the edge a while back, and have never looked back. While Cisco has been fiddling with SLA, other folks have made much cheaper alternate edge switches with fully adequate feature sets.)
A VM runs its own kernel. Containers share a kernel, but have their own namespace so e.g. they see only their own process table chroot jails just really control permissions and environment/libs
On the one hand all of them have some pretty compelling use cases like ease of moving machines to new/backup hardware. On the other hand they all lend themselves to horrible abuses and serve to keep crummy, buggy, code in service way past when it should be flushed down the toilet with extreme prejudice, and attract a swarm of people with awful instincts to create heinously bad UIs to administer them. And as someone noted above, often require network contortions after the fact when folks realize that yes, they needed some IPC between containers.
You think that's bad, you should see what goes on on the network side these days. All the layers of encapsulation can very often be larger than the innermost payload.
These days for heavy remote X use you use stuff like Xpra, also over SSH, as it can leverage hardware encoders which the X protocol didn't have at its disposal back when it was designed.
Slashdot Mirror
I'm hazy on the details but ISTR sports deriving from wardances which dervied from a desire not to have all your warriors killed just to figure out who got to use the better stream for the following month.
Almost any level of accuracy above pure randomness can be fruitfully added to the bayesion inference process. You can pretty harmlessly add the pure noise as well, it's just not going to be fruitful.
no MITM injection required
You say that like MITM is harder than setting up a server and socially engineering people to it. It isn't these days.
Since many people browse from poorly secured wifi segments, it can happen more than you might think. Also, since a large proportion of wired networks do not have their first-hop-security features turned on (and can't in the case of ipV6 because they lack the features) opportunities are readily available.
Yes, and while that can sometimes be funny, and more often be so stupid as to cause me to channel surf, this was bad taste in a way that was neither funny nor boring; it was just bad taste, period.
Answer: So that when someone browses to your URL they don't get malware injected into their browser by a MITM.
That said, GP nails it: the problem with SSL is not the tech, it's the that the CAs are money grubbing semi-competent boobs, and the trusted certificate lists are administered by either OS or browser producers leaving a huge open arena for politics and perverse incentives.
Yeah, same here. Kept ending up with certs presented from a CDN's domain.
Yeah, really corporate liability concerns are the core of the matter here. Nations and individuals can stand up to assholes like these guys, corporations will only do so when the profit/loss projections favor it. They are truly the weak link.
Not that the movie plot wasn't in rather poor taste in the first place. I kinda cringed when I first saw the ads, as it is sort of in the uncanny valley between an absurd envelope pusher and a bland clown show.
Yeah, who's to say the AI wasn't just seeing something we can't. Obviously aliens beamed a subliminal picture of a schoolbus into the TV static and the AI said Oh, a schoolbus!
When, Lord?! When the hell do I get to see the goddamn schoolbus?
Antiseptics are not so impacted, and are the more likely agent to be used for a skin cut.
Oh noes! Daywalker Goths!
Now we have to look at all those gross piercings in the full light of day? Ick.
Don't try to argue with culturally instilled puritancal "work ethic" a.k.a. self-hate and victim blaming, as it isn't rational, and probably won't go away for quite a few generations yet.
the blimps don't have cameras, and even if they are installed, the range drops from a 340 mile radius to "dozens" of miles
Even if they had absurdly powerful telescopic cameras, at that angle all they would see in most areas is the tops of trees.
Yes, we have three brands of edge switches (HP,Cisco,Aruba), Aruba wifi and Cisco routing. NAC is Extreme, Shaper is Procera. Integration is a pain sometimes, but we're well over the hump and now when a vendor walks in to sell us stuff they don't act like they own the place, and requiring standards compliance and interoperability tends to get us the better products in the ong run, IMO.
This. If you can convince some tech company to hire you as a technical writer you'd not only be able to learn a different field as you work, you'd be doing the entire industry a favor since good documentation is teetering on becoming a lost art.
Of course the pay might not be especially great.
No, he's definitely right. Work/life balance is definitely a factor in retention. If you can't check into your home security cam to see if your dog is chewing on the sofa, that may be worth a couple hundred in salary to you, and tens of those little things add up.
The technology is better and more reliable.
...but balefully less well documented, and full of feature sets that managers want to turn on that make it less reliable than the old gear/ware.
Really, if equipment and software providers would spend even 10% of what they do on sales on good documentation written by technical writers with priority access to engineers, IT would be 5 times simpler, and the presence of the documentation would more than make up for the lack of a few powerpoint slides and SE visits. Almost ALL my time is wasted trying to either figure out product behavior on my own or rub elbows with enough people until I find someone who can offer proper technical answers.
I have to agree with GP. SAN and virtual infrastructure isn't cheap, but neither are competent rack monkeys or business quality switchports. As long as you can avoid some of byzantinisms of managing the VMs it's better to have a sysadmin that does VM management part time than waste your network guy's time doubling as a rack monkey when he needs to be plumbing new features on the equipment. You end up with more talent at your disposal.
I keep getting marketing literature from companies promising that. But it never seems that they can deliver on their claims.
Yeah pretty much it goes like this:
1) Outsource existing application, burn out your IT staff on the migration effort, lose some IT staff
2) Try to get new application customized to a new need.
3) Remaining IT staff tied up in meetings and phone calls delineating the new need to the service provider.
4) Refresh all progress made in 3) again when your point of contact at the provider moves on to another company.
5) Eventually end up with consultants from the provider working as many FTEs on premisis as your IT staff did.
A company is rarely going to lose their shirt because someone found their marketing material in cyberspace
No, but they will surely raise holy hell when there's a BGP problem that kills access to the DNS server for their cloud service app and they can;t get any work done for a day while the ISPs bang it out.
Also some idiot will eventually drop PCI data on the cloud service, even if the service has no place to put it. They will find a way tp let their idiot light shine through.
I.... am glad I don't have your problems. Really the user base has gotten too lethargic. An occasional day-long outage due to an arp spoofing attack that the cheap-ass prosumer equipment cannot block can do wonders for an IT budget. Of course that's a lot of firing/hiring musical chairs because they won't remember that you told them the crap stuff wouldn't cut it.
Have fun with that "backplane" capacity :-)
(BTW these days you'd be looking at a 6800 not a 6500 unless buying used, and the Nexus only if you've got some majorly complex things going on in the server room. Also we gave up on paying the cisco premium on the edge a while back, and have never looked back. While Cisco has been fiddling with SLA, other folks have made much cheaper alternate edge switches with fully adequate feature sets.)
#like
A VM runs its own kernel.
Containers share a kernel, but have their own namespace so e.g. they see only their own process table
chroot jails just really control permissions and environment/libs
On the one hand all of them have some pretty compelling use cases like ease of moving machines to new/backup hardware. On the other hand they all lend themselves to horrible abuses and serve to keep crummy, buggy, code in service way past when it should be flushed down the toilet with extreme prejudice, and attract a swarm of people with awful instincts to create heinously bad UIs to administer them. And as someone noted above, often require network contortions after the fact when folks realize that yes, they needed some IPC between containers.
You think that's bad, you should see what goes on on the network side these days. All the layers of encapsulation can very often be larger than the innermost payload.
These days for heavy remote X use you use stuff like Xpra, also over SSH, as it can leverage hardware encoders which the X protocol didn't have at its disposal back when it was designed.