- News uses less than what 1/3 of the horizontal space not including the polls, everything is crammed in a narrow strip down the middle of the screen. - bright blank white space on each side is great than the content section as a whole at 1920X1080 - contrast of new design makes reading harder some how. - Comments are awful; due to the compressed layout and the fact they aren't boxed in as well as the old system - loaded it on my iPhone, and waited... and waited... slow and the banner ad that loaded made the layout break. big step backward from the current mobile option
Bottom line I am hard pressed to find anything positive here...
PPTP is a type of VPN still used by some companies and included with windows... MS-CHAPv2 is the default / most common authentication option when using PPTP with windows. Thus organizations still using PPTP for remote access may be at risk.
This is true, we just finished doing evaluations and IBMs quote included subbing out ALL the work to multiple sub vendors, the only part with IBMs name on it was the Quote.
Hacking in a custom firmware like OpenWRT, Tomato or DD-WRT isn't the point when it comes to mass penetration of IPv6, devices need to officially ship with it for it to spread.
I can forgive Juniper when compared to Cisco on the topic of licensing and complexity.
Despite advancements for support at the device level the next major hurdle for large enterprise is the management tools and monitoring tools not fully supporting IPv6.
It is really hard to manage a modern network without flow monitoring, snmp and syslog data from all systems. This is another area where you end up with a setback or compromise if you try and roll out right now.
On the consumer front only just recently did home WiFi routers start shipping or start getting IPv6 support, even then finding an ISP that will provision you is next to impossible.
On the enterprise front gear has been labeled as IPv6 ready or compatible or even listed it as a feature for a long time. However if you work in security and have to implement policy control over content, you quickly see that the functionality is years behind when applied to IPv6 flows... At an enterprise level switching isn't easy without swamping out a lot of gear, or reducing expectations... IPv6 enabled deep inspection, and application layer inspection tools are only now becoming available, or only now becoming mature enough to roll out.
That is external application brute force, in this case the attacker simply broke in and copied the list of hashes given them unlimited time to try and match them to known passwords.
Developers are not end users... they are some level of engineer, as they are BUILDING things for end users to use... They should be reading some kind of docs before choosing tool / function they use for the job... the more powerful the language the more you need to know.
In your example the developers should be the ones that build the BAD CAR with the exploit in it that was sold, they where not the poor end users that purchased it.
Your example is still a failure of the developer understanding the tool which caused the problem, not the tool missing an alternate secure way to do it.
Most web app exploits ARE the developers fault! - They don't check their inputs (length) buffer over flow - They parse or merge database commands (SQL injection) - They don't limit abuse (brute force retry attacks)
Yes some of these can be mitigated at other levels, but ALL are common APPLICATION DEVELOPER ISSUES! by measure of deployment to number of exploits I would say the programing languages and OS already do a MUCH better job than the application developers...
Also if you check the news for the ONLY platform with centralization to the point of causing National/ North America wide device outages, and being forced to hand over some control to other governments by building in centralization in a specific way, you have RIM..
On the plus side we haven't had a nation wide outage on RIM in over a year, must be all the surplus capacity. We started to see a surge in iOS device uptake during the last one.
Playbooks and BB OS X devices will REQUIRE mobile fusion on top of BES. Mobile fusion is barely out of beta. If you manage blackberries and don't know this you might also want to go check out the License cost for this upgrade, you might be shocked.
I agree, looking around Good, would be the closest off the shelf solution, it would also work with iOS devices giving you access to BOTH the most popular platforms right now..
Because starting from scratch on RIMs BB right now could be suicide...
- New OS devices coming in the fall with a new untested management platform - Over stock of current gen devices they can't sell ( way under powered compared to WP, Android, iOS) - Bleeding management - Laying off huge amounts of staff.
On long mountain roads far to often I see someone try to aggressively pass long sets of cars only to have to abort half way, causing other drivers to let them in quickly to avoid an accident..
Slashdot Mirror
- News uses less than what 1/3 of the horizontal space not including the polls, everything is crammed in a narrow strip down the middle of the screen.
- bright blank white space on each side is great than the content section as a whole at 1920X1080
- contrast of new design makes reading harder some how.
- Comments are awful; due to the compressed layout and the fact they aren't boxed in as well as the old system
- loaded it on my iPhone, and waited... and waited... slow and the banner ad that loaded made the layout break. big step backward from the current mobile option
Bottom line I am hard pressed to find anything positive here...
I don't know, when the Wii U controller was announced stuff like this http://www.macstories.net/news/ipad-games-on-apple-tv-firemint-announces-real-racing-2-hd-with-ios-5-airplay-mirroring/ had already landed.
If you already own a tablet that can stream to your TV why purchase a dedicated console with a limited tablet LIKE controller?
http://www.high-rely.com/
We ran some of these for off siting data in rotation... Way faster than tape and designed for swapping... Might not be the best for long term storage.
PPTP is a type of VPN still used by some companies and included with windows...
MS-CHAPv2 is the default / most common authentication option when using PPTP with windows. Thus organizations still using PPTP for remote access may be at risk.
This is true, we just finished doing evaluations and IBMs quote included subbing out ALL the work to multiple sub vendors, the only part with IBMs name on it was the Quote.
http://owncloud.org/
- Calendar
- Contacts
- dropbox like storage
Dd-wrt and tomato-USB firmware builds run on several buffalo and asus brand routers.
Buffalo even ships dd-wrt on select units.
I hate the GIANT font that doesn't fit on the screen used for titles on screens like the people app.
Hacking in a custom firmware like OpenWRT, Tomato or DD-WRT isn't the point when it comes to mass penetration of IPv6, devices need to officially ship with it for it to spread.
Out of the box you get access to a lot more (ipv4 features) than with Cisco without extra licensing, however you are right that the split is odd.
I can forgive Juniper when compared to Cisco on the topic of licensing and complexity.
Despite advancements for support at the device level the next major hurdle for large enterprise is the management tools and monitoring tools not fully supporting IPv6.
It is really hard to manage a modern network without flow monitoring, snmp and syslog data from all systems. This is another area where you end up with a setback or compromise if you try and roll out right now.
On the consumer front only just recently did home WiFi routers start shipping or start getting IPv6 support, even then finding an ISP that will provision you is next to impossible.
On the enterprise front gear has been labeled as IPv6 ready or compatible or even listed it as a feature for a long time. However if you work in security and have to implement policy control over content, you quickly see that the functionality is years behind when applied to IPv6 flows... At an enterprise level switching isn't easy without swamping out a lot of gear, or reducing expectations... IPv6 enabled deep inspection, and application layer inspection tools are only now becoming available, or only now becoming mature enough to roll out.
That is external application brute force, in this case the attacker simply broke in and copied the list of hashes given them unlimited time to try and match them to known passwords.
Not sure about Android 4.0 but iPhone has supported more ActiveSync policy management than Android for some time. Specifically around app-store access.
http://www.netqin.com/en/security/newsinfo_4388_3.html
However all bets are off once ether is rooted / jailbroken.
Developers are not end users... they are some level of engineer, as they are BUILDING things for end users to use... They should be reading some kind of docs before choosing tool / function they use for the job... the more powerful the language the more you need to know.
In your example the developers should be the ones that build the BAD CAR with the exploit in it that was sold, they where not the poor end users that purchased it.
Your example is still a failure of the developer understanding the tool which caused the problem, not the tool missing an alternate secure way to do it.
Most web app exploits ARE the developers fault!
- They don't check their inputs (length) buffer over flow
- They parse or merge database commands (SQL injection)
- They don't limit abuse (brute force retry attacks)
Yes some of these can be mitigated at other levels, but ALL are common APPLICATION DEVELOPER ISSUES! by measure of deployment to number of exploits I would say the programing languages and OS already do a MUCH better job than the application developers...
Fair enough, BB OS 10 adopts active-sync removing much of the dependance.
What about Siri? Or MobileMe/iCloud? Even Gmail has unexpected outages. Those are consumer features or services.
For Enterprise Email, calendaring and directory a current gen BB device simply has more points of failure to hop through before you get the message.
ActiveSync is Exchange->Internet->Device
BES BB7 and below is Exchange->BES->RIM->Internet->Device two additional points of failure.
Also if you check the news for the ONLY platform with centralization to the point of causing National/ North America wide device outages, and being forced to hand over some control to other governments by building in centralization in a specific way, you have RIM..
On the plus side we haven't had a nation wide outage on RIM in over a year, must be all the surplus capacity. We started to see a surge in iOS device uptake during the last one.
Playbooks and BB OS X devices will REQUIRE mobile fusion on top of BES. Mobile fusion is barely out of beta. If you manage blackberries and don't know this you might also want to go check out the License cost for this upgrade, you might be shocked.
I agree, looking around Good, would be the closest off the shelf solution, it would also work with iOS devices giving you access to BOTH the most popular platforms right now..
Because starting from scratch on RIMs BB right now could be suicide...
- New OS devices coming in the fall with a new untested management platform
- Over stock of current gen devices they can't sell ( way under powered compared to WP, Android, iOS)
- Bleeding management
- Laying off huge amounts of staff.
Super heating a capsule, then dumping it into salt water for hours isn't cut and dry... There are MANY things that could go wrong..
Also if the stuff they sent back is smashed to bits from a hard landing, then well they have lots of work to do before sending humans.
Touched down intact, but I wouldn't declare it safe till they recover it and open it... Re-entry is a bitch...
On long mountain roads far to often I see someone try to aggressively pass long sets of cars only to have to abort half way, causing other drivers to let them in quickly to avoid an accident..
I wonder if this road train would let them in.