madsushi

I saw this on another site discussing Trusted Root certs:

> What is required to get a Root Signing Certificate?

> Each certificate provider has different requirements for trusted rootsigning certificates. Most will require something similar to the following:

> - Substantial net worth and insurance

> - A Certification Practice Statement (CPS) outlining your exact policies on issuing and managing certificates.

> - A FIPS 140-2 Level 2 compliant device to generate and managing your root certificate keys.

So it sounds like they are handing out the keys and then hoping that auditing/policies/insurance are in place to cover themselves.

If you can only issue certificates for your domains and subdomains, then it's not an issue. This sounds more like an alternative to setting up a Windows Enterprise CA and then distributing the root cert to all of your non-Windows clients.

e: Think of it like this: instead of just giving you a wildcard cert, they're letting you make individual certs for your subdomains yourself.

Wow, finally a breach where the hackers DIDN'T make off with all of our passwords in plain-text. Kudos to Twitter for actually handling passwords properly, considering the eventuality that all websites are vulnerable to attack.

NetApp's FAS product line has 3 families: the 2xxx series, the 3xxx series, and the 6xxx series. Each of these families then also has sub-groupings based on release date/capabilities, like the 20xx series, 22xx series, etc. So the 2040 is their lowest-end filer they still sell (and that supports the latest OS version), while the 2240 is the newer build designed to replace the 2040 (better CPUs, RAM, etc).

The 2xxx series (2040 (older, but available), 2220, 2240) are all lower-end and have limited expansion capabilities, as well as including disks in the controller chassis. The 2240 is unique in that it can support a single 10Gb ethernet card or an 8Gb FC card (but not both at the same time), while the rest of the 2xxx family can't.

The 3xxx series (3140 (older), 3220, 3250) are mid-range filers with decent expansion options (SSD/Flash PCIe card, 10Gb ethernet, 8Gb fiber channel, more SAS ports, etc).

The 6xxx series (6040, 6080, with the 62xx series coming soon) are high-end filers with tons of expansion ports and built-in ports to handle larger workloads and higher total storage limits.

The v-series is designed to be a front-end to another SAN, giving you the NetApp suite of software/capabilities without rebuying all of that disk.

There's also the E-series, which is the Engenio tech they're selling after acquiring them a year or two ago. I haven't worked with that, but it's the very high-end filer.

The StoreVault ran a modified version of ONTAP, but still generally had most of the ONTAP features. Unfortunately, these were hidden by the special StoreVault System Manager. Even if you were familiar with NetApp, it was a major struggle to perform your typical tasks. The System Manager was buggy, slow, and only had the most basic workflows available. If you manually connected in to FilerView, you received a nasty warning about how dangerous/unsupported it was. But from FilerView, you could actually manage your filer the right way.

Non-savvy users struggled with the software and were steered in the wrong direction. It was incredibly frustrating being limited by the System Manager.

Now, the low-end filers like the 2040 occupy the same space, and are "full" NetApps so you don't have to worry about an abrupt EOL notice.

3 days?

Because the inquiring mind did zero research and asked a question so broad and so vague that it was impossible for anyone to answer it without months of work and very specific knowledge.

To quote Carl Sagan: "If you wish to make an apple pie from scratch, you must first invent the universe." I don't think anyone was wanting to sit and spend hours explaining to the author how to do something incredibly difficult and complex without the author putting anything forward. Why not just take that knowledge and do it myself?