Users of Wi-Fi hotspots have been warned about the “Poodle” attack – the latest bug in Internet browsers that can hijack web sessions and transactions, and even extract data from secure HTTP connections, The Straits Times reported today.

Poodle, or Padding Oracle on Downgraded Legacy Encryption, exploits Secure Sockets Layer version 3 (SSLv3), one of the protocols used to secure Internet traffic, the Singapore daily said.

All major browsers, from Google Chrome to Mozilla Firefox, support SSLv3.

An attacker can access online banking or email systems “secured” by HTTP connections. The flaw was reported by Google employees – Bodo Möller, Thai Duong and Krzysztof Kotowicz – in a paper published on Thursday.

The Poodle attack relies on the fact that most web servers and browsers are still using an “ancient” SSLv3 to secure their communications.

Source: The Malaysian Insider

Scenario:

In an Exchange Hybrid environment (using Office 365).

Problem:

In Exchange Management Console (EMC), under Move Request, there is some mailbox being moved. This action was not done by the local IT administrators. The mailbox affected are mailboxes already migrated to Office 365.

Solution/Explanation:

Run a Get-MoveRequest and if you see something like below, you are actually seeing the database being moved from Exchange Online DB to another Exchange Online DB. This is part of Exchange Online DB maintenance. There is no impact to users.

ExchangeGuid               : 404b747c-d942-4ecc-ba61-9459c234a8d3

SourceDatabase             : APCPR04DG020-db001

TargetDatabase             : APCPR04DG011-db170

SourceArchiveDatabase      :

TargetArchiveDatabase      :

Flags                      : IntraOrg, Pull, MoveOnlyPrimaryMailbox

Problem: Customer has a few email domain names and are slowly migrating to Office 365. The customer wants to auto assign license for certain domains using PowerShell.

Step 1:

Set the Office 365 tenant password in a TXT file.

The PowerShell Script:

#Modify below YOURPASSWORD to your Office 365 password
$password = “YOURPASSWORD”
$password | ConvertFrom-SecureString | Set-Content c:\o365\password.txt

Step 2:

Search based on the valid domains and add license for users that have not been licensed.

The powershell script:

#Valid Domains.
#Modify below domainA.com and domainB.com to your own domain that you want to auto assign license.
$validDomains =”*@domainA.com”,”*@domainB.com”

$MsolAdmUser = “admin@USERTENANTNAME.onmicrosoft.com”
$pwd = Get-Content c:\o365\credmsol.txt | ConvertTo-SecureString
$cred = New-Object System.Management.Automation.PSCredential $MsolAdmUser, $pwd

# CONNECT TO 365
Import-Module MSOnline
Connect-MsolService -Credential $cred

$temp = (get-msoluser -all) | select userprincipalname

foreach ($a in $validDomains){

foreach ($b in $temp){

$validUser = ($b) | where {$b.userprincipalname -like $a}

If ($validUser –eq $null){

} else{

set-msoluser -userprincipalname $validUser.userprincipalname -usagelocation “MY”

set-msoluserlicense -userprincipalname $validUser.userprincipalname -addlicenses “userTenantName:STANDARDWOFFPACK“

$validUser = $null

}

}

}

To get the “userTenantName:STANDARDWOFFPACK“, you will need to run get-msolaccountsku.

The above is a script that I quickly developed. Apologies if it isn’t neat as of now