[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

Daniel Pietzsch

Personal blog. Mostly photos.

All posts tagged with #osx

Review: Photos for OS X is faster than iPhoto but less powerful than Aperture | Macworld

macworld.com

Another detailed review.

Opinion: Can an Aperture user be happy with Apple's new 'Photos' software?

dpreview.com

Jeff Keller’s photo editing software history seems to be pretty close to my experience. He’s not going to use the new Photos app:

Given everything that I’ve said above, you can probably tell that I’m not enthused about Photos. Not just because of the loss of features from Aperture, but also the software’s incredibly dumbed down interface, which feels a bit like someone stuffed an iPad into my MacBook Pro.

Automator actions, geotags, and more advanced tricks for Photos for OS X

macworld.com

Some great tips there. More or less remedies the concerns I have with moving from Aperture to the new Photos app.

Notes on Migrating from Aperture to Photos for OS X

speirs.org

Helpful post from Fraser Speirs:

This is the story of migrating from a system that involved Aperture and a bunch of jury-rigged hacks to Apple’s new Photos for OS X.

How to use Photos for OS X: The ultimate guide

imore.com

Currently reading through this. I’d like to replace Aperture, but the new Photos app doesn’t (yet) seem to be a drop-in replacement. The things I’d definitely be missing would be geotagging and Automator/AppleScript support and maybe third-party adjustments/presets.

Signing and encrypting my emails with S/MIME

There are basically two popular ways to sign and encrypt one’s email messages: S/MIME and PGP. I had a look at both and decided to start with S/MIME. But I may use PGP in the future, too, and use it alongside.

Using S/MIME (or PGP) gives me these two benefits:

  1. I can sign all my emails, verifying that I am indeed the owner of the email address in the “From:” field.
  2. I can encrypt my messages for the recipient, if I have stored his or her S/MIME certificate (once you receive a S/MIME-signed email, you have also obtained the correspondent’s certificate).

I chose S/MIME first, because it is way easier to use: it’s integrated into all or most popular email clients and so there’s no need to install any additional software. And you can continue to use your email clients of choice, even for encrypted messages.

Here are the few things I needed to do, in order to sign and encrypt my email messages on my Mac and my iPhone using S/MIME:

  1. Obtaining a S/MIME email certificate. I got my class 1 certificate for free at Comodo.
  2. Opening and storing the certificate with my Mac’s Keychain Access. (At this point, my Mac was completely configured. From then on, Mail offered me to sign and encrypt my messages).
  3. Exporting it from there as a password-protected .p12 file.
  4. Copying it to the iPhone and installing it.
  5. In the iPhone preferences under Mail > (Email Account) > Account > Advanced, I turned on “S/MIME” plus “Sign” and “Encrypt”.

While this only took me 15 minutes, I wish this process was more straightforward, so this would be more easily accessible to less computer-savvy people, too. But it’s definitely easier than setting up PGP.
A more detailed description on how to set up S/MIME on a Mac and iOS device can be found in the article “How to secure your e-mail under Mac OS X and iOS 5 with S/MIME” on ars technica.

At last, here are some more links on the topic, that I find useful: