Archive group: Script to create new database with selected group and archive new database

[cgrunenberg]

@tjur

I’m assuming encrypted databases can’t be created via Applescript. Correct? But is it possible to disable the spotlight index via Applescript?

We’ll consider this for future releases.

[tjur]

Also setting up username and password for importing/syncing should be possible via script.

Thanks a lot!

[chrillek]

@tjur

Also setting up username and password for importing/syncing should be possible via script.

I respectfully disagree. Passwords should never, ever be set in clear text in a script. Did I say never?

You presumably want to encrypt your database to protect them from unauthorized access. Which, in your scenario, implies that someone might have access to your machine (how else would they be able to get at your databases). Which, in turn, means that they can read your scripts. Containing passwords? So, your scenario is that an authorized person is intelligent enough to find your databases, but too stupid to read your scripts? Seriously?

To reiterate: Never store your password in a script. Not in DT, not in Python, not in AppleScript. Never. I’d actually prefer no password “protection” at all. Instead, certificates, hardware keys, anything that is more difficult to guess and steal.

[tjur]

You’re right, of course, but it’s also possible to prompt for the name and password…

[chrillek]

First off, I’m not sure what these “encrypted” databases really are. The manual says

Encrypted Databases: If you have databases containing sensitive or private information, you can create an encrypted database. This is specialized AES-256 encrypted disk image that will not appear in the Finder or your desktop when it’s open.

But @BLUEFROG stated that a password protected database is not encrypted:

Sync an encrypted database between devices - no database password necessary

Let’s keep the terminology clear (and it’s important, not pedantic)… There is no password on a sync location. There is an encryption key. Its function is to scramble the data when syncing and allows storing the sync data in an encrypted state. There is no encryption key on a database. There is a password. It does not encrypt anything. A password is the same as the key to a safe or a door. Only those with a key, those using the key, can open and get into it. So applying a password in the Databa…

Regardless: I’d still rather use some hardware protection than a password, if I had to. Passwords can be brute-forced or guessed.

[tjur]

To clarify… there are three ways to protect the database or sync:

1. Encrypted database (AES-256 encrypted disk image > .dtSparse): The database is fully encrypted on local disk on a dmg-Volume. Without the password you cannot open the database.

2. Password protection for importing (set up in database properties): Asks for name and password if you want to import the database from sync location. Without the credentials you cannot import a database from a sync location.

3. Encryption with password protection for sync location itself (set up in sync location settings): Protects the sync location itself. Without the password you cannot join to a existing sync location.