May 21

Five ways to avoid Windows 8

You don't have to get on Windows 8 s Metro ride.

You don’t have to get on Windows 8′s Metro ride.

Some people are still sure Windows 8 is going to be the cat’s meow. I’m sure Windows 8 and its Metro interface will be more like a cat’s yowl of pain. The more I look at Metro, the more I’m sure that Microsoft’s new desktop will flop as badly as the Facebook IPO.

It’s not just me. Business analysts, who could care less about technology but care a lot about what customers think, are saying things like “Windows 8 will prove to be a disappointment.

Windows users who were already unhappy about having to learn Metro, which doesn’t work or look a thing like Vista and Windows 7’s Aero interface never mind XP’s familiar appearance, are finding out there’s more trouble ahead for them. Windows 8 will cost more at launch to upgrade to from Windows 7. DVD playback and media-center functionality will now be an extra-price option.

Oh as for Metro-friendly applications, here’s what Matthew Baxter-Reynolds, an independent software development consultant, speaker, author, and trainer and all around Windows guru who’s writing the book “Programming Windows 8 Apps with C#” had to say: “does Metro actually work? In my opinion: No.”

I don’t care if your most prized possession is an autographed copy of Bill Gates’ The Road Ahead, you have got to be wary of moving to Windows 8. So what can you do to avoid, or at least delay, the day you have to start using it?

1. Stick with Windows XP

OK, so your PC is getting a little older, but it’s still working isn’t it? According to some estimates, most PC users are still using XP. Certainly hundreds of millions of users are still using it. If it’s not broke, why fix it?

Well, there is one reason: On April 8, 2014, Microsoft says it will officially end support for XP–and Office 2003 while they’re at it. Of course, Microsoft has extended XP’s life support before. Today, they swear they wouldn’t do it again. But, if say 20% of users still have XP running in their PCs in 2014… well let’s just say I won’t be surprised if Microsoft has a change of heart.

2. Stick with Windows 7 or move to it

So, let’s say its 2012’s holiday season and all the new PCs are coming out with Windows 8, what do you do? You don’t ask, you demand, Windows 7 instead.

Yes, I’m a Linux guy, but if you really want Windows, and I know most of you do, Windows 7 SP 1 is easily the best version of Windows to date. Yes, it’s not the same as XP. There is a learning curve. On the other hand, while it’s not as safe as Linux, Windows 7 is a lot more secure than XP. There are also plenty of useful, easy to-use tools to move your XP data and applications to Windows 7.

3. Move to a Linux or Mac Desktop

Since Microsoft wants to force a radical change on you, why not really make a change and move to Linux or a Mac? The Linux desktop is great for both power users and for users who just need a computer for the basics. Specifically, I think XP users will find Linux Mint with the Cinnamon interface to be inviting. And, Ubuntu 12.04’s Unity interface is much easier to use than Metro. Heck, my 80-year old mother-in-law is a successful Ubuntu user!

Macs, of course, are Macs. They’re pricy, you’re locked into Apple’s hardware and software in ways that Steve Ballmer can only dream about, and, and, gosh they’re pretty and easy to use. Well, easy to use so long as you do exactly what Apple thinks you should be doing anyway.

4. Move to the cloud with Google’s Chrome OS.

Chrome OS hasn’t really caught on yet, but I think Google’s Chrome OS is a real alternative to Windows for many users. It’s not so much Chrome OS itself, it’s the whole concept of being able to use a Web browser and the cloud for everything you need to do and that you want to do instead of a fat client desktop operating system.

Think about what you’re doing today. Web-browsing, e-mail, IM, VoIP, maybe using Google Docs, whatever, how much of that actually requires that you use a local application? If 99% of what you’re doing on your computer can be done on the Web, what more than you really need than the Chrome Web browser, or-and there’s the point–an operating system like Chrome OS, which is just the Chrome Web browser running on a barebones Linux structure?

5. Use an iPad or Android tablet instead.

Microsoft really wants people to switch to Windows 8, and its close cousin Windows RT smartphones and tablets. I’m not holding my breath. I actually think Windows 8/Metro on Intel actually makes sense–Windows RT, which doesn’t have Active Directory support, not so much. Metro looks and works better on a tablet than it ever will on a desktop. There’s just this one little problem: People love iPads and they’re getting fonder of the Android tablets with their lower price tags. If I were a Microsoft fan, I’d worry if there’s any room left in the market for a Windows 8 tablet.

At the same time, as Microsoft is painfully aware, tablets are becoming popular as desktop replacements. As ZDNet’s own James Kendrick points out, “It is now possible to get a full day’s work from almost anywhere, without compromise,” on a tablet.

So, come the day you go to a Best Buy and all you see is Windows 8 PCs from one end of the store to the other, just remember you do have other, better, options.

