11-29-2008
Quote:
Originally Posted by
Perderabo
You will need bootable media that was used to install the os or that came with the os. The problem you will have is that your file system may not be readable by any other os. Attaching the HD to another box might be worth a try though. If you get access to shadow file, you will be able to read and write to it. Just remove the encrypted password. Or copy the encrypted password from the account whose password you know. If you give JtR, say, 500 passwords, it can quickly break a few most of the time. But if your root password is a good one, it can take many weeks.
Can't the guy who sold you the system tell you the password?
The seller is just a surplus dealer. He does not know what the unix is. Also he dont know (dont tell) the real prev user.
So I dont have any bootable media, and to hook HDD on another box looks the best option. Do you think a current Linux'es would be able to talk to Sys5 UNIX file system?
I'm still not sure if UNIX uses some encrypted files or general? Means If I would have same OS loaded on another box would I be able to read files from new hooked HDD?
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
My root password for mysql has some problem as it dosent allow me to login....
all commands to reset it failed. so I removed mysql
yum remove mysql
and installed it by
yum install mysql mysql-devel mysql-server
and it installed fine
I gave chkconfig --levels 235 mysqld on... (1 Reply)
Discussion started by: viji19812001
1 Replies
2. UNIX for Advanced & Expert Users
How to change the ldap root password.
I have generated the password by using "slappasswd " command, but In my root machine "/etc/ldap/sldap.d" file is not there. instead of the file sldap.d directory only is there. please help me...? (0 Replies)
Discussion started by: ungalnanban
0 Replies
3. Red Hat
I need some help with Fedora. I am trying to reset the root password. When I tried to login I was not able to. I kept getting the authentication failure message. I got the password reset success message.
passwd: all authentication tokens updated successfully.
I then thought maybe the root... (6 Replies)
Discussion started by: cokedude
6 Replies
4. Emergency UNIX and Linux Support
Hi All,
I'm stuck in a severe problem here , Someone have changed the root password
and he cannot remember it and there is no other user privileged user on the system , But I do have access to a non privileged user.
On the top of the system an application which requires a theoretical ... (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies
5. Solaris
Hello, I have two old Solaris machines
$ uname -a
SunOS unknown 5.8 Generic_117350-39 sun4u sparc SUNW,UltraAX-e2
unfortunately, it has been so long ago that i have used these that the root password has left my head...
i can log into one of the machine as a normal user, but am unable to... (4 Replies)
Discussion started by: Norman Khine
4 Replies
6. Solaris
Hi All,
I just found one thread on this forum on this subject here:
Forgot MYSQL password root | Unix Linux Forums | Web Development
but unfortunately the issue was not resolved.
I have the same problem with the same error message.
The background is that I built a Solaris 11 x86 server... (11 Replies)
Discussion started by: hicksd8
11 Replies
7. UNIX for Advanced & Expert Users
we have NCR 3455 system from long time as attached all information for server (images) , so we need your help to assist us to get root password which lost it , really we appreciate your efforts if you can send us the procedure for resting the administrator (root) password which this server... (0 Replies)
Discussion started by: univoip
0 Replies
8. UNIX for Beginners Questions & Answers
Hi ,
I ve a question about the Linux system root password change.
Which can be done using grub menu without inputting the old password.:confused:
So If anybody can change the root password without any password and then how it is secure. Anybody can manipulate the other user using the... (6 Replies)
Discussion started by: pradyumnajpn10
6 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)