Chuck Norris has nothing on Paul Clarke. Here’s my Top 10 reasons why:
10 – Documented message priorities are 0-9 but there’s an undocumented “Paul” priority.
9 – Paul doesn’t use message selectors. He just thinks about which message he wants and the QMgr delivers it.
8 – There is no message expiry. Only messages that Paul has allowed to live and those he has not.
7 – The signed certs trust the CA but the CAs trust Paul.
6 – Paul used to get terrible service in restaurants so he optimized the put-to-getting-waiter algorithm.
5 – Andy Stanford-Clark’s house has a sign out front that reads “Powered by Paul.”
4 – Paul authenticates to your QMgr with “it’s me.”
3 – When WebSphere MQ was invented they found a message already on the queue with the MQMD.UserID == pclarke.
2 – Paul doesn’t need his passport at customs. He shows them his identity context.
And the #1 Paul Clarke fact:
Paul can cause a message in a rolled back UOW to be committed *and* still maintain transactional integrity!
PCI zone and non PCI zone in same DataPower box
I’ve been having PCI Déjà vu lately. It seems the same questions keep coming up over and over. One strategy for compliance that is nearly ubiquitous is to segregate the PCI data from the rest of the network. In practical terms, this usually means a dedicated subnet or network, firewalled from the rest of the intranet and with dedicated software and hardware components. When people approach PCI compliance as simple configuration they eventually ask “why not put the non-PCI data in the PCI enclave?” The theory is that if the PCI network is good enough for the PCI data then it is good enough for the less sensitive data and having just one set of components would cut costs. Because I’m lazy and didn’t want to write yet another response to this, I thought I’d post the latest one here.
Continue reading →
Share this: