Comments for Code Snips

Comment on Random Passwords by admin

admin — Thu, 08 Apr 2010 05:33:48 +0000

Another alternative, if you have OpenSSL installed, and let’s face it who doesn’t, is:

openssl rand 16 -base64

Or similar.

Comment on To Mail a File Elegantly – Python or Perl? by admin

admin — Fri, 31 Jul 2009 10:08:18 +0000

The path argument is untidy as it reveals things to the recipient that they don’t need to know and my paranoid self never likes to give too much away if I can help it. But yes you are right any of those solutions are quite usable. The regex really is there as an illustration of a point about typical Perl coding approaches rather than the way things should be done.

Comment on To Mail a File Elegantly – Python or Perl? by chorny

chorny — Sun, 26 Jul 2009 09:13:13 +0000

You need a ‘Filename’ argument for $msg->attach only if it differs from real name or use ‘Data’ instead of ‘Path’, so there is no need for file name extraction, just use ‘Path’ argument. And in any case file name extraction is better done with File::Spec module (for example, it would work on VMS).

sitedesign: I prefer to use MIME::Lite even when sending through sendmail executable.

Comment on To Mail a File Elegantly – Python or Perl? by sitedesign

sitedesign — Sun, 26 Jul 2009 03:34:55 +0000

Would also like to point out that of the various options available there are not enough options that deal with direct email to smtp servers. Most bash options such as mutt and mail require there be a local MTA installed.

The reasons behind the above two scripts was for an option that sent email directly to a SMTP server and not via a local MTA.

Being a python fan, I have to admit that I would probably choose the perl script for it’s simplicity.

A database person we know said he likes perl because it, “Is still a scripting language and does what you need it to do without too much effort.”

I would add that is true, but only after you get your head around perl.

I had a look for a good netcat script but found none.

Comment on To Mail a File Elegantly – Python or Perl? by sitedesign

sitedesign — Sun, 26 Jul 2009 03:30:20 +0000

Aaah, But as we discussed at work on Friday, you don’t get to set a payload in the perl version.

Comment on To Mail a File Elegantly – Python or Perl? by admin

admin — Sat, 25 Jul 2009 05:17:33 +0000

I agree with Perl being more readable than Python in this case. It's just nicer to look at too. On the other hand Perl tends to hide function in plain sight too, which is why I used the regex next to Getopt::long. So take another look at it, everywhere but the regex is readable, and Perl is known for its cryptic regex code: whereas while the Python example is long winded, nothing about it requires any real mental gymnastics to understand what is being done on any line. So the illustration is that in one way Perl is more readable but in another Python is. A dead heat yet again. However if it was simply a choice between the two snippets of illustrated code, I certainly prefer the Perl because of its elegance and shear class, and would use Getopt:: instead of the code I've used in the example.

Comment on To Mail a File Elegantly – Python or Perl? by chorny

chorny — Fri, 24 Jul 2009 19:03:41 +0000

IMHO Perl version is way more readable than Python’s. And if you want better command line parsing in Perl, you should use an Getopt:: module. In your case it would be Getopt::Long.

Comment on Rewriting the Wheel: bin2hex – hex2bin by admin

admin — Tue, 11 Nov 2008 08:30:08 +0000

Oh yeah, for those of you who think that this is the best way of doing things, here’s a hint:

printf(“0x%02x”,c);

Not every solution fits the same problem.

Comment on Random Passwords by sitedesign

sitedesign — Tue, 12 Aug 2008 10:57:07 +0000

Just a hint. If you are using Fedora and wish to use uuencode, you will need to install sharutils.

# yum install sharutils

should do the trick.

Comment on NZ e-Commerce Payment Gateways by admin

admin — Thu, 31 Jul 2008 10:12:53 +0000

Yes it’s really hard to get good info on the payment gateways in New Zealand. I’m not sure that even this write up is really that good. However you are quite correct about the gateways being able to be broken up into classifications; but I’d do it differently.

Of course first you need to know that I help to run some of the gateways on behalf of some of the banks. We provide access for merchants to gateways and wallet systems, others use our products in value-added reseller models who then directly interface with merchants.

So the three categories are:

1. Gateways – simple API’s into the banking system like CardPay and BuyLine.

2. Wallets – Paygo, Paypal and others where the money is held by another organisation on your behalf in a virtual wallet.

3. Resellers – like Paystation, flow2cash and SecurePayTech that focus on delivering products to merchants with value added services, like integration and troubleshooting support, advanced merchant reporting, PCI compliance etc.

DPS does most of these things and is the dominant player in the market. But I suspect is this is mostly due to visibility not real service or price. (bias warning: I don’t work for DPS).

Each bank has its own preferred gateway so I suggest that you look at your merchant’s bank and ask them which they prefer. Your merchant has some vested interest in this too as they will need to know the terms, conditions, risks and costs of doing business through whichever gateway is chosen and may wish to shop around.

Lastly:

- Do not handle the customers card details EVER,
- Know all parties involved in the transaction process,
- Minimise your risk and your customer’s,
- Keep it simple, and,
- Make sure you meet your customer’s needs.

Good luck to you and your client.