The Basics of Hacking III


SUBMITTED BY: nationalsun

DATE: Nov. 8, 2017, 7:02 a.m.

FORMAT: Text only

SIZE: 4.3 kB

HITS: 587

  1. ****************************************************************************** ** The basics of hacking iii: data **
  2. ******************************************************************************
  3. Welcome to the basics of hacking iii: data general computers. Data general is
  4. favored by large corporations who need to have a lot of data on-line. The data
  5. general aos, which stands for advanced operating system, is a version of
  6. bastardized unix. All the commands which were in the unix article, will work
  7. on a data general. Once again, we have the problem of not knowing the format
  8. for the login name on the data general you want to hack. As seems to be
  9. standard, try names from one to 8 digits long. Data general designed the
  10. computer to be for busi- nessmen, and is thus very simplistic, and basically
  11. fool proof (but not damn fool proof). It follows the same login format as the
  12. unix system: dg=> login: you=> username dg=> password: you=> password passwords
  13. can be a maximum of 8 characters, and they are almost always set to a default
  14. of 'aos' or 'dg'. (Any you know about businessmen...) A word about control
  15. characters: cntrl-o stops massive print-outs to the screen, but leaves you in
  16. whatever mode you were. (A technical word on what this actually does: it
  17. tells the cpu to ignore the terminal, and prints everything out to the cpu!
  18. This is about 19200 baud, and so it seems like it just cancels.) Cntrl-u
  19. kills the line you are typing at the time. Now for the weird one: cntrl-c
  20. tells the cpu to stop, and wait for another cntrl character. To stop a
  21. program, you actually need to type cntrl-c and then a cntrl-b. Once you get on,
  22. type 'help'. Many dg (data general) computers are sold in a package deal,
  23. which also gets the company free customizing. So you never know what commands
  24. there might be. So we will follow what is known as the 'eclipse standard', or
  25. what it comes out of the factory like. To find out the files on the directory
  26. you are using, type => dir to run a program, just like on a dec, just type its
  27. name. Other than this, and running other people's programs, there really isn't
  28. a standard... *** Hark, yon other system users *** to see who is on, type =>
  29. who (and a lot of the other unix commands, remember?). This shows the other
  30. users, what they are doing, and what paths they are connected across. This is
  31. handy, so try a few of those paths yourself. To send a message, say => send
  32. username this is a one time message, just like send on the dec 10. From here
  33. on, try commands from the other previous files and from the 'help' listing.
  34. Superuser: if you can get privs, just say: => superuser on and you turn those
  35. privs on! By the way, you remember that computers keep a log of what people do?
  36. Type: => syslog /stop and it no longer records anything you do on the system,
  37. or any of the other users. It screams to high heaven that it was you who turned it off, but it keeps no track of any accounts created or whatever else
  38. you may do. You can say=> syslog /start to turn it back on (now why would
  39. you want to do something like that?????) To exit from the system, type=> bye
  40. and the system will hang up on you.
  41. Most of the systems around, including decs, vax's, and dg's, have games. These
  42. are usually located in a path or directory of the name games or <games> or
  43. games: try looking in them, and you may find some trek games, adventure, zork,
  44. wumpus (with bent arrows in hand) or a multitude of others. There may also be
  45. games called 'cb' or 'forum'. These are a sort of computer conference call.
  46. Use them on weekends, and you can meet all sorts of interesting people.
  47. *************************************** ***************************************
  48. If you would like to see more articles on hacking (this time far more than jus
  49. t
  50. the basics), or maybe articles on networks and such, then leave us mail if we
  51. are on the system, or have the sysop search us down. We call a lot of places,
  52. and you may just find us.
  53. This completes the series of articles
  54. on hacking... These articles were: the basics of hacking: introduction the
  55. basics of hacking i: dec's the basics of hacking ii: vax's (unix) the basics of
  56. hacking iii: dg's
  57. This and the previous articles by: the
  58. Knights of Shadow
  59. [end] 1984
  60. 

comments powered by Disqus