Friday, December 12, 2014

Phishing Email - You sent a iTunes Gift Card to - Examined

Sample Phishing Email - You sent a iTunes Gift Card $200 to ...

If you receive this crafty email similar to below, then it beware it's probably a phishing email attempt that is recently going around. What to do?  Report them, goto bottom of page.




Subject: You sent a iTunes Gift Card $200 to (teamtazdojo@gmail.com) Your receipt No.123456789

 
PayPal logo
12 Dec 2014 02:01:11 BST
Transaction ID: 4V999066CK355555N
 
You sent a iTunes Gift Card to (teamtazdojo@gmail.com)
Thanks for using iTunes. To see all the transaction details, log in to your Apple account.

It may take a few moments for this transaction to appear in your account.


 
Note to seller
This is a $200 itunes card or gift voucher.
Shipping address EMAIL - No Confirmed
teamtazdojo@gmail.com
Dispatch details
The seller hasnt provided any dispatch details yet.
 
Description
Unit price
Qty
Amount
Click here To Cancel This Transaction
iTunes Gift Card Item Number 333332959511
$$200 CAD
1
$$200 CAD
 
Postage and packaging
$200 CAD
Insurance - not offered
----
Total
$200 CAD

How to tell this is a Phishing email ?


  1. Is email is from you to you, then it's phishing.
  2. Hover over all links in email, if it's not from the apple.com site then forget it.

    In above example, all the links and source images seem to be from Apple website except the iforgot.apple.com link.

    You can test this
    in the above example, since I crafted that from source HTML of the phishing email. Try it, hover over links to examine the source URL. Note: I have re-coded iforgot.apple.com to report delnott.com as phishing site to Google.

    In the original phishing email, hovering over iforgot.apple.com pointed to spam site delnott.com
    . The correct link when you hover over iforgot.apple.com should be http://iforgot.apple.com.
    Reading email in Outlook generated pop-up "Click to follow link"


  3. The best way is to look at message source, see below.


How to examine Email Message Source ?

Now lets look at message source
  1. Outlook.com->Actions->View Message Source. 
  2. Gmail.com->More (down arrow to top right)->Show original.

For this phony email, well look at the top 25 lines of the message, known formally as the "message header".





At line 23 you have Return-Path: hosting.windows@aruba.it
and is suspect because domain was registered in Italy (
.it) and nothing to do with Apple.

Aruba.it is being investigate for a Paypal phishing and has reported links to Italian Mafia.


These are valid return-paths for Apple 

  • Return-Path: do_not_reply@apple.com 
  • Return-Path: bounces@insideicloud.icloud.com 

Why look at "Return-Path"? When the e-mail is put in the recipient's mailbox, a new mail header is created with the name "Return-Path:" containing the address on the MAIL FROM command. So it's a quick hit to determine authenticity.


Report Phishing Email (not as Spam)

  1. Outlook.com->Junk (at Top)->Phishing Scam
  2. Gmail.com->More (downarrow to top right)->Report Phishing 


Report Phishing URLs delnott.com at Google now 

If you have recievied this email take further action now by click these links

  1. https://www.google.com/safebrowsing/report_phish/?hl=en&url=delnott.com

Report phishing at Microsoft and government agencies

  1. http://www.microsoft.com/security/online-privacy/phishing-faq.aspx

Monday, December 1, 2014

Paste image into Gmail not working?

Are you having an issue pasting (ctrl-v) an image into Gmail message, no matter how many time you try to paste an image and it's just allowing you to add an image, but you can paste text ?


You most likely have plain text turned for composing emails in Gmail, but this is not obvious since it's really not indicated anywhere and if you slip into this mode you be frustrated that it's not indicated.

You can display your current default authoring mode by selecting this down arrow that is located to the right side of the garbage can when you compose a New Message in Gmail.

Plain text mode enable - this does not allowed images to be pasted!

Solution: You have to turn on Rich Text emails, which means makes sure Plain text mode is NOT selected.

Disable Plain text mode
Now you will be able to paste images into Gmail emails.



Saturday, November 22, 2014

Cost of 1 code change and myth of multi-tasking

At Sprintly, we have a lot of data on developer cycle time. We track how long it takes them to complete different types of tasks (Stories, Tests, Bugs), as well as different sizes of tasks (S, M, L, XL).


The sample size was 147,494 items that had been both accepted & scored. 


Patterns we seen at Sprintly


1.  Developers are remarkably average. Our ticket data shows that across all of our users, cycle times are very similar: 
75% of all tickets in our system are started and completed in about 175 hours.
1 ticket to close on ~ 175 hours or 21 work days or 1 elapsed work month!
2. Most of the variability occurs before a ticket has been started (Someday to Backlog). This is the stage when stakeholders are figuring out specs and prioritizing work. In the Kanban world, this is typically called reaction time (the amount of time from when the ticket is created to when it is prioritized). There’s a lot of time wasted at this stage:
Developer cycle time variability by Sprint.ly
3. it also appears that teams have a hard time transitioning from “done” to “tested and ready to be deployed” (look at Completed to Accepted above).
Context switching introduces huge costs
For example, we have a Lead Developer who does a lot of code reviews, pairing, going to meetings, and fighting fires.
Here’s a graph that shows cycle times for developers on our team:
Lead developer who switches contexts
In this case, it’s the nature of the Lead Developer’s role that affects the amount of time it takes him to complete tasks.
The problem arises when you, as a manager, switch your developers to new tasks mid-stream. If your priorities are always shifting, you’re introducing huge costs to your team.
Thanks for this article, we need more metrics like this...
https://sprint.ly/blog/your-developers-arent-slow/