You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Spike.md 5.0 KiB

3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. In 1997 a user by the name of Spike arrived on Redbrick. This writer
  2. cannot remember how Spike came to be on Redbrick for he was not, nor
  3. ever had been a student, but someone gave him a password and he was one
  4. of the best known Redbrick personalities and a
  5. [Table](/Table "wikilink") regular.
  6. Spike merits an entry in the [Encyclopedia](/Encyclopedia "wikilink")
  7. for the confused events surrounding his permanent
  8. [disuserment](/DAFT "wikilink") and the shutting down of Redbrick. What
  9. is beyond question is that Spike hacked files in other colleges,
  10. allegedly TCD and Glasgow. His carrying out of this deed was traced back
  11. to his Redbrick account and great was the wrath and anger of CSD who
  12. pulled the plug on Redbrick and threatened to close it down. As it was
  13. the system was shut down for three weeks and restored only with several
  14. conditions.
  15. The exact series of events has always been a bone of contention with
  16. Spike claiming that it wasn\'t all his fault, a stance for which there
  17. was some support, and others claiming that he was solely responsible. As
  18. a result Spike was banned from Redbrick and DCU\'s environs by the
  19. [Committee](/Committee "wikilink").
  20. At the time there was a great deal of anger towards Spike among the
  21. membership but time has healed many wounds though his name is still
  22. cursed by some of the older members.
  23. \--Cain
  24. ---
  25. In 2011, Spike became a DCU student and subsequently joined Redbrick as
  26. a member, with the username dilligaf. When the committee discovered who
  27. dilligaf was they held a meeting to decide whether he should be allowed
  28. to remain a member. At the end of the meeting it was decided that
  29. dilligaf/spike could stay on as a member.
  30. In December 2011, dilligaf changed his username to shaun.
  31. ---
  32. Singer kept a post from wibble from back in the day (well, over a year
  33. later, actually, but closer than today) when all this was happening, so
  34. here it is, in its entirety.
  35. Newsgroups: redbrick.babble
  36. Subject: Re: Encyclopaedia, with missing facts...
  37. Date: 24 Nov 1999 22:07:46 GMT
  38. Organization: DCU Networking Society
  39. Distribution: local
  40. NNTP-Posting-Host: enigma.redbrick.dcu.ie
  41. X-Trace: enigma.redbrick.dcu.ie 943481266 73677 136.206.15.5 (24 Nov 1999 22:07:46 GMT)
  42. X-Complaints-To: committee@redbrick.dcu.ie
  43. NNTP-Posting-Date: 24 Nov 1999 22:07:46 GMT
  44. User-Agent: slrn/0.9.5.7 (UNIX)
  45. Xref: enigma.redbrick.dcu.ie redbrick.babble:4852
  46. On 22 Nov 1999 10:31:02 GMT, <wishkah@RedBrick.DCU.IE> wrote:
  47. From: Shaun Neary <velocity@oceanfree.net>
  48. >>Spike merits an entry in the Encyclopedia for the confused events surrounding
  49. >>his permanent disuserment and the shutting down of Redbrick. What is beyond
  50. >>question is that Spike hacked files in other colleges, ...
  51. >
  52. >Schnipped I was busted with a password file on a glasgow account, which was
  53. >actually granted to me as I was doing work on their site. So again, yet
  54. >another cockup on your story.
  55. Shaun Neary was found with a cracked version of the password file belonging
  56. to a TCD server. I'm not totally sure how he was tracked down but it came
  57. from the fact that he was trading cracked passwords on IRC and somebody in
  58. TCD heard about him, traced his logins back to Glasgow, whose admins went
  59. ballistic they had somebody like him on their systems. They were upset at
  60. being accused of harbouring a hacker and traced his logins back to DCU
  61. whose admins (CSD) went ballastic in turn. Initally CSD didn't have a Shaun
  62. Neary on their books and believed it to be an alias for another well-known
  63. redbrick user. I recall setting them straight on this fact (otheriwse that
  64. innocent student could have been kicked out of DCU) and disusered Spike.
  65. >>allegedly TCD and Glasgow. His carrying out of this deed was traced back to
  66. >>his Redbrick account and great was the wrath and anger of CSD who pulled the
  67. >>plug on Redbrick and threatened to close it down. As it was the system was
  68. >>shut down for three weeks and restored only with several conditions.
  69. >
  70. >Actually reliable resources point to the fact that it was electricians that
  71. >cocked up and CSD shut down the wrong section down (CS labs) which shut down
  72. >mother for a while, This was confirmed by Andy Lundberg himself. So fucking
  73. >print that as well while you're at it..
  74. Total bullshit... as you're expect from Shaun! Redbrick servers weren't
  75. powered off during the "spike" incident, it's network access was cut. In
  76. fact all out-bound telnet access from DCU was cut if I recall correctly.
  77. Redbrick was previously abruptly powered down (un-plugged) at a different
  78. time due to suspected "lab room exam cheating" via our chat system, and the
  79. fact that CSD couldn't contact an admin@redbrick to do the job for them,
  80. and they hadn't any account with sufficent privledges on redbrick to
  81. shutdown the system properly.
  82. Just setting some facts straight :]
  83. Wibble
  84. \--Emperor
  85. Originally from the [Encyclopedia](/Encyclopedia "wikilink")
  86. [Category:Encyclopedia](/Category:Encyclopedia "wikilink")