eBay confirms security breach, password change recommended: Alert Priority High

eBay has confirmed that an attack on its systems earlier this year compromised a database containing encrypted passwords, customer names, email addresses, physical addresses, phone numbers and date of birth information.

It has stated that the database did not contain any financial information and that it has undertaken testing, finding no evidence of unauthorised activity for eBay users. It added that data stored with PayPal (owned by eBay) such as your credit card information, is encrypted and stored separately on a secure network.

eBay has advised it will begin contacting users to change their passwords.

Regardless of whether you receive notification from eBay, if you use eBay, you should change your password immediately.

If you use the same password to log in on any other website, you should change those as well, choosing something unique and strong.

SBS 2011 Devices or Users cannot relay even after setting anonymous to the connector in Exchange Management

After spending hours trying to rectify our send connector to allow our accounting program to send invoices out, we stumble across an article from Mark Berry at https://www.mcbsys.com.

We had run the Fix My Network Wizard in SBS 2011 and after that Exchange 2010 would not accept email from non authenticated users even if the anonymous was selected.

Can’t Anonymously Send External Email

Once I had made those changes, the accounting system wouldn’t send email external, only internally to our domain/network.

When the application tried to send an email to a recipient outside the network, it failed with a 5.7.1 error:

sterling-it-mail-relay

 

 

 

 

The Persits knowledge base has a helpful article identifying the problem:  it means that “the SMTP server you are using is configured to reject messages sent to outside email addresses and originating from unauthorized IP addresses or users.”

So it’s a separate setting to be able to send mail outside the organization?

Yup, and for some reason it can only be enabled from the Exchange Management Shell, not from the Console. Once I found and executed the command at the bottom of this Petri article, sending mail to external recipients worked as well:

Get-ReceiveConnector "Default SBS" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

Never in a million years would I have figured that one out. Thanks Mr. Petri! (no, thank you Mark Berry for reposting in a clean easy format)

NOTE:  If you need to re-run the Internet connection wizard, it will overwrite most of the above settings, and my mail wasn’t going out. So either don’t run that wizard, or make a note of your Exchange Hub Transport settings first.

SBS 2011 Can’t connect to the remote computer because no certificate was configured – Remote workplace certificate error

Problem:
When connecting to Windows SBS 2011 Remote Web Access, the following error appears when trying to connect to a remote computer.

RWA-Cant-Connect

 

 

 

 

 

 

Your computer can’t connect to the remote computer because no certificate was configured to use at the
Remote Desktop Gateway server. Contact your network administrator for assistance.

Solution:
You need to repair the Remote Desktop Gateway (RD Gateway) service in the the RD Gateway Manager management console.

By default, SBS 2011 does not have the RD Gateway Manager management console enabled, The following command will properly install the RD Gateway Manager management console:

dism /online /Enable-Feature:Gateway-UI

Run this command from an elevated command prompt.

Then follow these steps

  1. Open the Remote Desktop Gateway Manager from Administrative Tools > Remote Desktop Services.
  2. Right-click your server name and choose properties.
  3. Select the SSL Certificate tab.
  4. Click the Import Certificate… button.
  5. Choose your trusted certificate and click Import.
  6. Click Ok.

RDCM-SSL-Certificate

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

note: you may need to assign a different certificate, then reassign the desired certificate to force RD Gateway Manager to take effect

See Also:
How to Install Your Existing Certificate into SBS Essentials

 

SOURCE: Thanks to stevehardie.com – This is used for reference and internal use.

Open SSL web security issues named Heartbleed – Check and confirm website is safe here

Link to verify if website is secure and safe from heartbleed : https://filippo.io/Heartbleed/

Millions of websites, online stores and social networks are operating with a major security hole in place, exposing user information and financial information to hackers.

That is because a core safety mechanism used to secure the internet has a flaw in it. Worse still, it has been in place for over two years and experts are unsure if it has been exploited for criminal or espionage purposes.

Late on Tuesday, the bombshell hit the web: a Google security engineer and some other researchers published information indicating they had discovered a serious flaw, dubbed “Heartbleed“, in numerous but not all versions of the OpenSSL cryptographic software library, which is used to secure millions of websites.

Tech news website The Verge labelled it “the most dangerous security flaw on the web”.

Advertisement

“It is catastrophically bad,” ICSI security researcher Nicholas Weaver told the website.

Anonymisation software service Tor put it more bluntly: “If you need strong anonymity or privacy on the internet, you might want to stay away from the internet entirely for the next few days …”

“This might be a good day to call in sick and take some time to change your passwords everywhere – especially your high-security services like email, file storage, and banking, which may have been compromised by this bug,” Yahoo’s Tumblr said.

“This … means that the little lock icon (HTTPS) we all trusted to keep our passwords, personal emails, and credit cards safe, was actually making all that private information accessible to anyone who knew about the exploit.”

Melissa Elliott, a security researcher, noticed the flaw affecting a number of Yahoo websites – including the Yahoo.com search engine, email service mail.yahoo.com, and photography site Flickr.com – and suggested that users of those sites should stay away from them until they were patched.

Others echoed her concerns, saying that the only way internet users could be sure they were safe was to stop using vulnerable websites while they were unpatched, and to change their passwords after that. (A helpful tool at filippo.io/Heartbleed shows if a site is vulnerable.)

The flaw allowed anyone to grab credentials from a web server in plain text. In Yahoo’s case, this was possible for most of Tuesday until it patched its sites on Wednesday.

