From: Toni M. <sup...@oe...> - 2006-09-16 16:26:20
|
Hello George, On Fri, 08.09.2006 at 15:57:21 +1000, GeorgeOsvald <geo...@ya...> wrote: > On Friday 08 September 2006 09:55, Josh Berkus wrote: > > Well, security is something you implement at every level, not just at the > > gateway. So: SSL: yes, Domain limits: Yes, server lockdown: yes, strong > > passwords: yes, secure session tracking: yes, database security: yes, > > database auditing: yes. What you *don't* do is implement security in one > > area (like SSL or VPN) and expect that you don't need to worry about > > security anywhere else. That's a fast way to get hacked. > > You can do bit more than that depending on your level of paranoia. I am > extremely paranoid. When it comes to security redundancy is a good thing. nothing of all this helps you in case you *want* your server online, like when you're offering hosted SL. Fortunately, we don't so far, but with this experience in mind, I doubt we ever will. > Frankly If I had an employee who would be able to hack SL he/she would not be > working as an accountant. You can still search the logs to find out who was > logged in and did what. This depends on the degree of access the bad guy had to your server(s). If the claim that finding out the users of SL with almost no prior knowledge is valid, you'll only find in your logs that you were the one committing some kind of crime because the impostor impersonated you. Best, --Toni++ |
From: GeorgeOsvald <geo...@ya...> - 2006-09-17 01:00:43
|
On Sunday 17 September 2006 02:26, Toni Mueller wrote: > Hello George, > > On Fri, 08.09.2006 at 15:57:21 +1000, GeorgeOsvald <geo...@ya...> wrote: > > On Friday 08 September 2006 09:55, Josh Berkus wrote: > > > Well, security is something you implement at every level, not just at > > > the gateway. So: SSL: yes, Domain limits: Yes, server lockdown: yes, > > > strong passwords: yes, secure session tracking: yes, database security: > > > yes, database auditing: yes. What you *don't* do is implement > > > security in one area (like SSL or VPN) and expect that you don't need > > > to worry about security anywhere else. That's a fast way to get > > > hacked. > > > > You can do bit more than that depending on your level of paranoia. I am > > extremely paranoid. When it comes to security redundancy is a good thing. > > nothing of all this helps you in case you *want* your server online, > like when you're offering hosted SL. Fortunately, we don't so far, but > with this experience in mind, I doubt we ever will. I have had servers on line for the last three years. No problems so far. It works very well for me. I asked a question some time ago during all the commotion if anyone ever had any security breaches. So far zippo. > > Frankly If I had an employee who would be able to hack SL he/she would > > not be working as an accountant. You can still search the logs to find > > out who was logged in and did what. > > This depends on the degree of access the bad guy had to your server(s). > If the claim that finding out the users of SL with almost no prior > knowledge is valid, you'll only find in your logs that you were the one > committing some kind of crime because the impostor impersonated you. This was again only theory because in my case only two people access the servers. How ever if anyone wanted to impersonate me then they would have to do it either from my computer/my account (not likely) or they would have to know where to go exactly, spoof the IP, get through the first firewall/NAT, get authorized by proxy, get authorized by xinetd/apache and only then get authorized by SL. There are various levels of logging along the way as well. It would be easier to simply steal the box. > > Best, > --Toni++ > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users |
From: Luke <sl...@li...> - 2006-09-17 04:25:50
|
On Sun, 17 Sep 2006, GeorgeOsvald wrote: > I have had servers on line for the last three years. No problems so far. It > works very well for me. I asked a question some time ago during all the > commotion if anyone ever had any security breaches. So far zippo. I have had many servers on line for years as well. While I haven't, that I know of, had direct attacks against SL: almost from the week that our static IP addresses were assigned to machines, various machines have been under attack. The most common are attacks against apache (hard to prove), and definite attacks against our necessary public FTP server and name servers. I have no doubt, that it is only a matter of time before SL gets attacked. SSL does not prevent it, and we can't really block based upon IP addresses, because of mobile client users. For the same reason, it is difficult to implement any kind of htaccess authorization scheme, unless I write one that interfaces with SL's existing authorization system. It is not always possible, or reasonable, to bullet-proof a server as you claim to have done. Luke |
From: Trevor H. <tre...@th...> - 2006-09-17 10:05:15
|
Luke wrote: > On Sun, 17 Sep 2006, GeorgeOsvald wrote: > >> I have had servers on line for the last three years. No problems so far. It >> works very well for me. I asked a question some time ago during all the >> commotion if anyone ever had any security breaches. So far zippo. > > I have had many servers on line for years as well. While I haven't, that > I know of, had direct attacks against SL: almost from the week that > our static IP addresses were assigned to machines, various machines have > been under attack. > > The most common are attacks against apache (hard to prove), and definite > attacks against our necessary public FTP server and name servers. > > I have no doubt, that it is only a matter of time before SL gets attacked. > SSL does not prevent it, and we can't really block based upon IP > addresses, because of mobile client users. > For the same reason, it is difficult to implement any kind of htaccess > authorization scheme, unless I write one that interfaces with SL's > existing authorization system. > > It is not always possible, or reasonable, to bullet-proof a server as you > claim to have done. > > Luke > For clarification. A .htaccess file in /usr/local/sql-ledger containing something like: AuthType Basic AuthName "Accounts" AuthUserFile /var/www/passwd/passwords Require valid-user Add a line in the sql-ledger-httpd.conf file under: <Directory /usr/local/sql-ledger> SSLRequireSSL Create the usernames and passwords using Apache's htpasswd utility -stored in /var/www/passwd/passwords referred to in the .htaccess file above. Choose sensible usernames and passwords - preferably different to the those used for SQL-Ledger login. Create a Digital certificate, and make sure httpd/apache uses it. Block port 80, open port 443 This assumes you are using a recent version of Apache/httpd Or for a lot of users make httpd authenticate access against an LDAP or AD server. You will have two usernames and passwords to enter to use SQL-Ledger, but your server will be much more secure. Regards Trevor Hennion http://www.infocentrality.co.uk |
From: Luke <sl...@li...> - 2006-09-18 02:43:53
|
On Sun, 17 Sep 2006, Trevor Hennion wrote: > > SSL does not prevent it, and we can't really block based upon IP > > addresses, because of mobile client users. > > For the same reason, it is difficult to implement any kind of htaccess > > authorization scheme, unless I write one that interfaces with SL's > > existing authorization system. > > > > It is not always possible, or reasonable, to bullet-proof a server as you > > claim to have done. > > A .htaccess file in /usr/local/sql-ledger containing something like: > AuthType Basic > AuthName "Accounts" > AuthUserFile /var/www/passwd/passwords > Require valid-user With multiple corporations, with multiple users each, this separate maintaining of username password combinations, would be highly annoying, and prone to error. Also worth considering, is that with two sets of user names and passwords, users are even more likely to start writing things down, or keeping other sorts of penetrable records. Application level security is the problem and the solution here. > Add a line in the sql-ledger-httpd.conf file under: > <Directory /usr/local/sql-ledger> > SSLRequireSSL Just for clarity, my systems are using SSL. It encrypts transacted data. it does nothing for access security. Luke |
From: jean m. <je...@nr...> - 2006-09-19 14:07:12
|
Apache documentation says it's preferred to put authentication in the main server configuration and not use .htaccess whenever possible. The documentation says .htaccess should only be used when you don't have access to the main server configuration file. Instead of using .htaccess you can put the lines in sql-ledger-httpd.conf, Alias /sql-ledger /usr/local/sql-ledger/ <Directory /usr/local/sql-ledger> AuthType Basic AuthName "Accounts" AuthUserFile /var/www/passwd/passwords Require valid-user AllowOverride All AddHandler cgi-script .pl AddDefaultCharset On Options ExecCGI Includes FollowSymlinks Order Allow,Deny Allow from All </Directory> works for me jean > > For clarification. > > A .htaccess file in /usr/local/sql-ledger containing something like: > AuthType Basic > AuthName "Accounts" > AuthUserFile /var/www/passwd/passwords > Require valid-user > > Add a line in the sql-ledger-httpd.conf file under: > <Directory /usr/local/sql-ledger> > SSLRequireSSL > > Create the usernames and passwords using Apache's htpasswd utility > -stored in /var/www/passwd/passwords referred to in the .htaccess file > above. > > Choose sensible usernames and passwords - preferably different to the > those used for SQL-Ledger login. > > Create a Digital certificate, and make sure httpd/apache uses it. > > Block port 80, open port 443 > > This assumes you are using a recent version of Apache/httpd > > Or for a lot of users make httpd authenticate access against an LDAP or > AD server. > > You will have two usernames and passwords to enter to use SQL-Ledger, > but your server will be much more secure. > > Regards > Trevor Hennion > http://www.infocentrality.co.uk > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > |
From: Hugh E. <he...@re...> - 2006-09-17 15:21:38
|
Hello all: Since the second week of September 2006, our web site has reported: > SQL-Ledger Temporarily Disabled > > On Friday, September 8th, we temporarily disabled access to SQL-Ledger on > the report of a security vulnerability. Multiple developers are now > working on patches. And we are evaluating our options. The open source > community made possible by the GPL license has risen to the challenge. > We're hopeful we can restore services soon and urge you to read on about > what this powerful tool can offer your campaign. But I'm eager to restore services, eager to hear of a patched release and reluctant, given everything else I have on my plate right now, to study a diff between my installed version and the fork at this time. Trevor Hennion's strategy (which would require of me, only the addition of the "AuthType Basic" piece) is so far looking like my best step forward. I'm concerned by something I read once though which suggested that this form of authentication happens before the encrypted connection is made and outside of that tunnel, making it vulnerable to sniffing. Can anyone say definitively whether that is the case? -- Hugh Esco On Sun, September 17, 2006 3:04 am, Trevor Hennion said: > For clarification. > > A .htaccess file in /usr/local/sql-ledger containing something like: > AuthType Basic > AuthName "Accounts" > AuthUserFile /var/www/passwd/passwords > Require valid-user > > Add a line in the sql-ledger-httpd.conf file under: > <Directory /usr/local/sql-ledger> > SSLRequireSSL > > Create the usernames and passwords using Apache's htpasswd utility > -stored in /var/www/passwd/passwords referred to in the .htaccess file > above. > > Choose sensible usernames and passwords - preferably different to the > those used for SQL-Ledger login. > > Create a Digital certificate, and make sure httpd/apache uses it. > > Block port 80, open port 443 > > This assumes you are using a recent version of Apache/httpd > > Or for a lot of users make httpd authenticate access against an LDAP or > AD server. > > You will have two usernames and passwords to enter to use SQL-Ledger, > but your server will be much more secure. > > Regards > Trevor Hennion > http://www.infocentrality.co.uk |
From: Luke <sl...@li...> - 2006-09-18 03:20:30
|
On Sun, 17 Sep 2006, Hugh Esco wrote: > Trevor Hennion's strategy (which would require of me, only the addition of > the "AuthType Basic" piece) is so far looking like my best step forward. > > I'm concerned by something I read once though which suggested that this > form of authentication happens before the encrypted connection is made and > outside of that tunnel, making it vulnerable to sniffing. > > Can anyone say definitively whether that is the case? I can say definitively that it is not the case--that is: the authentication via HTTP auth basic, does indeed travel over the SSL connection. Luke |
From: Dr E. L. <el...@li...> - 2006-09-08 04:45:16
|
on 9/8/06 12:38 AM Josh Berkus said the following: > True, as far as I'm concerned. I don't exactly have a lot of spare time to > work on non-core projects. But, Dieter recommended the current course of > action: if we don't like the way SQL-Ledger is run, go to another project. > So I'm just following his advice. So, then, please, get the f***k off this list with all the other whiners, who have never contributed to SL and questions by users. el -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el...@li... el108-ARIN / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Please send DNS/NA-NiC related e-mail Bachbrecht, Namibia ;____/ to dns...@na... |
From: Shawn <sg...@op...> - 2006-09-08 05:33:46
|
>> I don't know if it's deliberate or not, but I have posted a fair number >> of questions to this list which have simply not shown up? Er.. to sidetrack the discussion a little for a moment. mailing lists are not always 100% reliable. Another list I have had admin access to, as well as being a regular member, occasionally stops working for one user. It's always a different user, and the fix is always the same. Unsubscribe, re-subscribe. Why? Because it is so rare we just do not have the time/resources to try to fix the problem, and we don't want to blow away the list (and recreate it), which will loose the archive and member list, just to fix such a rare issue. The point is that if your messages do not show up on the list, first thing, check to make sure you actually addressed it to the list. Second, make sure your email account actually sent it. Third, assume a problem with the list and report it as such, so that any appropriate actions or instructions can be implemented. IF you have done all that and your messages still do not show up, chances are you are being censored. Anyone being censored (or banned), normally has done something to cause that action. It is usually NOT politics at play, as is being implied in this case. What I'm seeing right now is a very healthy discussion that will make SL stronger. Deiter's responses to some may seem odd, but I just assume that is his cultural background (i.e. Germans usually seem very blunt and demanding, middle eastern folks always seem upset, etc... in my OWN expericne of course). If you look past the bluntness and/or perceived insults, and you STILL got the answer to your problem/question/comment, then chances are there was no intentional insult. We'll see where the Fork is a year from now... :) And with that, I'm done with this conversation. I could add more, and point out a few contradictions in statements, but the log will do that for anyone who reads all messages. As far as the security issue is concerned, it's old news, and we're beating a dead horse now. peace out. Shawn |
From: Chris C. <cc...@sp...> - 2006-09-08 12:41:47
|
Why don't you get off the list? This is open source, if users critical of this product want to talk about it, they will and can. If you have a problem with them, you have the power to get off the list. You need to get over it. The discussion is helpful, and needed for this product. You need to get over it! Chris Curtis On Sep 7, 2006, at 9:45 PM, Dr Eberhard Lisse wrote: > > on 9/8/06 12:38 AM Josh Berkus said the following: > > >> True, as far as I'm concerned. I don't exactly have a lot of >> spare time to >> work on non-core projects. But, Dieter recommended the current >> course of >> action: if we don't like the way SQL-Ledger is run, go to another >> project. >> So I'm just following his advice. > > So, then, please, get the f***k off this list with all the other > whiners, who have never contributed to SL and questions by users. > > el > > -- > Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) > el...@li... el108-ARIN / * | Telephone: +264 81 124 6733 (cell) > PO Box 8421 \ / Please send DNS/NA-NiC related e-mail > Bachbrecht, Namibia ;____/ to dns...@na... > > ---------------------------------------------------------------------- > --- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users Chris Curtis Sandpoint Computers Office 208-265-1608 Cell 208-610-3062 |
From: Dr E. L. <el...@li...> - 2006-09-08 17:48:27
|
Because you can't make me. And, I can't make people critical of this product leave. But I can talk about them as much as they can talk about the program. The point is that the Source is Open but it is not an Open Source Project managed by Open Source Zealots. None of this has *NOTHING* but *NOTHING* to do with alleged vulnerabilities, or being critical of this product, this is a long standing campaign against the author *AND* his business model. greetings, el on 9/8/06 2:41 PM Chris Curtis said the following: > Why don't you get off the list? This is open source, if users > critical of this product want to talk about it, they will and can. > If you have a problem with them, you have the power to get off the > list. You need to get over it. The discussion is helpful, and > needed for this product. You need to get over it! > > Chris Curtis |
From: ovaldez <osc...@pl...> - 2006-09-08 21:31:00
|
El vie, 08-09-2006 a las 19:48 +0200, Dr Eberhard Lisse escribi=F3: > The point is that the Source is Open but it is not an Open Source > Project managed by Open Source Zealots. None of this has *NOTHING* but > *NOTHING* to do with alleged vulnerabilities, or being critical of this > product, this is a long standing campaign against the author *AND* his > business model. In that case, here is my vote of confidence for Dieter and his SQL-Ledger. --=20 Oscar A. Valdez |
From: David J P. <dav...@sy...> - 2006-09-08 23:22:26
|
So OT (sorry list, can't resist) On 9/8/06, Dr Eberhard Lisse <el...@li...> wrote: > Because you can't make me. (thumb to nose and waggling fingers ?) > > And, I can't make people critical of this product leave. and why would you want to ? > But I can talk > about them as much as they can talk about the program. and what a pain-in-the-ass that is ! congratulations, you've become the single largest (negative) factor in signal to noise ratio between me and the guy who writes my accounting software, the guy I happily paid for the documentation and access to updates. This goes for anyone else here who actually cares what happens to this software, and is reading through this list because they need to get something done ! Not as anger management therapy ! Who told you it was ok to take it out on some innocent mailing list ? > > > The point is that the Source is Open but it is not an Open Source > Project managed by Open Source Zealots. speaking for Dieter's Zealothood ? "enthusiasm level" ? Is it all getting little too open, Dr L ? > None of this has *NOTHING* but > *NOTHING* to do with alleged vulnerabilities re-read > or being critical of this product, like any sane user, issues that concern security and/or precision require some scruitiny. > this is a long standing campaign against the author *AND* his > business model. the Tin Foil Hat is ON ! I, for one, have been watching SL for a couple of years, selected it from available open source options, I obviously like the mans work, and have long held up Dieters business model as a perfectly reasonable aproach. HOWEVER, this zealot (me) IS concerned when development of key software components is stalled, sidetracked, or hi-jacked. The fork is the preferred tool to restore proper meritocracy. Whether or not we are using SQL-Ledger a year from now is, at this point, up to Dieter. There is impetus to improve this code base, as well as talent. If SL development is inclusive, it has a chance, if competitive, it will fall behind. This is the GPL in action, and if you don't like it, well... idonno, I guess you just have to cry into your keyboard while obstructing your favorite software project. and THUSLY I add your email address to your third favorite hole; /dev/null rave on, but I can't HEAR you ! (hands on ears, eyes closed) lalalalalalalalalalalalalaaaaaa !!! |
From: Chris C. <cc...@sp...> - 2006-09-08 23:25:48
|
I could have not said it better David. Good for you! Chris Curtis On Sep 8, 2006, at 4:22 PM, David J Patrick wrote: > So OT > (sorry list, can't resist) > > On 9/8/06, Dr Eberhard Lisse <el...@li...> wrote: >> Because you can't make me. > (thumb to nose and waggling fingers ?) >> >> And, I can't make people critical of this product leave. > and why would you want to ? > >> But I can talk >> about them as much as they can talk about the program. > and what a pain-in-the-ass that is ! > congratulations, you've become the single largest (negative) factor in > signal to noise ratio between me and the guy who writes my accounting > software, the guy I happily paid for the documentation and access to > updates. This goes for anyone else here who actually cares what > happens to this software, and is reading through this list because > they need to get something done ! Not as anger management therapy ! > Who told you it was ok to take it out on some innocent mailing list ? >> >> >> The point is that the Source is Open but it is not an Open Source >> Project managed by Open Source Zealots. > speaking for Dieter's Zealothood ? "enthusiasm level" ? Is it all > getting little too open, Dr L ? > >> None of this has *NOTHING* but >> *NOTHING* to do with alleged vulnerabilities > re-read >> or being critical of this product, > like any sane user, issues that concern security and/or precision > require some scruitiny. >> this is a long standing campaign against the author *AND* his >> business model. > the Tin Foil Hat is ON ! > I, for one, have been watching SL for a couple of years, selected it > from available open source options, I obviously like the mans work, > and have long held up Dieters business model as a perfectly reasonable > aproach. HOWEVER, this zealot (me) IS concerned when development of > key software components is stalled, sidetracked, or hi-jacked. The > fork is the preferred tool to restore proper meritocracy. Whether or > not we are using SQL-Ledger a year from now is, at this point, up to > Dieter. There is impetus to improve this code base, as well as talent. > If SL development is inclusive, it has a chance, if competitive, it > will fall behind. This is the GPL in action, and if you don't like it, > well... idonno, I guess you just have to cry into your keyboard while > obstructing your favorite software project. > > and THUSLY I add your email address to your third favorite hole; / > dev/null > rave on, but I can't HEAR you ! > (hands on ears, eyes closed) > lalalalalalalalalalalalalaaaaaa !!! > > ---------------------------------------------------------------------- > --- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users Chris Curtis Sandpoint Computers Office 208-265-1608 Cell 208-610-3062 |
From: Dr E. L. <el...@li...> - 2006-09-08 23:44:08
|
You three. Why can't you whiners get lost? There is the fork, create the list and be done with it. Who told me it was ok? I now need some American's permission to post to a list? But then that's another story. el on 9/9/06 1:26 AM Chris Curtis said the following: > I could have not said it better David. Good for you! > > Chris Curtis > > > > On Sep 8, 2006, at 4:22 PM, David J Patrick wrote: > >> So OT >> (sorry list, can't resist) >> >> On 9/8/06, Dr Eberhard Lisse <el...@li...> wrote: >>> Because you can't make me. >> (thumb to nose and waggling fingers ?) >>> And, I can't make people critical of this product leave. >> and why would you want to ? >> >>> But I can talk >>> about them as much as they can talk about the program. >> and what a pain-in-the-ass that is ! >> congratulations, you've become the single largest (negative) factor in >> signal to noise ratio between me and the guy who writes my accounting >> software, the guy I happily paid for the documentation and access to >> updates. This goes for anyone else here who actually cares what >> happens to this software, and is reading through this list because >> they need to get something done ! Not as anger management therapy ! >> Who told you it was ok to take it out on some innocent mailing list ? >>> >>> The point is that the Source is Open but it is not an Open Source >>> Project managed by Open Source Zealots. >> speaking for Dieter's Zealothood ? "enthusiasm level" ? Is it all >> getting little too open, Dr L ? >> >>> None of this has *NOTHING* but >>> *NOTHING* to do with alleged vulnerabilities >> re-read >>> or being critical of this product, >> like any sane user, issues that concern security and/or precision >> require some scruitiny. >>> this is a long standing campaign against the author *AND* his >>> business model. >> the Tin Foil Hat is ON ! >> I, for one, have been watching SL for a couple of years, selected it >> from available open source options, I obviously like the mans work, >> and have long held up Dieters business model as a perfectly reasonable >> aproach. HOWEVER, this zealot (me) IS concerned when development of >> key software components is stalled, sidetracked, or hi-jacked. The >> fork is the preferred tool to restore proper meritocracy. Whether or >> not we are using SQL-Ledger a year from now is, at this point, up to >> Dieter. There is impetus to improve this code base, as well as talent. >> If SL development is inclusive, it has a chance, if competitive, it >> will fall behind. This is the GPL in action, and if you don't like it, >> well... idonno, I guess you just have to cry into your keyboard while >> obstructing your favorite software project. >> >> and THUSLY I add your email address to your third favorite hole; / >> dev/null >> rave on, but I can't HEAR you ! >> (hands on ears, eyes closed) >> lalalalalalalalalalalalalaaaaaa !!! >> >> ---------------------------------------------------------------------- >> --- >> Using Tomcat but need to do more? Need to support web services, >> security? >> Get stuff done quickly with pre-integrated technology to make your >> job easier >> Download IBM WebSphere Application Server v.1.0.1 based on Apache >> Geronimo >> http://sel.as-us.falkag.net/sel? >> cmd=lnk&kid=120709&bid=263057&dat=121642 >> _______________________________________________ >> sql-ledger-users mailing list >> sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users > > > > > > > Chris Curtis > Sandpoint Computers > Office 208-265-1608 > Cell 208-610-3062 > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > sql-ledger-users mailing list > sql...@li... > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el...@li... el108-ARIN / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Please send DNS/NA-NiC related e-mail Bachbrecht, Namibia ;____/ to dns...@na... |
From: Luke <sl...@li...> - 2006-09-09 20:52:28
|
On Sat, 9 Sep 2006, Dr Eberhard Lisse wrote: > You three. > > Why can't you whiners get lost? There is the fork, create the list and > be done with it. > > Who told me it was ok? I now need some American's permission to post to > a list? But then that's another story. I thought NEGATIVE mass (antimatter) annihilated with regular mass. By that rule, and the theory of asymmetry, shouldn't you have evaporated in a ball of gamma rays by now, thereby leaving those of us who want to hear both sides of the issue, to just get on with it? You are the most disruptive influence I have ever seen in my ten plus years of running and being on mailing lists, and some of those were lists for divisive political organizations! Assuming you won't go away, please at least get a spell checker, so that those who continue to read your insults, can do so without having to guess at your meaning. As sucking holes go, you and my /dev/null device can commence to battle it out. I will never post again on this subject. Disrespectfully to you, & apologetically to Dieter, Et Al, Luke |
From: Dr E. L. <el...@li...> - 2006-09-09 21:28:26
|
In the words of my TV colleague Dr House: "Do I get paid extra if I care?" el on 9/9/06 10:52 PM Luke said the following: > On Sat, 9 Sep 2006, Dr Eberhard Lisse wrote: > >> You three. >> >> Why can't you whiners get lost? There is the fork, create the list and >> be done with it. >> >> Who told me it was ok? I now need some American's permission to post to >> a list? But then that's another story. > > I thought NEGATIVE mass (antimatter) annihilated with regular mass. By > that rule, and the theory of asymmetry, shouldn't you have evaporated in a > ball of gamma rays by now, thereby leaving those of us who want to hear > both sides of the issue, to just get on with it? > > You are the most disruptive influence I have ever seen in my ten plus > years of running and being on mailing lists, and some of those were lists > for divisive political organizations! > > Assuming you won't go away, please at least get a spell checker, so that > those who continue to read your insults, can do so without having to guess > at your meaning. > > As sucking holes go, you and my /dev/null device can commence to battle it > out. > > I will never post again on this subject. > > Disrespectfully to you, & apologetically to Dieter, Et Al, > > Luke -- Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar) el...@li... el108-ARIN / * | Telephone: +264 81 124 6733 (cell) PO Box 8421 \ / Please send DNS/NA-NiC related e-mail Bachbrecht, Namibia ;____/ to dns...@na... |