Related Stories:

No Windows 8 DVD playback will mean increased costs, and consumer confusion

Windows 8 will “disappoint”: Analysts cut price targets on HP, Dell

Windows 8 Pro upgrade for new PC buyers set at $14.99

Windows 8’s five biggest enemies

Five Reasons why Windows 8 will be dead on arrival

Article source: http://www.zdnet.com/blog/open-source/five-ways-to-avoid-windows-8/11007

May 21

Configuring password complexity in Windows and Active Directory

Both modern Windows systems (e.g., Windows Server 2008 and 2008 R2) and Active Directory, like Linux and Solaris systems, allow you to configure password policies that determine how long and complex your users’ passwords must be, providing a first line of defense for your systems. If your Unix systems authenticate to AD, then this is the place to specify your all of your password requirements. If Active Directory is only one of many places where password policies are configured, it’s still a good idea to ensure that good passwords are used. Having similar complexity standards across the enterprise is a good strategy as it reinforces the importance of good passwords in keeping your systems secure.

Windows and Active Directory allow you to specify a number of parameters to enforce password security. The default values are listed in the table below.

Policy Setting 					        Default Setting Value
==============		                                ====================
Enforce password history 				24 days
Maximum password age 					42 days
Minimum password age 					1 day
Minimum password length 				7
Password must meet complexity requirements 		Enabled
Store passwords using reversible encryption 		Disabled
Account lockout duration 				Not defined
Account lockout threshold 				0
Reset account lockout counter after 			Not defined
Enforce user logon restrictions 			Enabled
Maximum lifetime for service ticket 			600 minutes
Maximum lifetime for user ticket 			10 hours
Maximum lifetime for user ticket renewal 		7 days
Maximum tolerance for computer clock synchronization	5 minutes

Password history — how many passwords will be remembered by the system. Using the default, none of the previous 24 passwords can be reused when a user changes his or her password.

Maximum password age — how long a password can be used before it must be changed. If changed, this is typically set to something like 90 days. This would mean that your passwords must be changed every few months.

Minimum password age — how long your users must wait before they can change a password again. If you users could change their passwords immediately and the system only remembered a few of the previous passwords, it would be easy for them to resurrect their current passwords, essentially using the same password forever. If you force them to use each new password for some number of days, the likelihood that they will return to using the original password is slim. If the wait were two days and ten passwords would be remembered, it would take 20 days to get back to the original password. By that time, even the cleverest of passwords will probably have lost its appeal.

The drawback of minimum password age policies is that your users won’t be able to change their passwords right away even if they believe the passwords have been compromised. You should keep this in mind if you choose this option and make sure a hotline is available for emergency password changes.

