Sekiur My Thoughts

Working on multiple iPhone application projects and shortly looking at the iPad for other development opportunities, I found an excellent step by step guide on creating a development provisioning profile on http://devclinic.com by Kuix, that I thought I should share.

As simple as it may, I thought i’d contribute and write a tutorial on how to get your development application onto your testing device. Due to the exponential speed and memory differences between your development computer and an actual mobile device, it is very important for you to test your application on a mobile device.

Step 1: Certify
This is the hardest step, so please follow the steps closely.
Open Keychain Access application, inside your Application->Utilities folder. Click on Keychain Access->Certificate Assistant->Request a certificate from a certificate Authority… Enter your email, your name, and for CA Email i used my email again(the last one don’t really matter, for these purposes, but it’s required). Choose Saved to disk and click continue. It will then, by default save to your desktop.

Open up Apple Developer Connection inside your browser and login. Go to the Program Portal section and click on Certificates. Choose add certificate. The page will basically tell you to do what i just told u. scroll all the way to the bottom, where you will upload and submit that new certificate, from your desktop. Now your certificate needs to be approved by you/administrator. Simply click on approve, where your certificate is pending. Now, you will have the option of downloading your approved certificate. Download that, and the WWDR intermediate certificate, linked below your certificate. double click on both downloaded certificates to install them into your Keychain. Use login, instead of System, for both.

Once that is done, move on.

Step 2: Device
Now click on Devices. Here you will get your mobile device recognized as a development device. You can develop your app on either an iPhone or an iPod Touch. Open xCode, and go to Window->Organizer Here you will see the device that is currently connected to your computer. notice the long ass identifier key for Identifier:. now inside your program portal, click on Add Devices. you will make up a device name and then copy past that identifier value, you stole from the xCode organizer. Submit.

Step 3: App IDs
Next step: click on the link App IDs from the left hand side, then New App Id. The Description is for your sake, so you know what the ID is for. Choose Generate New, and for Bundle Identifier, it’s like writing an URL backwards.
com.yourCompanyName.AppName then submit that.

Step 4: Provisioning Profile
Almost done! Go to Provisioning page, then New Profile.Choose a memorable profile name. check the box for your approved certificate. Choose your App ID, created from step 3. check the box for your development device. Submit. Now you can download your provisioning profile. Go back to your xCode organizer and add your provisioning profile into the Provision section, under Devices.

Step 5: Load it!
In your app, go to Resources->appName-info.plist Where it says Bundle identifier, change the value to what you entered for your app ID:com.yourCompanyName.AppName.

On the top left hand corner, in the drop down menu, choose Device – 3.0 (if you’re running 3.0 firmware). Build and Go.
If you’ve done everythign correctly, it will build successfully, and your app will be now on your mobile device!

I know it’s a lot of writing, but every step is pertinent. Good luck, guys=)

~Kuix

Its been a long time since my last post. Suffice to say that I have been extremely busy after reaching an inflection point in my life and am working on very exciting and promising projects.

MUST SEE. SIMPLY AWESOME.

Related articles by Zemanta

• Apple unveils new iPhone without Steve Jobs (mycompuquest.blogspot.com)

Tim Ferriss and Kevin Rose discuss their top 5 Must Read Books.

Random w/ Tim and Kevin – Ep3 from Glenn McElhose on Vimeo.

I endorse the following:

• The 22 Immutable Laws of Marketing
  
• Getting Real
• The Tipping Point: How Little Things Can Make a Big Difference

Other books on my reading list this year.

