Jump to content

So, "glitch" on Wall Street, United Airlines and WSJ ... coincidence ?


AURaptor

Recommended Posts

NYSE repoens after trading stopped amid United Airlines, WSJ.com tech issues

LINK

Link to comment
Share on other sites





No worries. barry will be quick to surrender...

Link to comment
Share on other sites

Also heard there was some cyber games going on by the US military.

U.S. Agencies Conduct Cyberwar Games

Pentagon, Homeland Security, NSA and others join British officials and private companies for three-weeks of exercises

http://www.wsj.com/articles/u-s-agencies-conduct-cyber-war-games-1436069213?mod=WSJ_TechWSJD_moreTopStories

( sorry, I don't have access to the WSJ. Even after the attempted hack job. )

;)

Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha
Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha

(Forgot the dancing bananas.)

Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

No one is more predictable that Timah. Well, except maybe Raptor and Proud.

Link to comment
Share on other sites

And yet, neither AURaptor or Proud made 1 mention of Barry.

Huh.

Link to comment
Share on other sites

Considering the timing (yesterday morning), and some of the patches I noticed on my WSUS server yesterday morning, my initial speculation would be that a few system admins discovered why WSUS auto-approval and group policy auto-install can be a dangerous combination.

Link to comment
Share on other sites

I blame it on the Whiskey.

Link to comment
Share on other sites

Anonymous apparently had a tweet the day before the glitch. Something about hope Wall Street does not have a bad day tomorrow. It's possible it was a coincidence, I mean the planets do line up in a row from time to time. That is a coincidence, but it is a very rare occurrence.

Link to comment
Share on other sites

Anonymous apparently had a tweet the day before the glitch. Something about hope Wall Street does not have a bad day tomorrow. It's possible it was a coincidence, I mean the planets do line up in a row from time to time. That is a coincidence, but it is a very rare occurrence.

All anyone has said so far is that it was an internal technical issue. Anonymous did not "hack" the New York Stock Exchange or United Airlines, and I doubt they have an insider (which would be required) in either place with sufficient access AND a willingness to sacrifice their job AND face potential legal issues.

Link to comment
Share on other sites

Just because they say it wasn't hacked from the outside doesn't really mean it wasn't .

Our government told us that Benghazi was because of a YouTube video. It wasn't.

Link to comment
Share on other sites

Just because they say it wasn't hacked from the outside doesn't really mean it wasn't .

Our government told us that Benghazi was because of a YouTube video. It wasn't.

Hacking doesn't really work like it does on TV. To actually hack a secured network requires a tremendous amount of knowledge about what they are using at every level of their infrastructure. You need to know the specifics about internal and external-facing firewalls, routing details, switch details, software details, etc. Once you have obtained all of that, you then need a vulnerability. For example, knowing their external-facing firewalls are Cisco ASA's does you no good without a vulnerability you can exploit. Since no one publishes that information, you would need an insider with sufficient access to obtain it. I guarantee you that the New York Stock Exchange and United Airlines do not let just anyone enter their datacenters.

I find it far more likely that a bad update from Microsoft (which happens extremely frequently) was intentionally or unintentionally applied, or that some other component was updated or failed.

Link to comment
Share on other sites

But it's so cool to see people flip open a laptop plug in and start tapping away to hack into a system without even knowing the first thing about it and break and within minutes. As seen on TV…

Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

No one is more predictable that Timah. Well, except maybe Raptor and Proud.

....and the entire sewing circle.....
Link to comment
Share on other sites

Just because they say it wasn't hacked from the outside doesn't really mean it wasn't .

Our government told us that Benghazi was because of a YouTube video. It wasn't.

not the govt....only the LIARS in the WH...
Link to comment
Share on other sites

Considering the timing (yesterday morning), and some of the patches I noticed on my WSUS server yesterday morning, my initial speculation would be that a few system admins discovered why WSUS auto-approval and group policy auto-install can be a dangerous combination.

