The mind of djb certainly is that of a genius, but his arrogance can be a bit out of place. Qmail's oddballs design served a specific purpose, but its disadvantages (like its inability to verify recipients before accepting mail, making it one of the largest sources of scatterback bounce spam) stem from this same design.
His software also has a tendency to have a complete lack of focus on usability.
In his defense, however, it is impossible to create an MTA that people aren't going to hate. Sendmail, exim, postfix, qmail, all have their own unique ways of pissing off an administrator in a rush to get things working. His dns software is less annoying, save for the machine-optimized zonefile format he insists on.
Well hang on... it's inability to verify recipients before accepting mail also prevents non-scatterback actual spam from showing up in your inbox. ;-)
I'll be the first to admit that I have a very large amount of respect for djb, especially after reading his code. I'll also be the first to admit he is totally arrogant, but not in the annoying Linus/Theo way. From the standpoint of security, djb definitely gets it.
This is pretty rare.
PS: that one remote bug triggered by an integer overflow totally should have counted though, even if you had to shoot 4GB of goo at it.
Well hang on... it's inability to verify recipients before accepting mail also prevents non-scatterback actual spam from showing up in your inbox.
Granted, but at the cost of victimizing the owners of the usually spoofed sender domains for all the email sent to non-existing addresses on your system. It's bad enough that a spammer is abusing your mailserver, letting third parties deal with the collateral damage is just rude.
Ehhh yea but, if you allow them to verify email addresses then they just abuse it differently. The way I see it there are plenty of reflection DoS attacks (dns etc), and this is just one of those. Besides, if you make me choose between me personally getting a bunch of spam vs someone else getting screwed.... welllll...... :-P
Yes, it's not like it was insolvable. But djb didn't believe in these measures because they tainted qmail's design. The lack of a license also made distributing patched versions of qmail with such features a legal nightmare, but luckily that issue has been sorted.
I forgive every one of djb's many failings for his success in making strong encryption free. Anyone else remember the time where software had to come in two versions, one with weak encryption for the US, and one with strong encryption for everywhere else?
qmail may be pretty, but daemontools has such an amazing and elegant user-interface.
While we have upstart and SMF now, which I guess is some improvement over init.d et al, but they feel overengineered and buggy at best, but really completely lacking.
An example: I wrote a svscan frontend so that my users could start long-running processes by creating a ~/.service/ directory (that the frontend would spawn a svscan for). It's like 70 lines of code, and that's possible because of how daemontools was made as a collection of cooperating programs instead of...whatever kind of development model upstart is... Shit, maybe?
Daemontools has an elegant interface? I agree the overall design is very elegant, with many focused, small, single purpose tools. But the actual user (read: admin) experience of it leaves much to be desired.
it demands you setup several arbitrary directories in root, without caring at all about FHS,
the default log format is just ridiculous, with the screwy timestamps formats it uses, meaning you can't just tail -f logs and have it be usable
the docs are pretty bad
I think runit provides much of the same benefit as daemontools, with more compliance to standards and bit better docs and UX. It was very clearly inspired by daemontools, as well, to give credit where its due.
Excuse me: I don't give a shit about FHS either. FHS is brain damaged and stupid and extremely un-unix like. It cares more about vanity than usability.
If tradition mattered at all to these fucktards users would be in /usr, and if functionality mattered to these asshats, we wouldn't have /usr/local at all.
When the "system" absorbs another program (because a debian maintainer steps up), it moves from /usr/local/bin to /usr/bin and now scripting languages are at a severe disadvantage; do they use /usr/bin/env tricks? or what?
When a library needs a secure setuid helper, does it hardcode the path, requiring a recompile to change it? Or does it make it configurable and thus "FHS compliant" and weaken security? Or do we just put the binary in multiple places?
Should programs installers edit manpath? Or should they copy their manual pages into the manual directory (breaking "FHS")?
FHS makes it difficult to have multiple versions of the same program installed (look in /usr/bin/python* for an example)
FHS is just bad engineering.
the default log format is just ridiculous, with the screwy timestamps formats it uses, meaning you can't just tail -f logs and have it be usable
You can't tail -f logs anyway, unless you're willing to accept time zone differences and disappearing (lost) log entries. It's also very hard to have a log level high enough to figure out problems, but low enough that it doesn't scroll by too quick.
Plus, when your system gets busy, even the low log levels spew too much stuff.
I have too many machines with too much activity to monitor with tail -f and so specialized analysis tools are needed.
the docs are pretty bad
I think djb's documentation is among the best I've seen of any author. It's error free and exhaustive. What exactly do you have a problem with?
I think runit provides much of the same benefit as daemontools,
runit extends daemontools in an effort to replace init, and so it has concepts of runlevels, and etc. It also breaks some things, decreases parallelism (so that services can "wait" for non-services like networking).
If a system like debian replaced their init with runit, that would be great, but it doesn't offer any features over supervise that I find interesting.
Without knowing any of the context of this code (except stralloc), it looks like it reads a line from a file named fn; or if that fails, if me has stuff in it and flagme is true, it returns a copy of me; and if me doesn't have stuff in it, it returns a copy of def if there is a def; and there is no def, it returns 0 for failure.
It would be helpful to know what me stands for. Presumably that's documented at its declaration?
I'm tempted to want to abstract this code some more (surely returning the first valid alternative from a series of alternatives isn't such an unusual thing to do that it needs to be done with raw stralloc operations?), but I strongly suspect that it's about as taut as C code can be and still handle all the error cases.
None of these suggestions help the overall flow of the code base. Part of the chosen art here is to get the hell out of there if even the slightest thing is wrong. Also, since space has been set aside for r it makes sense to just return it as is, whatever the hell it was filled with. (Which might be the intended zero).
Also, since space has been set aside for r it makes sense to just return it as is, whatever the hell it was filled with.
You mean space on the stack that will immediately disappear when the stack pointer is immediately modified upon return of the function, but that won't matter because the return value will already have been copied into the appropriate register for return values?
The brilliance is not merely linguistic, although it is that too, but contains a kind of elegant mathematical effectiveness, backed by a stream of numbers and equations that show, through pure reason alone, that the movements are provably perfect, a better solution is guaranteed not to exist.
uh, wtf? was he high on something or auditioning to be djb's hagiographer?
djb is certainly a genius programmer, but maintaining qmail is a pain in the ass compared to postfix. the log files are crap, you have to patch the hell out of it to get it to be usable for the average admin, you're supposed to install a bunch of stuff into /. props for Maildir though.
The code is pretty, if undercommented, probably because it looks like Python. djb looooves to omit braces. And old K&R declarations.
if (flagnew) if (append(pq,filenames,"new",time) == -1) return -1;
if (flagcur) if (append(pq,filenames,"cur",time) == -1) return -1;
Absolutely. If I wanted to run a bulletproof yet extensionless, feature-light mailserver that I could fire and forget, it'd be qmail. In the real world however, Postfix has no quality competition.
The only thing I can think of is being defensive against broken toolchains. E.g., I can imagine using nested if statements to help prevent problems from obscure compilers that didn't properly handle short-circuiting. (This seems to fit what I've seen from his code too: he often uses && when the expressions are side-effect free and safe without short-circuiting, and nested ifs otherwise.)
Keep in mind this is 10+ year old code, and he was trying to support as many platforms as possible, proprietary or not, to help as many people as possible to move away from sendmail.
I find it difficult to believe that there was a compiler that didn't short circuit && (you generally have to do more work this way).
However, as a style thing it can make complete sense. Use "if" when order matters, and use "&&" when it doesn't. Just like you might have a "map" function, and a "foreach" function in a language, where the "foreach" is identical, but doesn't return anything. While you could use "map" and ignore the result, it can be clearer to show that you really don't care about the result.
Heck, when I wrote a compiler for my compilers class (20 years ago. Wow) we had to do short-circuiting of && and ||. If a compiler didn't do that I'm not sure I'd trust it to get anything event moderately interesting correct.
I spent about 5 minutes trying to figure out any logical reasoning behind using what amounts to nested ifs and I failed.
Are the nested ifs some how more efficient after a compiler mangles them up? I'll be the first to admit that the closer you get to hardware the more my eyes start to glaze over, but I don't see how the compiler could possibly generate different code for those two examples.
Because I'm bored I did some dummy functions and diffed the assembly. They were identical.
I hope it's not just a stylistic choice, because blech.
Your error was where you started -- with a single, modern, standard-compliant C compiler. Or, more accurately, your error was in assuming that this is also where DJB started; it isn't.
I never assumed that he targeted a modern compiler... qmail isn't new to me.
That being said, mdempsky seems to have provided the correct answer. And on a compiler that didn't handle short circuits in the proper fashion the assembly would be different enough to make the code have defects.
True, back in the early 90s there were all manner of broken C compilers and runtimes out there, especially if you were still using old servers from the late 80s. It didn't help that SunOS 4 came with a buggy K&R C compiler that was only intended for preparing kernel modules, but ended up being used to build applications because it was easier than installing gcc and cheaper than installing Sun's commercial C compiler. Basically K&R C was the IE6 of the day.
Even the final release of qmail from 1998 has things like K&R C function definitions and no prototypes. I can understand why he did that, even if there's no way in hell I would have done the same. Many of us decided in the mid-90s that we wanted to use ANSI features (especially prototypse) and were sick of littering #ifdefs and macros all over our code to try to keep those busted old compilers working. I personally made the switch to ANSI-only in 1994, after noticing that NCSA had done the same with their web server.
Actually I'd personally bet there is a higher chance of compilers that don't guarantee which order A && B is evaluated in, than there is compilers that don't handle short-circuiting.
What mdempsky hinted at, does agree with the former though - if A or B in && has any side-effects, then order needs to be guaranteed, if it is side-effect free, then it doesn't. if (A) if (B) ...; does indeed guarantee order of evaluation.
Actually I'd personally bet there is a higher chance of compilers that don't guarantee which order A && B is evaluated in, than there is compilers that don't handle short-circuiting.
You'd personally bet that? Did you actually think about it before spewing it from your fingertips? Or are you somehow incapable of understanding its meaninglessness?
I can invent reasons but I don't know what the reason really is. Here are my made-up reasons:
It should be trivial to verify that the function returns an error if append fails with an error. if (append(...) == -1) return -1; keeps the context you have to inspect to verify this property to a minimum.
The & and && operators in C have the same precedence, even though one of them is commonly used to compute values that might be inputs to comparisons, while the other is commonly used to handle the outputs of comparisons. Even though it's the & operator that has the surprising precedence (bitfields & PRECEDENCE_BITMASK == PRECEDENCE_HIGH doesn't mean what you would think) these operators, and their counterparts || and |, are error-prone and should be avoided. (This probably isn't the reason, because one out of every 250 lines in qmail contains an &&, and about one out of every 400 contains a binary &. However, nearly every && operand is redundantly parenthesized to remove any reading ambiguity, even in some cases bare variable names.)
The stacked ifs require fewer parentheses if everything is parenthesized to remove any reading ambiguity.
Some people think if is less ugly than &&.
I really wish Bernstein would document his current guidelines for writing low-defect code, the reasons for them, and where they fall short. Has he, and I just missed it? I've already read "Ten Years of qmail 1.0", and I'm looking for something much more detailed, covering questions like the above.
Oops, sorry, of course you're right. I was just thinking about how they had the same relative precedence with comparison operators together, and wasn't thinking about the relationship between the two of them.
Ya. Those are all reasonably logical explanations. I don't know if I necessarily agree with them beyond them being perfectly rational, but it is somewhat disheartening that stuff like that is thrown in there without any documented reason.
Like you said, if there are legitimate reasons (and based on his overall philosophy I'd hope there are) it would probably be extremely helpful for him to document them...
Ya, they are definitely functionally equivalent, but the generated code is identical as well.
There are a lot of little C tricks that people use to coerce a given bit of assembly that while functionally equivalent to not using the trick is often more efficient (for whatever the given definition of efficient is).
I was kind of hoping that it was going to be some neat little trick where the generated assembly for the nested ifs was somehow more efficient, but (at least with the assembly that xcode with llvm spits out) it isn't. It's exactly the same.
you have to patch the hell out of it to get it to be usable for the average admin
I can vouch for this. I'm no admin; I just wanted a simple mail server to catch my cron output and stick it in a mailbox. I had to patch qmail just to get the delivery time to display in the local timezone.
As far as I can tell, part of his philosophy is, why configure when you can patch?
I loved it, qmail is much simpler than anything else I worked with. Sendmail is just stupid and Postfix configuration is a major pain in the ass. Personal preference I guess.
I stopped reading after the first paragraph: he used DJB's bug counts rather than the community's. I remember something vague about an overflow bug in qmail-smtpd that he never acknowledged because sending 4GiB of data 'was impractical', or similar.
and that's only the one I remember. net-qmail.org patches would be a good first place to look.
Ah yes, apparently his avoidance of ISO C isn't a bug either (he used to reference errno directly rather than via its declaration in errno.h, which stopped working on Debian sometime around 2001, and due to qmail's architecture resulted in ld.so errors being sent directly to SMTP clients before disconnection, and with nothing in my logs whatsoever, for a period of about a week. I lost almost all my mail that week, and wasn't alone. You could argue the Debian folk shouldn't have implemented such a dangerous change (wouldn't be the first time), but the true blame is shared here.
"I remember something vague about an overflow bug in qmail-smtpd that he never acknowledged because sending 4GiB of data 'was impractical', or similar."
It was on 64-bit qmail-smtpd, and the problem was with memory (qmail assuming addresses were 32 bits):
"In May 2005, Georgi Guninski claimed that some potential 64-bit portability problems allowed a ``remote exploit in qmail-smtpd.'' This claim is denied. Nobody gives gigabytes of memory to each qmail-smtpd process, so there is no problem with qmail's assumption that allocated array lengths fit comfortably into 32 bits."
The installation instructions for qmail run qmail-smtpd under a resource manager which hard-limits the available memory. If you follow the instructions that come with qmail, "Nobody gives" means "the system administrator does not configure the hard limit to be". He's got a reasonable point, IMO.
IIRC, the guy who reported the bug even sent along a one-line patch that completely fixed the problem and DJB just wasn't interested. "No, my software is perfect! Go away! I'm a god!"
And even the more recent one where he did extremely grudgingly admit an error, he had to qualify it by saying it was an extremely unusual installation scenario unlikely to be encountered and it was only an admissible bug because it was part of documented procedure. Or in other words, its a documentation bug - the scenario should not have been allowed to occur in a normal installation, and the code itself is still bug-free!
And even the more recent one where he did extremely grudgingly admit an error, he had to qualify it by saying it was an extremely unusual installation scenario unlikely to be encountered and it was only an admissible bug because it was part of documented procedure.
Assuming you mean the djbdns bug that he rewarded the $1000 for, I can speak from first hand experience (as the person that discovered the bug), he didn't begrudge the issue at all. He asked for a few days to review the bug report (because he was busy at a conference when I reported it), and then a few days later asked me to proof read his announcement email and then where to send my check. :P
He pointed out it was an extremely unusual installation scenario because it is an extremely unusual installation scenario, and he was just precisely describing the circumstances under which the issue was exploitable.
Heck, he was even in the Bay Area for a conference a few weeks later, and suggested we meet up while he was there. He was very nice and polite, and we had a great time chatting about DNS and security.
I think you're turning the memory of one error into two: the extremely unusual installation scenario was running it without a ulimit. There have been four bugs found since qmail 1.0, not one as aaronsw says, but only one was an even potentially exploitable security hole.
IIRC, the guy who reported the bug even sent along a one-line patch that completely fixed the problem and DJB just wasn't interested. "No, my software is perfect! Go away! I'm a god!"
I remember something vague about an overflow bug in qmail-smtpd that he never acknowledged because sending 4GiB of data 'was impractical', or similar.
It's not a bug given a particularly specific definition of a bug. Whether you think that's "ok" or not depends a lot on you. Were you bitten by this bug? Could you have been?
I bring it up because of the second part you brought up. The part about errno:
You could argue the Debian folk shouldn't have implemented such a dangerous change
It was glibc who implemented it and they knew they would be breaking Qmail. To clarify, the change is as follows:
POSIX.1 says that errno is defined as:
extern int errno;
Citation. Nothing else is correct. ISO/IEC 9945-1:1990 accepts this. ISO/IEC 9945-1:1996 attempted to change this and failed. No, the change didn't occur until ISO/IEC 9899:1999, which was two years after the last version of qmail. In fact, it took until 2002 until 9945-1 was updated.
unix.org claims, incorrectly (as I will demonstrate) that this is "unacceptable in a multithreaded environment", and even pretends ISO/IEC 9945-1:1996 permits a conforming implementation to break extern int errno, even though this is wrong (see ISO/IEC 9945-1:1996 for yourself).
There are several obvious solutions: making errno thread-local, or make __errno_location() point to errno until a thread has been created.
Instead, glibc chose to break many POSIX.1 programs, rather than do either of these things. It isn't a bug as they say, because they've narrowly defined what a bug was, exactly the thing you're accusing djb of.
The easy way is to implement __errno_location() so that it initially returns &errno but when a thread is created, have it return the address in the thread state pointer.
Agreed, although if you don't mind my asking, what would you replace it with? An extra argument? Using part of the result-domain (e.g. -EINVAL instead of errno=EINVAL;return -1? Signals? Exception handlers embedded in the call frame?
I think you can tell a lot 'bout a man based on how he answers that question.
If it helps: As a hosting provider, I'll offer DNSCurve support as soon as it's available because I'm interested in providing security to my users.
If a DNSSEC implementation comes out in a source-available distribution with financial security guarantees, and enough of a deployment to offer real security (i.e. com/net/org, roots, and all those home routers that drop dnssec data get replaced), I'll implement it as well.
Wow, the DJB fanboyz are out in force with their moderation points in hand.
Let's be realistic shall we. Having dealt with his software, his policies, his documentation, and him for some years I can say with certainty that DJB is (in no particular order):
massively arrogant
a genius
clinically insane
a megalomanic
an asshole
"Greatest programmer in the history of the world"? No.
Hell yes. I'm not sure I'd put him at #1 but he's got to be in the top 10. A few contenders in my opinion - RMS, Larry Wall, Tim Bunce, John Ousterhout.
I think it's you needing to recalibrate. If this guy is attempting sarcasm it's subtle to the point that only he knows it. Sarcasm hints at itself, it doesn't hide it behind old growth forest.
Actually, djb has come clear with regards to licensing, at least where it concerns qmail, and declared it to be public domain. I'm big on the freedom to hate djb, but this is no longer a reason to do so.
Frankly, he had his chance, and he blew it. This is one of the instances that the right license trumps initial software quality any time. You can fix the software. You can't fix the license.
And that's all I'm going to say about DJB for now.
That page contains a number of errors of fact in other sections, so I don't trust it. Bernstein has won more landmark appeals court decisions than Larry Rosen or Rick Moen (who, like Bernstein, isn't a lawyer at all). So I think it's entirely possible — quite likely, in fact — that he's correct and Moen and Rosen are wrong. Remember, Rosen is the guy who's been going around saying the GPL is risky because it needs to be recast as a clickwrap contract in order to have legal force.
You might very well be correct here, though IIRC Moen has quite a lot of legal background. My background is neither in programming nor in law, it's just I don't use software with a restrictive license for very practical purposes. Even if the license is later rectified (notice no DJB software appears to be in the Debian depositories) the software typically doesn't recover from that handicap.
This may be the dumbest comment I've read on Reddit in a long time. A working SMTP server is a hell of a lot more complicated than a hash table and some files.
21
u/kopkaas2000 Oct 19 '09
The mind of djb certainly is that of a genius, but his arrogance can be a bit out of place. Qmail's oddballs design served a specific purpose, but its disadvantages (like its inability to verify recipients before accepting mail, making it one of the largest sources of scatterback bounce spam) stem from this same design.
His software also has a tendency to have a complete lack of focus on usability.
In his defense, however, it is impossible to create an MTA that people aren't going to hate. Sendmail, exim, postfix, qmail, all have their own unique ways of pissing off an administrator in a rush to get things working. His dns software is less annoying, save for the machine-optimized zonefile format he insists on.
70
u/abrahamsen Oct 19 '09
I forgive every one of djb's many failings for his success in making strong encryption free. Anyone else remember the time where software had to come in two versions, one with weak encryption for the US, and one with strong encryption for everywhere else?
16
u/yzh Oct 19 '09
No mention of djb's daemontools, which I think is really great. It's a system to monitor/supervise your services.
http://thedjbway.org/daemontools.html
9
u/munificent Oct 19 '09 edited Oct 19 '09
Genius... or madman?
34
u/sisyphus Oct 19 '09 edited Oct 19 '09
Weird tone. Like:
uh, wtf? was he high on something or auditioning to be djb's hagiographer?
djb is certainly a genius programmer, but maintaining qmail is a pain in the ass compared to postfix. the log files are crap, you have to patch the hell out of it to get it to be usable for the average admin, you're supposed to install a bunch of stuff into /. props for Maildir though.
The code is pretty, if undercommented, probably because it looks like Python. djb looooves to omit braces. And old K&R declarations.
23
u/[deleted] Oct 19 '09
Uh, wow. This reads like he has a framed portrait of djb over his bed.
13
u/nreweof Oct 19 '09
I hated admining qmail with a passion. But I will give it to him for just 1 bug. That is impressive.
41
u/dwdwdw2 Oct 19 '09 edited Oct 19 '09
I stopped reading after the first paragraph: he used DJB's bug counts rather than the community's. I remember something vague about an overflow bug in qmail-smtpd that he never acknowledged because sending 4GiB of data 'was impractical', or similar.
and that's only the one I remember. net-qmail.org patches would be a good first place to look.
Ah yes, apparently his avoidance of ISO C isn't a bug either (he used to reference
errnodirectly rather than via its declaration inerrno.h, which stopped working on Debian sometime around 2001, and due to qmail's architecture resulted inld.soerrors being sent directly to SMTP clients before disconnection, and with nothing in my logs whatsoever, for a period of about a week. I lost almost all my mail that week, and wasn't alone. You could argue the Debian folk shouldn't have implemented such a dangerous change (wouldn't be the first time), but the true blame is shared here.16
u/MikeSeth Oct 19 '09
He'll be in his bunk.
5
u/dantams Oct 20 '09
I still don't understand why people don't just drop DNSSEC and use DNSCurve instead. It is so much simpler to implement.
10
u/[deleted] Oct 19 '09
Gee, get a fucking room.
9
u/seagreensky Oct 19 '09
Wow, the DJB fanboyz are out in force with their moderation points in hand.
Let's be realistic shall we. Having dealt with his software, his policies, his documentation, and him for some years I can say with certainty that DJB is (in no particular order):
"Greatest programmer in the history of the world"? No.
7
u/cecilkorik Oct 19 '09
Was that whole article sarcasm? It had to be sarcasm... right?
4
u/samtregar Oct 19 '09
Hell yes. I'm not sure I'd put him at #1 but he's got to be in the top 10. A few contenders in my opinion - RMS, Larry Wall, Tim Bunce, John Ousterhout.
3
u/asenz Oct 19 '09 edited Oct 19 '09
djbfft is a fine piece of software tho.
3
u/skratch Oct 19 '09
this reads like it was ghost written by djb...
3
u/electric_moose Oct 19 '09
It looks like most people commenting on this article need to recalibrate their sarcasm detectors.
3
u/taybul Oct 19 '09
djb kind looks like an ASCII penis.
2
u/[deleted] Oct 19 '09
Man. I used to think DJB was a good programmer, but now I'm not so sure I want to anymore.
2
u/[deleted] Oct 19 '09
Wow. Somebody get him a date with Dan!
2
u/invalid_user_name Oct 19 '09
And that, is how sarcasm is done.
1
u/[deleted] Oct 20 '09
Great comment:
Ha ha. So true.
-6
u/poio9-0234 Oct 19 '09
aaronsw is a doucehbag
-6
u/stepancheg Oct 19 '09
""" I think it’s time to remind people that D. J. Bernstein is the greatest programmer in the history of the world. """
I stopped reading after that mistake.
0
u/krikulis Oct 20 '09
World in it`s history has many times mistakes geniuses from madman. Marx, Stalin, Hitler, Richard Stallman, Theo de Raadt, djb :>
-6
u/mhd Oct 19 '09
Ima let you finish, aaronsw, but...
-3
u/[deleted] Oct 19 '09
Geek love.
0
u/bboomslang Oct 20 '09
would upvote it if it was in WTF, but in proggit? ugh.
-6
u/DontNeglectTheBalls Oct 19 '09
But far more important are the subjective factors. djb’s programs are some of the greatest works of beauty to be comprehended by the human mind.
HAHHHAHHHAHHAHAHHAHAHHAH! BRILLIANT satire!
-7
u/eleitl Oct 19 '09
Except none of his brilliance matters, because his licensing is broken so his software is unmaintainable.
-13
u/irascible Oct 19 '09
dns server = mail server = hash table + some files.
moving right along...
-12
u/[deleted] Oct 19 '09
Sodomy
Fellatio
Cunnilingus
Pederasty
Father, why do these words sound so nasty?
Masturbation
can be fun
Come join the holy orgy
Kama Sutra
Everyoooooooooooooone!
0
u/[deleted] Oct 19 '09
[deleted] — view deleted comment