Password complexity requirements — incorporates a number of requirements that are configured separately on Linux and Solaris systems. If this setting is enabled — as it is by default, passwords must be at least six characters long and must contain characters from three of the following: uppercase characters, lowercase characters, digits (0-9), special characters (e.g.,!, #, $), and unicode characters. In addition, the password must not contain more than two characters from the username (provided the username is three or more characters long).

Minimum password length — how many characters must be included in users’ passwords. While this defaults to 7, something between 8 and 12 is a better choice. Your users are likely to balk at having to remember an additional four characters, so be ready to offer some suggestions on how to make longer passwords memorable, such as adding a couple digits to each end, prepending passwords with their best friend’s birthday (e.g., 0323) or setting passwords to be a short phrase like “want2goHome!”. Remind them that writing down their passwords is always a very bad idea, but writing down something that reminds them of their passwords might be OK, especially if they don’t make it obvious that it’s a password that they’re trying to remember.

Account lockout duration — how many minutes a locked-out accounts remains locked out before becoming unlocked. If set to 0, however, a password remains locked until an admin (someone authorized to make these kind of changes) unlocks it. This setting is dependent, however, on the account lockout threshold. In other words, if you don’t specify that accounts will be locked after some number of failed attempts to log in, there’s no significance to specifying how long they’ll be locked.

Account lockout threshold — the number of consecutive failed login attempts that will cause an account to be locked. If set to 0 (the default), accounts are never locked.
The only drawback of the account lockout threshold setting is that it makes it possible for a user to lock out some other user’s account.

Reset account lockout counter after — how many minutes must elapse before a lockout counter is reset to 0 (i.e., the account is unlocked). This can range from 1 minute to 99,999. It must be less than or equal to the account lockout duration.

Enforce user logon restrictions — whether the Kerberos Key Distribution Center validates every request for a session ticket against the user rights policy on a particular computer.

Maximum lifetime for service ticket — maximum time that a session ticket can be used. This means that the authentication system underlying Windows (Kerberos) must revalidate a connection at the specified interval.

Maximum lifetime for user ticket — maximum time that a user’s ticket granting ticket may be used. After that time (default 10 hours) has passed, it must be renewed.
Maximum lifetime for user ticket renewal — defines the time period within which a ticket can be used for and renewed.

Maximum tolerance for computer clock synchronization — defines the maximum time difference that is allowed between the time on the client’s clock and the domain controller. It is meant to prevent what are called “replay attacks” in which a valid data transmission is maliciously or fraudulently repeated or delayed.

The default settings for passwords on Windows and Active Directory are quite reasonable, though I would change the 7-character minimum password length to something higher. While the lockout features make the success of brute force password attacks highly unlikely — if this is set and it is not by default, setting users’ expectations that password should be longer than 8 characters is likely to improve the security of other accounts they use.

Article source: http://www.itworld.com/security/277846/configuring-password-complexity-windows-and-active-directory

May 20

Linuxnews.me reorganising – Less Android news

The amount of Android news has been way more than the amount of linux news. Therefore we will no longer post news about Android, unless it has something to do with the OS or Linux. We hope you like the new and  better Linux news-updates.

– Tommy Eide, Director of Awsomenews Enterprises, CEO Linuxnews.me

May 20

Samsung S Voice Siri clone gets leaked for Android 4.0

It’s no secret that when it comes to smartphones, Samsung sees only one company as its competitor – Apple. It believes, rightly so, that it has the most popular presence on Android so rather than fight against other Android manufacturers it has its eyes set solely on the iPhone. So it is really no surprise that the company has developed its own version of Siri. Will it be able to measure up?

Called S Voice, it is supposed to be one of the crown jewels of the newly announced Galaxy S III, an Android phone that arguably received more hype than any before it. However, the S Voice software has managed to leak out into the wild, and it will apparently work on any phone running the latest version of Android, version 4.0 also known as Ice Cream Sandwich.

S Voice truly is a Siri clone. It encourages users to speak to the phone in normal human speech as opposed to only being able to use a few stale, specific voice commands. There will no doubt be a whole bunch of analysis comparing the two services as S Voice gets more ingrainted into the market, which is exactly what Samsung wants. It wants you to compare its phones to the iPhone, not to other Android phones.

[via Redmond Pie]

Article source: http://www.slashgear.com/samsung-s-voice-siri-clone-gets-leaked-for-android-4-0-20229040/

May 20

Microsoft Wins Patent Suit Against Motorola Android Handsets

Technology giant Microsoft claimed victory this weekend as the International Trade Commission (ITC) issued its final determination in Microsoft’s Android infringement case against Motorola, ruling Motorola violated a Microsoft patent related to ActiveSync, a mobile data synchronization technology and protocol developed by Microsoft, originally released in 1996. The technology is licensed to a number of mobile device companies, including Apple for iOS.

The ruling affects eight individual Motrola Mobility handsets which run Google’s Android operating system, including the popular Droid 2 and Droid X smartphones, as well as the Backflip, Charm, Clip, Devour, i1 and Cliq XT. “Microsoft started its ITC investigation asserting 9 patents against Motorola Mobility,” Motorola spokeswoman  Jennifer Erickso said in an emailed statement. “Although we are disappointed by the Commission’s ruling that certain Motorola Mobility products violated one patent, we look forward to reading the full opinion to understand its reasoning.”

A Bloomberg article reported that Motorola Mobility could appeal the ruling or cut a licensing deal with Microsoft in order to avoid altering the software on its phones. The company is currently being acquired by Google for $12.5 billion, a move that would give Google a hardware arm, as well as inheriting a broad array of wireless technology patents that could provide useful cover against its rivals’ legal assault on Android. “These cases usually end up with the parties settling,” Charlie Wolf, an analyst with Needham Co in New York, told the news service. “I would expect Motorola to get together with Microsoft to resolve this.”

According to the ITC filing, the Commission instituted the investigation on November 5,2010, based on a complaint filed by Microsoft titled In the Matter of Certain Mobile Devices, Associated Software and Components Thereof, 337-744. The final ruling was delivered to President Obama as well as the U.S. Trade Representative, where Obama has the decision to either support or override the decision, based on public policy grounds.

“Microsoft sued Motorola in the ITC only after Motorola chose to refuse Microsoft’s efforts to renew a patent license for well over a year. We’re pleased the full Commission agreed that Motorola has infringed Microsoft’s intellectual property, and we hope that now Motorola will be willing to join the vast majority of Android device makers selling phones in the US by taking a license to our patents,” David Howard, corporate vice president and deputy general counsel for Microsoft, said in an emailed statement.



Article source: http://www.eweek.com/c/a/Mobile-and-Wireless/Microsoft-Wins-Patent-Suit-Against-Motorola-Android-Handsets-808814/

Older posts «