I had 39 aliases listed with my cotse.net account...some of which were \njust subscription addies to different lists. Since most of my \nsubscription addresses were not for list where I could respond, I \ndecided to unclutter my alias list by deleting them. (Since the cotse.\nnet mail server doesn't *care what sort of alias I use, it's wide open \nto *any mail to me that I don't even have listed...I figured I'd take \nadvantage of this security breach, and make it work for me in some way.)\n\n(Of course, I keep a separate list of *all my aliases in a text file, in \norder to keep track of what addies *I created, vs. what addies some \nspammers might come up with, to take advantage of cotse.net's security \nbreach.)\n\nSo, after deleting my fifth trivial aliases, and the alias page \nreloaded..guess what? All remaining aliases the *were listed under the \nlast one I deleted, were GONE, GONE, GONE. This included *seven \nnon-trivial aliases that I never wanted to delete!\n\nExiting my account and relogging back in, did *not clear up the problem.\n..thus, this is yet one *more glitch I've inadvertently discovered.\n\nSo, WARNING TO ALL COTSE.NET USERS:\n\nKeep a separate text file of *all aliases you use, on your hard drive. \nThere is not telling *when you'll wind up losing any aliases you've \nregistered in your account.\n\nNo wonder cotse.net apologists prefer me to post my queries to either \nthe helpdesk or chat help...as posting in newsgroups puts any reports \nprobable glitches on public record! This obviously includes those \nglitches which cotse.net admins (and owner) already *know about, but do \nnot care to admit.\n\nAs for *another apologist who said I'd make a good beta tester because I \ntest unusual situations: well...none of the things I've done on cotse.\nnet are out of the range of *normal usage for an active subscriber. I \ndid *not go out of my way to discover *any glitches, I just simply began \nusing and learning about the standard features that most subscribers \nwould enjoy using.\n\nMy conclusion: cotse.net is filled with unreported glitches...some of \nwhich may compromise a user's security, as well as erase one's settings \nin some sections (such as the alias list), and unduly inconvenience \nsubscribers who put their trust in a service that is *supposed to \nspecialize in security.\n\nWhat a hoot! Now, here come the apologists who, at last count, starting \nusing cuss words and covering up for their "leader", rather than face \nthe truth (which is the first step towards improving security and user \naccommodation).\n\nI never expected to post to alt.cotse again...but this is just \nridiculous, to have a large chunk of my aliases peremptorally erased, \njust because I wanted to delete about 10 (of my 39). So, for the sake of \nthe *decent subscribers who think cotse.net is "all that", I say:\n\nCaveat emptor.\n\nIf I stumble upon any other glitches, I'll surely report them here...but \ndon't expect me to participate in any thread, due to certain hostile \nparticipants, including the owner himself. \n\n I can't imagine what *other glitches I'll discover, as I learn more \nabout this flakey service...but I'm *sure I'll find 'em...without *ever \nhaving to perform other-than-usual tasks provided by cotse.net.\n\nP.S.: Besides poor response time (if *any) via helpdesk, I find that the \nIRC online help can often be useless. The one client I subscribed to \ncotse.net, had trouble setting up the stunnel.conf. He went to IRC and \nasked them is his settings were correct...they only asked to see the \n"connect" and "accept" settings.\n\nThey told him to change this: \n\naccept = 127.0.0.1:8082\n\nTo this:\n\naccept = 127.0.0.1:8081\n\nOkay, so he did that. Now, please realize that cotse.net's own *help \nfile says to use 8082, which is what my client did. See:\n\n[URL]https://www.cotse.net/support/stunnel.html[/URL]\n\nBut after making that change, he *still couldn't get on. So when I \ncalled him later, he told me he still couldn't connect via cotse's \nproxy. So I dropped over and discovered the *real problem:\n\nHe had set the "CAfile" path to the executable "stunnel-4.05.exe", \ninstead of to the certificate "cotse-stunnel.pem". (The path itself was \notherwise correct.)\n\nNow, why didn't the IRC helper ask to go through the settings in \n"stunnel.conf", in the first place? There are only six to deal with, and \nall simple to see whether or not they're correct...and if not correct, \neasy to make the proper change.\n\nIRC online help is mediocre at best; so is the helpdesk e-mail; so is \nthe security; so is the e-mail service, as I've recently learned. What a \nshame!\n\nI can't fine *any reviews or discussions re. cotse.net, either through \nsearch engines, or usenet searches. I'd think that a quality service \nwould have *much discussion and favorable reviews, easily found on the \n'net. But not the case with cotse.net. Their claim that "no service \nprovides more privacy protection than we do," is untrue. They've simply \ncobbled together various features into an appealing package which, under \nthe surface, is extraordinarily flakey.\n\nOne can cobble together's one's *own quality security, with some basic \nhacker and security knowledge...using proxomitron,\n\n[URL]http://www.proxomitron.info/[/URL]\n\ncontantly updated anonymous proxy list,\n\n[URL]http://www.cybersyndrome.net/pla.html[/URL]\n\nnon-IE browser, such as Mozilla's Firefox,\n\n[URL]http://www.mozilla.org/[/URL]\n\nor Opera,\n\n[URL]http://www.opera.com[/URL]\n\nw/high security browser settings (various Mozilla & Opera sites and \nnewsgroups will keep you updated re. security and privacy. Too many to \nmenition here, and easy to find on your own).\n\nquality antivirus program,\n\n[URL]http://www.grisoft.com/[/URL]\n\nfirewall protection,\n\n[URL]http://www.zonelabs.com/[/URL]\n\nand a secure e-mail service:\n\n[URL]http://www.hushmail.com/[/URL]\n\nAll of these can be accomplished via freeware. (The services/products I \njust listed are *all free for personal use.)\n\nAnd I'm *sure there are other low-cost security "complete" package \nservices out there, that *do maintain a well-run and minimally-glitchy \nsystem, unlike cotse.net.\n\nSetting up your own free security system is *not that difficult, even \nfor non-geeks. The learning curve is *not that long, and well worth the \neducation. Most people are *so busy, that they prefer to pay for \npackaged services...which often wind up taking advantage of one's \nnaiveness about computer/Internet operations, by providing substandard \nservice, including when it comes to security. Microsoft's success in \nutilizing dishonest business practices (and their mere wrist-slap in \ncourt) has propelled *many online services to follow suit. I see *some \nof that being applied to the operations of cotse.net, among others.\n\nIn closing: it was never my intent to seek out problems or be a \nwhistle-blower on cotse.net. I rightfully assumed it was a reliable \nsecurity service. But as things have turned out, I *have become a \nwhistle blower...and thus accept this role without griping. For what I \nhave learned is nonetheless of value, and will be part of my own *free \nsecurity package I'll provide to our hacktivist community, in the great \nopen-source/freeware tradition.\n\nP.S.: The author of Proxomitron-\-a great freeware online security \nprogram that surpasses any other-\-has recently passed away. Truly a \ngreat loss to the hacker world, and to democracy at large. Not to \nmention his family, friends, and associates...he was still young. He was \nScott R. Lemmon.