He could find flaws in your ruleset and (try to) exploit them. However, you can mitigate that risk (to a degree) by obfuscating or omitting public IP addresses, or by posting only snippets from it. After all you can't not post your ruleset if you want to discuss it. ^_^
I agree, I don't think it is a problem to post it as long as you change/remove any identifying information from them. I also suggest not posting from a machine behind your firewall as it is quite easy to determine from what IP the post was made hence negating much of your work to hide your public IPs from the posted configs.
OK - DNS has to be on port 53, and is generally open to everyone. HTTP is generally on port 80, and may or may not be open to everyone. SSH defaults to 22. Who do you want to allow access to SSH? Everyone? (Why?) If so, thats one problem. Specific individuals well known to you? If so, there is nothing that absolutely requires SSH to be on port 22 (though moving it may run into others firewall complications - some administrators only allow outbound SSH to port 22). Also, there is rarely a valid reason to allow access to your SSH server from everywhere. You say you're "not doing anything fancy" - so you wouldn't be showing anything like portknocking ports - so it boils down to showing what any skript kiddiez would be able to find with a simple port-scan anyway.
As for the rest of the services, what can be so secret about '-j REJECT'?
If your rule set has errors, will someone tell you about it and you get it fixed before some skript kiddiez can try to exploit the error?
80 lines? Probably not a problem - are the comments necessary for other to understand something? But as you've also stated you are going to post them to comp.os.linux.security, why not combine the posts by listing both newsgroups (comma separated) in the newsgroup header, and perhaps include a Followup-To: header - that way you're going to waste a bit less bandwidth.
If you've moved a service to a different port, you need not show the "real" port it's been moved to. If you are restricting access to certain IP ranges, you might consider showing those as RFC3330 ranges - 192.0.2.0/24 is often used for that, 198.18.0.0/15 is another, but there are still whole /8s that IANA hasn't released - see
I figured the comments would be helpful so that others can understand my intent and tell me how my dumbo attempts to achieve that intent are doomed to failure. :-)
As for posting in c.o.l.s, I guess I should have done that in the manner you suggest, but for now I've just posted it here.
It ended up a shade over 80 lines (134 lines actually) with some added comments; it's in the new "Sample iptables rules list, inviting your suggestions / criticisms" thread. Hope it didn't get thoroughly trashed by newsreader reformatting... :-(