Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Motorola 6300 Workstation - root password hacking?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Motorola 6300 Workstation - root password hacking?

    Someone (frankhintsch) in Germany has a working Motorola 6300 Unix workstation. And he don't remember the root password. How to get in?

    He has a manual which also talks about single mode bootup. But nobody knows how to start single mode. And it looks like that even in single mode it requests for the root password.

    Any hints? See more details, photos and manual scans here: http://forum.classic-computing.de/in...ction=firstNew

    The only current hopely working idea is to raw read the ST-506 (MFM) harddisk with an MFM/Drive reader/emulator ( see here ) and trying to decode the disk and hoping to find the passort (crypted or uncrypted) in /etc/passwd or /etc/shadow (and probably decrypt it with speed of a modern PC).

    What do you think?
    <album>

    #2
    RetroHacker_ and I did something similar with a large lot of UNIX machines from the same owner. We found one that had a SCSI hard disk and cracked the root password from /etc/passwd. It was running an old version of SunOS, which was limited to 3des password encryption, and 8 character passwords. Using some educated tuning with John the Ripper, we retrieved the root password in an afternoon on an dual-core i5 laptop running Linux, and the rest of the accounts within a few days. The previous owner had used the same root password on all of his systems, so we were able to get the original installs of various OSes up and going.

    Something to consider: if the machine has Ethernet and will come up (but can't be logged in to), it's worthwhile to see what services are running. There's a good chance something will be misconfigured and/or have known vulnerabilities that can be exploited. For instance, sufficiently old SunOS has a vulnerability in the rlogin system that completely compromises the machine, and rlogin is almost always running.
    Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

    Comment


      #3
      Single user mode is typically entered by telling the system to reboot directly into single user mode, so you'd need to be able to boot it up in the first place.
      On the other hand, if you can cause a disk failure that prevents it from going into user mode or network mode, it should halt in single user mode and ask you to fix the problem. Caveat here is that you're usually also in a read only mode.

      If it is booting up all the way, it would be a good idea to scan it, like Glitch mentioned. The server is likely to have several exploitable issues from that era.

      There are 2 methods that I would have used in the days before breaking the boot sequence was common. First, boot off installation media and escape to the shell, then mount the boot disk and either add a user with a known password hash and UID 0, or modify the root user's password hash to one that was known. You can do this with any editor and not have to rely on the passwd utility targeting the right password file. The second method would have been to install the drive as a secondary in another system and mount and modify the password file as above.

      Comment


        #4
        Would it be possible to connect the Hard Drive to a Linux Box or a USB to IDE adapter and read the contexts of the Hard Drive to an Image file
        using Linux's DD command? That would simply make an Image that could be mounted in Linux.

        dd if=<source> of=<target> bs=<byte size> ("USUALLY" some power of 2, and usually not less than 512 bytes.) skip= seek= conv=<conversion>

        Larry

        Comment


          #5
          OP says it's MFM, so no -- MFM drives are tied to the controller they're formatted with, unless you have one of the (mentioned above) modern "attempt to read MFM" solutions.
          Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

          Comment


            #6
            Just for your reference. The reading of the MFM harddisk with the MFM/Drive reader/emulator was successfull, the /etc/passwd file could be located and the root's password hash has been found. One of the members of the forum got the password out of the hash in 10 minutes, the owner himself needed about 6 hours but the result was the same, and it was working.
            <album>

            Comment


              #7
              Excellent news!
              Check out The Glitch Works | My Retro Projects | Vintage Computer Services | Glitch Works Tindie Store -- Vintage Computer Kits and More

              Comment


                #8
                Originally posted by 1ST1 View Post
                Just for your reference. The reading of the MFM harddisk with the MFM/Drive reader/emulator was successfull, the /etc/passwd file could be located and the root's password hash has been found. One of the members of the forum got the password out of the hash in 10 minutes, the owner himself needed about 6 hours but the result was the same, and it was working.
                was it running Motorola System V?

                Comment


                  #9
                  Originally posted by Al Kossow View Post
                  was it running Motorola System V?
                  The complete title is

                  Motorola Information Systems
                  S6300 AND S6350 UNIX-Derived Operating System
                  Revision FE07A
                  September 25, 1985
                  This is a System V.2

                  Comment


                    #10
                    Originally posted by Al Kossow View Post
                    was it running Motorola System V?
                    The official title is

                    Motorola Information Systems
                    SOFTI'IARE RELEASE GUIDE FOR
                    56300 AND S6350 UNIX-Derived Operating System
                    Revision FE07A: September 25, 1985

                    Comment


                      #11
                      I save the manuals, roms and the mfm-image made by the owner at http://oldcomputers.dyndns.org/publi...ies/index.html
                      Last edited by fritzeflink; September 8, 2017, 02:51 AM.

                      Comment

                      Working...
                      X