Does sound like the most plausible answer, but it seems like these entities would know better and have a system in place to prevent this.
Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha

Don't we have rules against this.....a mod at that

Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha

Don't we have rules against this.....a mod at that

No. Next?
Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha

Don't we have rules against this.....a mod at that

No. Next?

What a complete and utter embarrassment to this board...

Link to comment
Share on other sites

Considering the timing (yesterday morning), and some of the patches I noticed on my WSUS server yesterday morning, my initial speculation would be that a few system admins discovered why WSUS auto-approval and group policy auto-install can be a dangerous combination.

Does sound like the most plausible answer, but it seems like these entities would know better and have a system in place to prevent this.

WSUS is a free product from Microsoft that allows you to basically operate your own Windows update server(s), and it is used by virtually every company that has nearly 100 workstations or more since it saves the bandwidth of every workstation and server having to download those updates independently. It also gives you lovely reports on status. Approval is how an update is made available for clients to install. Auto-approval is not enabled by default, but substantially reduces the workload of having to approve updates if you trust a certain category of them.

On the client side, group policy handles when workstations query the WSUS server for updates, and what is done with them. For example, the setting I use is auto download and notify users for install. Some people actually install when they have a chance, but most end up installing the updates when they shut down for the day. What this does prevent is any updates being installed on any servers until I specifically choose to install them. Another option (the dangerous one for servers especially) is auto download and schedule the install, where the install proceeds regardless at whatever time the admin sets.

A bad patch/update from Microsoft can be catastrophic if WSUS and group policy are set to auto-approve and scheduled install, and Microsoft releases plenty of them. More often than not, they do not cause a huge problem across most of Microsoft's huge user base, but they do frequently interfere with proprietary or custom software that many companies use.

Link to comment
Share on other sites

Considering the timing (yesterday morning), and some of the patches I noticed on my WSUS server yesterday morning, my initial speculation would be that a few system admins discovered why WSUS auto-approval and group policy auto-install can be a dangerous combination.

Does sound like the most plausible answer, but it seems like these entities would know better and have a system in place to prevent this.

WSUS is a free product from Microsoft that allows you to basically operate your own Windows update server(s), and it is used by virtually every company that has nearly 100 workstations or more since it saves the bandwidth of every workstation and server having to download those updates independently. It also gives you lovely reports on status. Approval is how an update is made available for clients to install. Auto-approval is not enabled by default, but substantially reduces the workload of having to approve updates if you trust a certain category of them.

On the client side, group policy handles when workstations query the WSUS server for updates, and what is done with them. For example, the setting I use is auto download and notify users for install. Some people actually install when they have a chance, but most end up installing the updates when they shut down for the day. What this does prevent is any updates being installed on any servers until I specifically choose to install them. Another option (the dangerous one for servers especially) is auto download and schedule the install, where the install proceeds regardless at whatever time the admin sets.

A bad patch/update from Microsoft can be catastrophic if WSUS and group policy are set to auto-approve and scheduled install, and Microsoft releases plenty of them. More often than not, they do not cause a huge problem across most of Microsoft's huge user base, but they do frequently interfere with proprietary or custom software that many companies use.

With the what they have at stake, it seems like they would have a system to test the updates. They should have the resources to visualize and automate these test. However, no system is perfect.
Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha

Don't we have rules against this.....a mod at that

No. Next?

Oh no rules with name calling? My mistake

Link to comment
Share on other sites

No worries. barry will be quick to surrender...

LOL!!!! :laugh:/> :roflol:/>

First response is Obama!

....First and last you uneducated moron. Not my fault your savior in the WH is the most pathetic president in history. Bwahahahaha

Don't we have rules against this.....a mod at that

No. Next?

What a complete and utter embarrassment to this board...

What's funny is I imagine every morning he gets up and look in the mirror and thinks he's the greatest lol

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...