Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #58567 > unrolled thread
| Started by | Νίκος Γκρ33κ <nikos.gr33k@gmail.com> |
|---|---|
| First post | 2013-11-06 17:25 +0200 |
| Last post | 2013-11-16 10:40 +0000 |
| Articles | 20 on this page of 220 — 47 participants |
Back to article view | Back to comp.lang.python
To whoever hacked into my Database Νίκος Γκρ33κ <nikos.gr33k@gmail.com> - 2013-11-06 17:25 +0200
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-06 10:34 -0500
Re: To whoever hacked into my Database Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-07 21:20 +0000
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-07 14:39 -0700
Re: To whoever hacked into my Database alex23 <wuwei23@gmail.com> - 2013-11-08 11:32 +1000
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:15 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 11:34 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 20:52 +1100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:52 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 12:00 +0200
Re: To whoever hacked into my Database Maarten <maarten.sneep@knmi.nl> - 2013-11-08 03:08 -0800
Re: To whoever hacked into my Database Tim Delaney <timothy.c.delaney@gmail.com> - 2013-11-09 00:12 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 15:48 +0200
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-08 14:55 +0100
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-08 12:05 -0500
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 13:30 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 15:57 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 14:09 +0000
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-08 15:44 +0100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 10:00 +0000
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 21:09 +1100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 13:40 +0000
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 14:02 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 17:15 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 16:06 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 18:28 +0200
Re: To whoever hacked into my Database unknown <unknown@unknown.com> - 2013-11-08 16:48 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 18:57 +0200
Re: To whoever hacked into my Database unknown <unknown@unknown.com> - 2013-11-08 17:01 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 19:09 +0200
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-08 12:16 -0500
Re: To whoever hacked into my Database Ned Deily <nad@acm.org> - 2013-11-08 09:26 -0800
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-08 20:30 +0100
Re: To whoever hacked into my Database unknown <unknown@unknown.com> - 2013-11-08 16:10 +0000
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-08 16:46 +0100
Re: To whoever hacked into my Database aurelien@xload.io (Aurélien DESBRIÈRES) - 2013-11-08 14:56 +0100
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-07 16:45 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 00:18 +0200
Re: To whoever hacked into my Database Tim Delaney <timothy.c.delaney@gmail.com> - 2013-11-08 09:45 +1100
Re: To whoever hacked into my Database Tim Delaney <timothy.c.delaney@gmail.com> - 2013-11-08 09:46 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 00:56 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 10:04 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 01:10 +0200
Re: To whoever hacked into my Database Grant Edwards <invalid@invalid.invalid> - 2013-11-07 23:18 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 01:28 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 10:32 +1100
Re: To whoever hacked into my Database Larry Hudson <orgnut@yahoo.com> - 2013-11-08 00:42 -0800
Re: To whoever hacked into my Database Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-08 18:19 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 21:18 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:12 +0000
Re: To whoever hacked into my Database Steve Simmons <square.steve@gmail.com> - 2013-11-08 01:10 +0000
Re: To whoever hacked into my Database Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-08 18:22 +0000
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:06 +0000
Re: To whoever hacked into my Database Alister <alister.ware@ntlworld.com> - 2013-11-06 15:40 +0000
Re: To whoever hacked into my Database Steve Simmons <square.steve@gmail.com> - 2013-11-06 18:02 +0100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-06 17:30 +0000
Re: To whoever hacked into my Database Νίκος Γκρ33κ <nikos.gr33k@gmail.com> - 2013-11-06 23:26 +0200
Re: To whoever hacked into my Database mm0fmf <none@mailinator.com> - 2013-11-06 21:51 +0000
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-06 22:11 +0000
Re: To whoever hacked into my Database Grant Edwards <invalid@invalid.invalid> - 2013-11-06 22:22 +0000
Re: To whoever hacked into my Database Tim Chase <python.list@tim.thechases.com> - 2013-11-06 16:34 -0600
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-07 09:54 +1100
Re: To whoever hacked into my Database Neil Cerutti <neilc@norwich.edu> - 2013-11-07 13:43 +0000
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-06 23:52 +0000
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-07 10:57 +1100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-07 00:11 +0000
Re: To whoever hacked into my Database Ethan Furman <ethan@stoneleaf.us> - 2013-11-06 16:22 -0800
Re: To whoever hacked into my Database Tim Chase <python.list@tim.thechases.com> - 2013-11-06 21:07 -0600
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-07 12:00 +1100
Re: To whoever hacked into my Database Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-11-06 23:06 -0500
Re: To whoever hacked into my Database Tim Chase <python.list@tim.thechases.com> - 2013-11-07 06:09 -0600
Re: To whoever hacked into my Database bob gailer <bgailer@gmail.com> - 2013-11-07 07:19 -0500
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-07 16:27 +0000
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-07 01:01 -0800
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-07 01:13 -0800
Re: To whoever hacked into my Database Jussi Piitulainen <jpiitula@ling.helsinki.fi> - 2013-11-07 11:35 +0200
Re: To whoever hacked into my Database Steve Simmons <square.steve@gmail.com> - 2013-11-07 09:15 +0000
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-07 01:31 -0800
Re: To whoever hacked into my Database Alister <alister.ware@ntlworld.com> - 2013-11-07 10:06 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-07 15:46 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 00:59 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-07 16:16 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 01:33 +1100
Re: To whoever hacked into my Database Neil Cerutti <neilc@norwich.edu> - 2013-11-07 14:58 +0000
Re: To whoever hacked into my Database Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-11-07 16:13 +0100
Re: To whoever hacked into my Database Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-11-07 19:22 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-07 15:47 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-07 16:34 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-07 19:42 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-07 18:11 +0000
Re: To whoever hacked into my Database MRAB <python@mrabarnett.plus.com> - 2013-11-07 18:28 +0000
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-07 11:45 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-07 19:45 +0200
Re: To whoever hacked into my Database Denis McMahon <denismfmcmahon@gmail.com> - 2013-11-07 21:29 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 00:31 +0200
Re: To whoever hacked into my Database ishish <ishish@domhain.de> - 2013-11-08 00:32 +0000
Re: To whoever hacked into my Database Johannes Findeisen <mailman@hanez.org> - 2013-11-06 23:28 +0100
Re: To whoever hacked into my Database Gene Heskett <gheskett@wdtv.com> - 2013-11-06 18:19 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 10:20 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 19:31 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 10:59 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:19 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 11:37 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:58 +0000
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-08 04:59 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 11:39 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 09:55 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 12:05 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-08 21:13 +1100
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-08 14:27 +0100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-08 13:31 +0000
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-08 14:53 +0100
Re: To whoever hacked into my Database rurpy@yahoo.com - 2013-11-08 09:11 -0800
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 05:08 +1100
Re: To whoever hacked into my Database rusi <rustompmody@gmail.com> - 2013-11-08 19:15 -0800
Re: To whoever hacked into my Database rusi <rustompmody@gmail.com> - 2013-11-08 20:24 -0800
Re: To whoever hacked into my Database rurpy@yahoo.com - 2013-11-11 14:47 -0800
Re: To whoever hacked into my Database Joel Goldstick <joel.goldstick@gmail.com> - 2013-11-11 18:49 -0500
Re: To whoever hacked into my Database rurpy@yahoo.com - 2013-11-11 22:24 -0800
Re: To whoever hacked into my Database Tim Chase <python.list@tim.thechases.com> - 2013-11-12 05:30 -0600
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-12 00:03 +0000
Re: To whoever hacked into my Database Ned Batchelder <ned@nedbatchelder.com> - 2013-11-11 17:16 -0800
Re: To whoever hacked into my Database Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2013-11-12 18:21 +1300
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-12 09:34 +0000
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-12 20:35 +1100
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-12 11:20 +0100
Re: To whoever hacked into my Database rurpy@yahoo.com - 2013-11-11 22:31 -0800
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-12 10:09 +0100
Re: To whoever hacked into my Database Ned Batchelder <ned@nedbatchelder.com> - 2013-11-12 03:23 -0800
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-12 18:22 +0100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-12 23:25 +0000
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-12 06:02 -0700
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-12 17:27 +0100
Re: To whoever hacked into my Database Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-11-13 00:41 +0000
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-13 09:08 +0100
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-13 23:46 +0200
Re: To whoever hacked into my Database Ned Batchelder <ned@nedbatchelder.com> - 2013-11-13 13:52 -0800
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-14 12:46 +0200
Re: To whoever hacked into my Database Alister <alister.ware@ntlworld.com> - 2013-11-14 12:32 +0000
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-14 15:24 +0200
Re: To whoever hacked into my Database Robert Kern <robert.kern@gmail.com> - 2013-11-14 13:30 +0000
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-15 00:27 +1100
Re: To whoever hacked into my Database Alister <alister.ware@ntlworld.com> - 2013-11-14 13:56 +0000
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-12 14:26 -0700
Re: To whoever hacked into my Database Ethan Furman <ethan@stoneleaf.us> - 2013-11-12 13:59 -0800
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-12 16:27 -0700
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-12 23:38 +0000
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-13 13:14 +0200
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-13 12:37 +0100
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-12 16:54 -0700
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-13 00:04 +0000
Re: To whoever hacked into my Database Ethan Furman <ethan@stoneleaf.us> - 2013-11-12 17:19 -0800
Bullying [was Re: To whoever hacked into my Database] Steven D'Aprano <steve@pearwood.info> - 2013-11-13 03:40 +0000
Re: Bullying [was Re: To whoever hacked into my Database] Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-13 07:22 -0700
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-13 10:08 +0100
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-13 05:38 -0700
Re: To whoever hacked into my Database Ian Kelly <ian.g.kelly@gmail.com> - 2013-11-13 07:10 -0700
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-13 19:11 +0100
Re: To whoever hacked into my Database superchromix <markb77@gmail.com> - 2013-11-13 10:27 -0800
Re: To whoever hacked into my Database Ned Batchelder <ned@nedbatchelder.com> - 2013-11-13 10:30 -0800
Re: To whoever hacked into my Database Steve Simmons <square.steve@gmail.com> - 2013-11-13 20:02 +0100
Re: To whoever hacked into my Database Zachary Ware <zachary.ware+pylist@gmail.com> - 2013-11-13 13:24 -0600
Re: To whoever hacked into my Database Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-11-13 19:36 +0000
Re: To whoever hacked into my Database William Ray Wing <wrw@mac.com> - 2013-11-13 15:11 -0500
Re: To whoever hacked into my Database Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-11-13 19:54 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-08 21:23 +0200
Re: To whoever hacked into my Database Neil Cerutti <neilc@norwich.edu> - 2013-11-08 20:23 +0000
Re: To whoever hacked into my Database Dotan Cohen <dotancohen@gmail.com> - 2013-11-12 11:37 +0200
Re: To whoever hacked into my Database Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-11-08 19:06 -0500
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-09 00:14 +0000
Relational data model, relations, and relationships (was: To whoever hacked into my Database) Ben Finney <ben+python@benfinney.id.au> - 2013-11-09 11:34 +1100
Re: To whoever hacked into my Database Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-11-08 19:03 -0500
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 07:54 +0200
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 08:16 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 17:20 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 08:32 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 17:37 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 09:05 +0200
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 09:54 +0200
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 10:31 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 19:39 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 10:46 +0200
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 10:50 +0200
Re: To whoever hacked into my Database Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-11-09 15:07 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 18:58 +0200
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 18:59 +0200
Re: To whoever hacked into my Database ishish <ishish@domhain.de> - 2013-11-10 01:44 +0000
Re: To whoever hacked into my Database Alister <alister.ware@ntlworld.com> - 2013-11-10 12:42 +0000
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-09 16:32 +0100
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-10 09:20 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-10 12:32 +0200
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-10 14:49 +0100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-10 17:01 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-10 15:09 +0000
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-10 16:28 +0100
Re: To whoever hacked into my Database Ned Batchelder <ned@nedbatchelder.com> - 2013-11-10 08:15 -0800
Re: To whoever hacked into my Database Antoon Pardon <antoon.pardon@rece.vub.ac.be> - 2013-11-10 20:13 +0100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-10 19:58 +0200
Re: To whoever hacked into my Database Petite Abeille <petite.abeille@gmail.com> - 2013-11-10 18:57 +0100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-10 20:46 +0200
Re: To whoever hacked into my Database Petite Abeille <petite.abeille@gmail.com> - 2013-11-10 20:16 +0100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-10 21:21 +0200
Re: To whoever hacked into my Database Petite Abeille <petite.abeille@gmail.com> - 2013-11-10 20:32 +0100
Re: To whoever hacked into my Database Rod Person <rodperson@rodperson.com> - 2013-11-10 14:54 -0500
Re: To whoever hacked into my Database Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-11-10 21:41 +0100
Re: To whoever hacked into my Database Rod Person <rodperson@rodperson.com> - 2013-11-10 15:44 -0500
Re: To whoever hacked into my Database Rod Person <rodperson@rodperson.com> - 2013-11-10 15:50 -0500
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-11 10:36 +1100
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-10 14:45 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-10 17:12 +0200
Re: To whoever hacked into my Database Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-10 15:24 +0000
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 08:35 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 17:45 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 09:11 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 18:19 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-09 09:44 +0200
Re: To whoever hacked into my Database Chris Angelico <rosuav@gmail.com> - 2013-11-09 18:57 +1100
Re: To whoever hacked into my Database Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> - 2013-11-11 11:36 +0200
Re: To whoever hacked into my Database Ferrous Cranus <nikos.gr33k@gmail.com> - 2013-11-12 15:37 +0200
Re: To whoever hacked into my Database Robert Day <robert.day@merton.oxon.org> - 2013-11-16 10:40 +0000
Page 10 of 11 — ← Prev page 1 … 8 9 [10] 11 Next page →
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2013-11-09 19:39 +1100 |
| Message-ID | <mailman.2284.1383986383.18130.python-list@python.org> |
| In reply to | #58916 |
On Sat, Nov 9, 2013 at 7:31 PM, Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> wrote: > if page and os.path.isfile( cgi_path + page ) in os.listdir( cgi_path ): > > Try pass bogus values again into my database! Well done! *slow clap* In the interests of security, you have just locked everything out, including legitimate usage! ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-09 10:46 +0200 |
| Message-ID | <l5ksol$pf9$1@dont-email.me> |
| In reply to | #58917 |
Στις 9/11/2013 10:39 πμ, ο/η Chris Angelico έγραψε: > On Sat, Nov 9, 2013 at 7:31 PM, Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> wrote: >> if page and os.path.isfile( cgi_path + page ) in os.listdir( cgi_path ): >> >> Try pass bogus values again into my database! > > Well done! *slow clap* In the interests of security, you have just > locked everything out, including legitimate usage! > > ChrisA > What ?!!?
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-09 10:50 +0200 |
| Message-ID | <l5kt1h$qpf$1@dont-email.me> |
| In reply to | #58917 |
Στις 9/11/2013 10:39 πμ, ο/η Chris Angelico έγραψε: > On Sat, Nov 9, 2013 at 7:31 PM, Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> wrote: >> if page and os.path.isfile( cgi_path + page ) in os.listdir( cgi_path ): >> >> Try pass bogus values again into my database! > > Well done! *slow clap* In the interests of security, you have just > locked everything out, including legitimate usage! > > ChrisA > Ah yes you are right! Correction! if page and page in os.listdir( cgi_path ): That should keep the site working and still leave the attacker away from my daatabase!
[toc] | [prev] | [next] | [standalone]
| From | Steven D'Aprano <steve+comp.lang.python@pearwood.info> |
|---|---|
| Date | 2013-11-09 15:07 +0000 |
| Message-ID | <527e4fbd$0$29972$c3e8da3$5496439d@news.astraweb.com> |
| In reply to | #58903 |
On Sat, 09 Nov 2013 09:05:51 +0200, Νίκος Αλεξόπουλος wrote: > Its probably unwise to post the following snippet of code that validates > user input so an attacker wouldn't pass arbitrary values to my script > but what the heck..... On the contrary, it is wise to publicise your security code. It is a very strong principle of security that you should not put your trust in obscurity. To give an analogy, your doors should be secure even if people know where the door is, what brand of lock you use, and even the type of key used. Nikos, you have annoyed and alienated enough people here that the following may not apply to you, but in general I would expect that publishing your code in a friendly forum would lead to "many eyes make shallow bugs" -- people who spotted a bug in your security code, a weakness or a flaw, would speak up and tell you. Your security should depend on the strength of the security mechanism, and not rely on others being ignorant of what security you have in place. On the other hand, it is possible to be *too* open. Secrets should not be publicised. Secrets include passwords. Occasionally they may include other things. For example, in port-knocking, the precise sequence of ports used is a secret. There is, sometimes, value in obfuscating parts of your security. E.g. rather than allowing ssh on the usual port 22, some people prefer to use some other port number for that extra bit of security. But they don't rely on that -- if the attacker manages to discover that they use port 45081 instead of 22, they still have to defeat the normal ssh security before gaining access. -- Steven
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-09 18:58 +0200 |
| Message-ID | <l5lpje$kf7$1@dont-email.me> |
| In reply to | #58946 |
Στις 9/11/2013 5:07 μμ, ο/η Steven D'Aprano έγραψε: > On Sat, 09 Nov 2013 09:05:51 +0200, Νίκος Αλεξόπουλος wrote: > >> Its probably unwise to post the following snippet of code that validates >> user input so an attacker wouldn't pass arbitrary values to my script >> but what the heck..... > > On the contrary, it is wise to publicise your security code. It is a very > strong principle of security that you should not put your trust in > obscurity. To give an analogy, your doors should be secure even if people > know where the door is, what brand of lock you use, and even the type of > key used. > > Nikos, you have annoyed and alienated enough people here that the > following may not apply to you, but in general I would expect that > publishing your code in a friendly forum would lead to "many eyes make > shallow bugs" -- people who spotted a bug in your security code, a > weakness or a flaw, would speak up and tell you. Your security should > depend on the strength of the security mechanism, and not rely on others > being ignorant of what security you have in place. > > On the other hand, it is possible to be *too* open. Secrets should not be > publicised. Secrets include passwords. Occasionally they may include > other things. For example, in port-knocking, the precise sequence of > ports used is a secret. > > There is, sometimes, value in obfuscating parts of your security. E.g. > rather than allowing ssh on the usual port 22, some people prefer to use > some other port number for that extra bit of security. But they don't > rely on that -- if the attacker manages to discover that they use port > 45081 instead of 22, they still have to defeat the normal ssh security > before gaining access. > > Thank you Steven, indeed posting my code helped me realize that it wasn't the secure code i though it were. The attacker compromised my counters database once again and that helped me push my logic further into delve into how we went successful. Now witht he last changed i have made, for 9 hours or so, my databases are intact. I feel a bit sad though because if i wasn't able to detect the flaw nobody
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-09 18:59 +0200 |
| Message-ID | <l5lpl5$kf7$2@dont-email.me> |
| In reply to | #58946 |
Στις 9/11/2013 5:07 μμ, ο/η Steven D'Aprano έγραψε: > On Sat, 09 Nov 2013 09:05:51 +0200, Νίκος Αλεξόπουλος wrote: > >> Its probably unwise to post the following snippet of code that validates >> user input so an attacker wouldn't pass arbitrary values to my script >> but what the heck..... > > On the contrary, it is wise to publicise your security code. It is a very > strong principle of security that you should not put your trust in > obscurity. To give an analogy, your doors should be secure even if people > know where the door is, what brand of lock you use, and even the type of > key used. > > Nikos, you have annoyed and alienated enough people here that the > following may not apply to you, but in general I would expect that > publishing your code in a friendly forum would lead to "many eyes make > shallow bugs" -- people who spotted a bug in your security code, a > weakness or a flaw, would speak up and tell you. Your security should > depend on the strength of the security mechanism, and not rely on others > being ignorant of what security you have in place. > > On the other hand, it is possible to be *too* open. Secrets should not be > publicised. Secrets include passwords. Occasionally they may include > other things. For example, in port-knocking, the precise sequence of > ports used is a secret. > > There is, sometimes, value in obfuscating parts of your security. E.g. > rather than allowing ssh on the usual port 22, some people prefer to use > some other port number for that extra bit of security. But they don't > rely on that -- if the attacker manages to discover that they use port > 45081 instead of 22, they still have to defeat the normal ssh security > before gaining access. > > Thank you Steven, indeed posting my code helped me realize that it wasn't the secure code i though it were. The attacker compromised my counters database once again and that helped me push my logic further into delve into how we went successful. Now witht he last changed i have made, for 9 hours or so, my databases are intact. I feel a bit sad though because if i wasn't able to detect the flaw nobody would have heed me solve it.
[toc] | [prev] | [next] | [standalone]
| From | ishish <ishish@domhain.de> |
|---|---|
| Date | 2013-11-10 01:44 +0000 |
| Message-ID | <mailman.2323.1384072299.18130.python-list@python.org> |
| In reply to | #58946 |
Am 09.11.2013 15:07, schrieb Steven D'Aprano: ... > Nikos, you have annoyed and alienated enough people here... Sorry, I DO NOT AGREE! These threads keep my entire office entertained. I would even go so far to suggest, that we should set up an entirely new mailing list for Nikos only, maybe something called like acropolis-list(at)python.org. Mea culpa, I am entirely aware that this is an IT list, but hey, when you have done 2x65ish hrs per week in a row - standing in for our Ops Guy, holidaying - you really start to appreciating little interruptions like this... Greekings ...oops, meant greetings from Tartan-Land, Sas&Co
[toc] | [prev] | [next] | [standalone]
| From | Alister <alister.ware@ntlworld.com> |
|---|---|
| Date | 2013-11-10 12:42 +0000 |
| Message-ID | <gbLfu.18569$EW5.5690@fx27.am4> |
| In reply to | #58988 |
On Sun, 10 Nov 2013 01:44:17 +0000, ishish wrote: > Am 09.11.2013 15:07, schrieb Steven D'Aprano: > ... >> Nikos, you have annoyed and alienated enough people here... > > Sorry, I DO NOT AGREE! These threads keep my entire office entertained. > I would even go so far to suggest, that we should set up an entirely new > mailing list for Nikos only, maybe something called like > acropolis-list(at)python.org. > > Mea culpa, I am entirely aware that this is an IT list, but hey, when > you have done 2x65ish hrs per week in a row - standing in for our Ops > Guy, holidaying - you really start to appreciating little interruptions > like this... > > Greekings ...oops, meant greetings from Tartan-Land, > > Sas&Co I too am leaning plenty from watching Nicos' tales of woe, thank you Nicos. To repay the favour one instant lesson i can see that you need to apply is how you are using the page variable to select pages. Do not use the value provided as the direct source of the page name instead us it as a key to look up the page in a white-list, no where do i store that white list? I know how about another database table. I know you don't seem to like using more than one table Nicos but that is daft. they are not rationed & cost nothing. Also when you fail to find a page in the white-list return nothing, there is no point in giving potential hackers any more clues than necessary. I also suggest you check your firewall you seem to have far more ports open to the public internet than should ever be necessary. to follow on from one of the other security analogy's posted here you would not put the door to your house safe on the outside wall even if you think it has a stronger lock than your front door. -- He who despises himself nevertheless esteems himself as a self-despiser. -- Friedrich Nietzsche
[toc] | [prev] | [next] | [standalone]
| From | Antoon Pardon <antoon.pardon@rece.vub.ac.be> |
|---|---|
| Date | 2013-11-09 16:32 +0100 |
| Message-ID | <mailman.2304.1384026888.18130.python-list@python.org> |
| In reply to | #58899 |
Op 09-11-13 07:32, Νίκος Αλεξόπουλος schreef: > Στις 9/11/2013 8:20 πμ, ο/η Chris Angelico έγραψε: >> On Sat, Nov 9, 2013 at 4:54 PM, Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> wrote: >>> Στις 6/11/2013 5:25 μμ, ο/η Νίκος Γκρ33κ έγραψε: >>>> >>>> Okey let the hacker try again to mess with my database!!! >>>> >>>> He is done it twice, lets see if he will make it again! >>>> >>>> I'am waiting! >>> >>> >>> >>> I have to congratulate the hacher because as it seems s/he's done it again. >>> >>> S/he's manages to actually pass fake filename values inside my db even after >>> my changes: >> >> https://en.wikipedia.org/wiki/Hubris >> >> ChrisA >> > > > I'am not saying out of arrogance but i was really under the impression i had secure my script. That is arrogance. That you with your history of misunderstandings (to put it midly) were under the impression that you had a secure script and that you thought that impression was somehow reliable is pure arrogance. > And i had until i made some new changes last night, which i think i have corrected now as we speak. Continuing the arrogance. -- Antoon Pardon
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2013-11-10 09:20 +1100 |
| Message-ID | <mailman.2311.1384035618.18130.python-list@python.org> |
| In reply to | #58899 |
On Sun, Nov 10, 2013 at 2:32 AM, Antoon Pardon <antoon.pardon@rece.vub.ac.be> wrote: >> And i had until i made some new changes last night, which i think i have corrected now as we speak. > > Continuing the arrogance. Just to put that in perspective, by the way: *EVERYONE* writes vulnerable code. Even Python itself has been found to have had significant exploits (hash randomization had to get backported a long way). There's nothing wrong with fixing security bugs; there's not even a lot wrong with the iterative process of "find bug, fix bug, find another bug, fix another bug". There are two major problems with what you did here, Nikos, and they are: 1) Starting with a hopelessly insecure system and then trying to band-aid patch it one vulnerability at a time, which is folly; and 2) Boasting that your system was now secure. The main issue is the boasting, which is utterly unwarranted arrogance. All you have to do is look at how, after boasting previously, you were provably vulnerable - which means that you clearly still had problems while you were boasting. A more humble attitude of "Oops, well, that's fixed now" without saying "Ha ha, now try to break THAT, I'm oh so perfect now" would suit you far better, based on your history. ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-10 12:32 +0200 |
| Message-ID | <l5nnch$2pq$1@dont-email.me> |
| In reply to | #58970 |
Στις 10/11/2013 12:20 πμ, ο/η Chris Angelico έγραψε: > On Sun, Nov 10, 2013 at 2:32 AM, Antoon Pardon > <antoon.pardon@rece.vub.ac.be> wrote: >>> And i had until i made some new changes last night, which i think i have corrected now as we speak. >> >> Continuing the arrogance. > > Just to put that in perspective, by the way: *EVERYONE* writes > vulnerable code. Even Python itself has been found to have had > significant exploits (hash randomization had to get backported a long > way). There's nothing wrong with fixing security bugs; there's not > even a lot wrong with the iterative process of "find bug, fix bug, > find another bug, fix another bug". There are two major problems with > what you did here, Nikos, and they are: > > 1) Starting with a hopelessly insecure system and then trying to > band-aid patch it one vulnerability at a time, which is folly; and > > 2) Boasting that your system was now secure. > > The main issue is the boasting, which is utterly unwarranted > arrogance. All you have to do is look at how, after boasting > previously, you were provably vulnerable - which means that you > clearly still had problems while you were boasting. A more humble > attitude of "Oops, well, that's fixed now" without saying "Ha ha, now > try to break THAT, I'm oh so perfect now" would suit you far better, > based on your history. > > ChrisA > Ha, ha ha! I'm safe now!! No breaks in this time!
[toc] | [prev] | [next] | [standalone]
| From | Antoon Pardon <antoon.pardon@rece.vub.ac.be> |
|---|---|
| Date | 2013-11-10 14:49 +0100 |
| Message-ID | <mailman.2333.1384092226.18130.python-list@python.org> |
| In reply to | #58998 |
Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: > Στις 10/11/2013 12:20 πμ, ο/η Chris Angelico έγραψε: >> There are two major problems with >> what you did here, Nikos, and they are: >> >> 1) Starting with a hopelessly insecure system and then trying to >> band-aid patch it one vulnerability at a time, which is folly; and >> >> 2) Boasting that your system was now secure. >> >> The main issue is the boasting, which is utterly unwarranted >> arrogance. ,,, > Ha, ha ha! > I'm safe now!! > > No breaks in this time! You just can't help yourself, can you? I predict your database will be broken in, within a week, after which you will plug one leak and after an other day boast again about how secure your system is, because you hadn't had a break in after your latest "fix". -- Antoon Pardon
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-10 17:01 +0200 |
| Message-ID | <l5o74v$nfv$1@dont-email.me> |
| In reply to | #59007 |
Στις 10/11/2013 3:49 μμ, ο/η Antoon Pardon έγραψε: > Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: >> Στις 10/11/2013 12:20 πμ, ο/η Chris Angelico έγραψε: > >>> There are two major problems with >>> what you did here, Nikos, and they are: >>> >>> 1) Starting with a hopelessly insecure system and then trying to >>> band-aid patch it one vulnerability at a time, which is folly; and >>> >>> 2) Boasting that your system was now secure. >>> >>> The main issue is the boasting, which is utterly unwarranted >>> arrogance. > ,,, > >> Ha, ha ha! >> I'm safe now!! >> >> No breaks in this time! > > You just can't help yourself, can you? I predict your database will > be broken in, within a week, after which you will plug one leak > and after an other day boast again about how secure your system is, > because you hadn't had a break in after your latest "fix". > It won't break again. 'page' variable cannot be manipulated by arbitrary url strings no more. This time is fixed for good. Your predictions are wrong.
[toc] | [prev] | [next] | [standalone]
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Date | 2013-11-10 15:09 +0000 |
| Message-ID | <mailman.2337.1384096165.18130.python-list@python.org> |
| In reply to | #59010 |
On 10/11/2013 15:01, Νίκος Αλεξόπουλος wrote: > Στις 10/11/2013 3:49 μμ, ο/η Antoon Pardon έγραψε: >> Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: >>> Στις 10/11/2013 12:20 πμ, ο/η Chris Angelico έγραψε: >> >>>> There are two major problems with >>>> what you did here, Nikos, and they are: >>>> >>>> 1) Starting with a hopelessly insecure system and then trying to >>>> band-aid patch it one vulnerability at a time, which is folly; and >>>> >>>> 2) Boasting that your system was now secure. >>>> >>>> The main issue is the boasting, which is utterly unwarranted >>>> arrogance. >> ,,, >> >>> Ha, ha ha! >>> I'm safe now!! >>> >>> No breaks in this time! >> >> You just can't help yourself, can you? I predict your database will >> be broken in, within a week, after which you will plug one leak >> and after an other day boast again about how secure your system is, >> because you hadn't had a break in after your latest "fix". >> > > > It won't break again. 'page' variable cannot be manipulated by arbitrary > url strings no more. > > This time is fixed for good. > > Your predictions are wrong. > I'm not a gambling man, but I'd put my house on the fact that your site is so insecure that even the little fingers of my team can get in. -- Python is the second best programming language in the world. But the best has yet to be invented. Christian Tismer Mark Lawrence
[toc] | [prev] | [next] | [standalone]
| From | Antoon Pardon <antoon.pardon@rece.vub.ac.be> |
|---|---|
| Date | 2013-11-10 16:28 +0100 |
| Message-ID | <mailman.2339.1384099434.18130.python-list@python.org> |
| In reply to | #59010 |
Op 10-11-13 16:01, Νίκος Αλεξόπουλος schreef: > Στις 10/11/2013 3:49 μμ, ο/η Antoon Pardon έγραψε: >> Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: >>> Ha, ha ha! >>> I'm safe now!! >>> >>> No breaks in this time! >> >> You just can't help yourself, can you? I predict your database will >> be broken in, within a week, after which you will plug one leak >> and after an other day boast again about how secure your system is, >> because you hadn't had a break in after your latest "fix". >> > > It won't break again. 'page' variable cannot be manipulated by > arbitrary url strings no more. So you fixed one specific leak and you think that is enough to declare yourself safe?! > This time is fixed for good. The fact that you said this before and were wrong didn't teach you anything? > Your predictions are wrong. And you wonder why people think you are arrogant. You are a perfect example of the arrogance of the ignorant. -- Antoon Pardon.
[toc] | [prev] | [next] | [standalone]
| From | Ned Batchelder <ned@nedbatchelder.com> |
|---|---|
| Date | 2013-11-10 08:15 -0800 |
| Message-ID | <70f6852d-d157-4f0f-8ae4-dd48d5768ff1@googlegroups.com> |
| In reply to | #59014 |
On Sunday, November 10, 2013 10:28:46 AM UTC-5, Antoon Pardon wrote: > Op 10-11-13 16:01, Νίκος Αλεξόπουλος schreef: > > Στις 10/11/2013 3:49 μμ, ο/η Antoon Pardon έγραψε: > >> Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: > >>> Ha, ha ha! > >>> I'm safe now!! > >>> > >>> No breaks in this time! > >> > >> You just can't help yourself, can you? I predict your database will > >> be broken in, within a week, after which you will plug one leak > >> and after an other day boast again about how secure your system is, > >> because you hadn't had a break in after your latest "fix". > >> > > > > It won't break again. 'page' variable cannot be manipulated by > > arbitrary url strings no more. > > So you fixed one specific leak and you think that is enough to > declare yourself safe?! > > > This time is fixed for good. > > The fact that you said this before and were wrong didn't teach > you anything? > > > Your predictions are wrong. > > And you wonder why people think you are arrogant. You are a perfect > example of the arrogance of the ignorant. > > -- > Antoon Pardon. Can we please just ignore Nikos' boasts? The only way to end a Nikos thread is to ignore Nikos. At this point, Mark and Antoon are as much of a problem as Nikos is. Continuing to insult and bait Nikos just prolongs the noise. Yes, we know he is wrong. But no amount of "nyah-nyah" posts is going to convince him. We have to settle for an end to the thread. --Ned.
[toc] | [prev] | [next] | [standalone]
| From | Antoon Pardon <antoon.pardon@rece.vub.ac.be> |
|---|---|
| Date | 2013-11-10 20:13 +0100 |
| Message-ID | <mailman.2349.1384113731.18130.python-list@python.org> |
| In reply to | #59015 |
Op 10-11-13 17:15, Ned Batchelder schreef: > On Sunday, November 10, 2013 10:28:46 AM UTC-5, Antoon Pardon wrote: >> Op 10-11-13 16:01, Νίκος Αλεξόπουλος schreef: >>> Στις 10/11/2013 3:49 μμ, ο/η Antoon Pardon έγραψε: >>>> Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: >>>>> Ha, ha ha! >>>>> I'm safe now!! >>>>> >>>>> No breaks in this time! >>>> >>>> You just can't help yourself, can you? I predict your database will >>>> be broken in, within a week, after which you will plug one leak >>>> and after an other day boast again about how secure your system is, >>>> because you hadn't had a break in after your latest "fix". >>>> >>> >>> It won't break again. 'page' variable cannot be manipulated by >>> arbitrary url strings no more. >> >> So you fixed one specific leak and you think that is enough to >> declare yourself safe?! >> >>> This time is fixed for good. >> >> The fact that you said this before and were wrong didn't teach >> you anything? >> >>> Your predictions are wrong. >> >> And you wonder why people think you are arrogant. You are a perfect >> example of the arrogance of the ignorant. >> >> -- >> Antoon Pardon. > > > Can we please just ignore Nikos' boasts? When I'm bored with them. I don't understand why you suddenly complain. This whole thread started with what amounts to a boast. So why wait four days before you ask for them to be ignored. > The only way to end a Nikos thread is to ignore Nikos. At this point, > Mark and Antoon are as much of a problem as Nikos is. Continuing to > insult and bait Nikos just prolongs the noise. Yes, we know he is wrong. > But no amount of "nyah-nyah" posts is going to convince him. We have to > settle for an end to the thread. This much we new when the thread started. Thus IMO all those that reacted and blew life into this thread are to blame that it could flourish. But it seemed they were having their fun. So why shouldn't I have my fun now? They were a problem then, I am a problem now, that seems perfectly fair. -- Antoon Pardon
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-10 19:58 +0200 |
| Message-ID | <l5ohgh$lus$1@dont-email.me> |
| In reply to | #59014 |
Στις 10/11/2013 5:28 μμ, ο/η Antoon Pardon έγραψε: > Op 10-11-13 16:01, Νίκος Αλεξόπουλος schreef: >> Στις 10/11/2013 3:49 μμ, ο/η Antoon Pardon έγραψε: >>> Op 10-11-13 11:32, Νίκος Αλεξόπουλος schreef: >>>> Ha, ha ha! >>>> I'm safe now!! >>>> >>>> No breaks in this time! >>> >>> You just can't help yourself, can you? I predict your database will >>> be broken in, within a week, after which you will plug one leak >>> and after an other day boast again about how secure your system is, >>> because you hadn't had a break in after your latest "fix". >>> >> >> It won't break again. 'page' variable cannot be manipulated by >> arbitrary url strings no more. > > So you fixed one specific leak and you think that is enough to > declare yourself safe?! > >> This time is fixed for good. > > The fact that you said this before and were wrong didn't teach > you anything? > >> Your predictions are wrong. > > And you wonder why people think you are arrogant. You are a perfect > example of the arrogance of the ignorant. > Really? I have even pasted the code as i used to had it and the new correction i have made. Since my code is so crappy try to mess with the script and databases since you re so competent and smart
[toc] | [prev] | [next] | [standalone]
| From | Petite Abeille <petite.abeille@gmail.com> |
|---|---|
| Date | 2013-11-10 18:57 +0100 |
| Message-ID | <mailman.2341.1384106504.18130.python-list@python.org> |
| In reply to | #59010 |
On Nov 10, 2013, at 4:28 PM, Antoon Pardon <antoon.pardon@rece.vub.ac.be> wrote: > You are a perfect example of the arrogance of the ignorant. Finally! The Dunning–Kruger effect proven beyond a doubt.
[toc] | [prev] | [next] | [standalone]
| From | Νίκος Αλεξόπουλος <nikos.gr33k@gmail.com> |
|---|---|
| Date | 2013-11-10 20:46 +0200 |
| Message-ID | <l5okal$91s$1@dont-email.me> |
| In reply to | #59019 |
Στις 10/11/2013 7:57 μμ, ο/η Petite Abeille έγραψε: > > On Nov 10, 2013, at 4:28 PM, Antoon Pardon <antoon.pardon@rece.vub.ac.be> wrote: > >> You are a perfect example of the arrogance of the ignorant. > > Finally! The Dunning–Kruger effect proven beyond a doubt. > > You are a moron, no doubt! Freddy Kruger Effect!
[toc] | [prev] | [next] | [standalone]
Page 10 of 11 — ← Prev page 1 … 8 9 [10] 11 Next page →
Back to top | Article view | comp.lang.python
csiph-web