• The Knack
• The Integrity Dividend: Leading by the Power of Your Word
• The Trophy Kids Grow Up: How the Millennial Generation is Shaking Up the Workplace
• Mastering the Hype Cycle: How to Choose the Right Innovation at the Right Time (Gartner)
• Talent Is Overrated: What Really Separates World-Class Performers from Everybody Else
• Inside Drucker’s Brain
• Tribes: We Need You to Lead Us
• High Altitude Leadership: What the World’s Most Forbidding Peaks Teach Us About Success
• Plugged In: The Generation Y Guide to Thriving at Work
• Content Nation: Surviving and Thriving as Social Media Changes Our Work, Our Lives, and Our Future
• Smart Networking: Attract a Following In Person and Online
• Making Technology Investments Profitable: ROI Road Map to Better Business Cases
• Strategic Alliances: Three Ways to Make Them Work (Memo to the Ceo)
• Reward Systems: Does Yours Measure Up? (Memo to the CEO)
• Wargaming for Leaders : Strategic Decision Making from the Battlefield to the Boardroom

Seven ways to achieve customer service.

Do you know any others?

1. Focus on the wants of the customer
2. Make your effort about fulfilling their need, not having them do what you want
3. Listen don’t hear
4. Determine what action(s) you need to perform to fulfill the customer’s expectations
5. Go above and beyond what is necessary to get the job done
6. Follow-up to ensure the customer is satisfied with the result you have achieved
7. Determine if there is there anything else you can do to make the customer happier?

So funny. MUST SEE.

As professionals in security we are constantly researching new technologies to keep our skills sharp. The Internet Storm Center was formed to assist with keeping our peers aware of the fast paced changes in vulnerabilities, patches, hacks, worms, Trojans and threats in general.

How we communicate these risks to our key decision makers sometimes can be a challenge. A recent example would be the Conficker April 1st situation. It was important for us to convey the sense of urgency we felt to have MS08-067 patched, as well as cross checking all our systems for updates being rejected, anti-virus definitions up-to-date and so on. My question to you is “did you communicate the risk effectively”? Were you able to give a complete and accurate risk assessment to your management?

Remember that risk assessment is the process of identifying a threat, understanding how that threat relates (vulnerability) to your organization, assessing the cost and providing that information to management. The formula is simple, let’s break it down.

Risk = Threat x Vulnerability x Cost

1. State the threat in language that is easily understood. It is your job to decrypt the threat for your management team.
2. Portray clearly and accurately what the threat could do and how it would possibly perform in your environment.
3. Identify the number of assets which may be affected by the threat. What is percentage of vulnerable devices in relation to the total devices? (Servers, workstations, operating systems, Internet exposure)
4. Identify the corrective measures which are available to be taken.
5. Calculate the SLE (Single Loss Expectancy). What is the dollar value of the cost that equals the total cost of the risk?
6. State how the remediation would lower the exposure to the organization and give a cost for those actions.
7. Recalculate the SLE with projected remediation included.
8. Provide status of the protection mechanisms already in place (anti-virus definitions, IPS signature detections, patching statistics).
9. Then allow management to make an educated decision based on risk to the enterprise, not just the security event itself.

By utilizing this concrete methodology, we can lessen the influence of media hype and provide a professional cost based opinion to those best equipped to make enterprise decisions.

Source:  http://www.dshield.org/diary.html?storyid=6223 by Mari Nichols

Related articles by Zemanta

• Top Ten Ways to Know If You Have the Conficker Virus (ethelthefrog.com)

In just under a minute I migrated a couple of GrandCentral account to Google Voice and I am very exited to see a transcript of a voicemail show up in my Inbox.

I will definitely miss the GrandCentral interface as its much more intuitive than the new Google Voice GUI.

A limitation currently in place on both platforms is the capability to have 2 different accounts ring one same number. I particularly like this to have a personal and a business number both ring my cell and landlines. The workaround for the moment is leaving an account with GrandCentral and on one Google Voice. Lets see how long that lasts.!

One thing that I have seen more and more recently is my GrandCentral dropping calls on me. Maybe its Google’s way of getting users migrated.

Related articles by Zemanta

• Google Voice Emerges from GrandCentral, Transcribes Voicemail (lifehacker.com)
• Google Voice: Bells, Whistles, and Voicemail Transcripts (blippitt.com)
• Google Voice: A New Approach to Voice Communications (littlegreenfootballs.com)
• Google Launching GrandCentral As Google Voice (searchenginewatch.com)