Australian IT security expert Chris Gatford, of HackLabs, wrote in a blog post that about 10 per cent of the Australian Stock Exchange’s top 200 companies used vulnerable versions of OpenSSL as of Tuesday night. Although some might dismiss the flaw, he was concerned by it.

A separate search of Alexa’s top 10,000 websites on the internet performed by former Lulzsec hacker Mustafa Al-Bassam found about 629 of them vulnerable to the flaw.

“… We have been able to dump from the affected servers plain text usernames and passwords, session cookies of banking customers and other information that would at the least allow compromise of user accounts etc from the affected web applications running on the tested servers,” Mr Gatford said.

While usernames and passwords were exposed, if an attacker had access to a user’s session cookie, they could log-in as the user without their password, as the cookie acts as their log-in.

A search by Fairfax Media using publicly available vulnerability testing websites uncovered retailer JB Hi-Fi’s website jbhifionline.com.au was vulnerable to the flaw on Tuesday, as well as cert.gov.au, the Australian government’s Community Emergency Response Team (CERT) website.

CERT refused to comment on whether it patched its site and would not say what advice it was offering to government departments.

“There is a range of open source information available about the Heartbleed vulnerability and the actions to take to address it,” it said.

Priceline’s priceline.com.au and the Commonwealth Courts portal comcourts.gov.au were also vulnerable.

JB Hi-Fi chief executive Terry Smart said JB Hi-Fi’s website used Amazon Web Services, which was vulnerable to the flaw until late on Tuesday.

“We’re updating all of our [SSL] certificates to protect against this potential issue,” Mr Smart said.

“No attacks have been identified by both our internal and external scans and we’re confident that no data breaches have occurred.”

Priceline confirmed it was affected too and had moved “immediately to apply a security patch”. “We have run security checks that indicate there were no breaches before we fixed the flaw. We are also purchasing a new certificate.”

Comment is being sought from the Federal Court by Fairfax Media as to what it will be doing to address the issue.

The flaw

OpenSSL is one way to implement the cryptographic protocol Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL), on web servers. Most consumers know when these protocols are implemented when they see “https” and a padlock in their browser.

The padlock is the indication web users look for to be assured a website is safe and transmitting their data in a secure manner. It essentially means that the connection between the user and the server is encrypted and can’t be snooped on. The idea behind using this is so that anyone attempting to perform a “man in the middle” attack can’t see the data transmitted. This means that even if a rogue network administrator at an internet service provider was in the “middle” of your connection and tried to intercept it they would be unsuccessful and get encrypted data they couldn’t decrypt.

But thanks to the flaw the IT security researchers found, in many instances the way the encryption has been implemented on the server side across large swathes of the internet has been flawed. It’s meant that an attacker with knowledge of it would have been able to get servers to spit out data previously thought to be secure by injecting the server with exploit code.

That leaky data was coming out in chunks from a server’s memory, and a number of proof of concepts built overnight show that lots of private user data can be extracted from a server over time.

Attackers could do this all remotely, the researchers who found the flaw said. Further, it’s thought that a server’s “crown jewels” – the private keys it uses to encrypt data between it and users – could have also been stolen using the flaw, as it allowed for not only client data to be stolen but server data.

It may sound boring, but many IT security experts have told Fairfax Media that it’s really important for internet users to understand the flaw and the risks.

“You are likely to be affected either directly or indirectly,” the researchers who found the flaw said of the bug. “OpenSSL is the most popular open source cryptographic library and Transport Layer Security implementation [is] used to encrypt traffic on the internet.

“Your popular social site, your company’s site, commerce site, hobby site, site you install software from or even sites run by your government might be using vulnerable OpenSSL.”

With the private keys potentially having been stolen, it means affected companies now face making a decision of whether they need to renew and regenerate their private keys – at a cost. This can vary from a couple of dollars to thousands depending on the type of key purchased.

As of Wednesday morning, hacking search engine tool Shodan was showing there were at least 576,231 devices worldwide with vulnerable versions of OpenSSL running on them. Of those, 6270 were based in Australia. The numbers are by no means comprehensive – as Shodan doesn’t index the entire internet – and they may include some servers that aren’t affected.

Security experts are encouraging users to wait until the sites they use patch their OpenSSL and issue new certificates before recommending they change their passwords.

Downgrading Outlook and backwards compatibility

There can be various reasons which will require you to downgrade to a previous version of Outlook such as the current trial/beta version expiring or compatibility issues with some needed add-ins or business software. This guide provides solutions to various problems you may encounter when trying to downgrade Outlook or when you need to remain compatible with previous versions of Outlook.

We found a really good article explaining this at https://www.howto-outlook.com

For full details, click here

Regards

Mark

www.sterlingit.com.au

Microsoft Remote Desktop on Apple mac OSX and Windows 2012 – How to fix & get updated software

Watch out – the old OS X Microsoft Remote Desktop (version 2.1.1) that comes with Mac Microsoft Office 2011 no longer works with Windows 2012 R2 (it does work with plain old Windows 2012). For me it fails with the following error message:

Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.

A (regular) Windows 2012 Remote Desktop client doesn’t have this problem.

(Brief aside – Microsoft have a little note that says the 2.1.1 client is not supported on OS X v10.7 or later. Who knew and why did it make me report all those crashes?)

The good news is that the new OS X Microsoft Remote Desktop 8.0.24091 (Mac App store only though – grr) does work with Windows 2012 R2 . Why this information isn’t listed on the What’s New in 2012 R2 Remote Services page I don’t know…

Another alternative is a product called CoRD – Home Page of CoRD