06-10-2016
Vendor root access
All,
I wanted to get others opinions on providing root access to vendors. I have a vendor that is claiming to need full root sudo access to complete a one time system set up for their software. The system is on our corporate network and we never provide this level of access. Not only that, they want to do the install remotely.
We all know that the claim to need the full root sudo access is complete BS since they only need the sudo access to do what needs to be done. However they claim that there is too much involved to not have full access.
What are your thoughts? Have there been situations in your environments when you've provided full root sudo access? If so, did you take certain precautions (remove from corporate network, have one of your team sit with them, etc)?
I really appreciate any thoughts on the subject..
TIA,
Herb
10 More Discussions You Might Find Interesting
1. Linux
wish to know how to access root password it root password is forgotten in linux (1 Reply)
Discussion started by: wojtyla
1 Replies
2. SCO
We have SCO 5.0.5 and can't log into system as "root". The system indicates the password is incorrect. No one knows what happened.
How can we resolve this issue.. Are there files we can restore from backup...?
Any suggestions would be appreciated.
Thank you.. (2 Replies)
Discussion started by: RBurer
2 Replies
3. Shell Programming and Scripting
Hi,
I just wanted to know to what files root does not have access, not even read....I read that .profile for any user is the only file which root cannot access is it true..??...If we have to use passwords and ID's in a script can we use them in .profile and call them as parameters..???
... (3 Replies)
Discussion started by: mgirinath
3 Replies
4. Solaris
Hi,
The security auditor give a this statement , what to do ?
On my solaris system (S10)
"The User ID "root" should not be used on the system - the su and
the priviledged account should be used from each administrator for
accountability purposes"
What to do ? (3 Replies)
Discussion started by: falcon16
3 Replies
5. AIX
Hello
I have a question.
I have a box with Aix 5.3 but I want to disable root access direct from any terminal or console. I mean If I want to login to 10.10.10.10
login:root
password *********
Root access is not permited
Which file I have to edit. to the users first login with... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies
6. UNIX for Dummies Questions & Answers
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Discussion started by: suryashikha
5 Replies
7. Shell Programming and Scripting
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
Discussion started by: adisky123
4 Replies
8. SuSE
I access over 100 SUSE SLES servers as root from my admin server, via ssh sessions using ssh keys, so I don't have to enter a password. My SUSE Admin server is setup in the following manner:
1) Remote root access is turned off in the sshd_config file.
2) I am the only user of this admin... (6 Replies)
Discussion started by: dvbell
6 Replies
9. Ubuntu
We are having a little problem on a server. We want that some users should be able to do e.g. sudo and become root, but with the restriction that the user can't change root password. That is, a guarantee that we still can login to that server and become root no matter of what the other users will... (2 Replies)
Discussion started by: 244an
2 Replies
10. OS X (Apple)
Mac users...
I updated this MBP from OSX 10.12.1 to the brand new OSX 10.12.2 two days ago.
A week ago I installed the Xcode suite.
Now the QT shell audio capture in another recent thread is broken when exporting a file.
It gives an error in a window, paraphrasing, The action is not... (4 Replies)
Discussion started by: wisecracker
4 Replies
LEARN ABOUT HPUX
gvid_no_claim_dev
gvid_no_claim_dev(5) File Formats Manual gvid_no_claim_dev(5)
NAME
gvid_no_claim_dev - PCI Vendor/Device ID that the gvid graphics driver will not claim
VALUES
Failsafe
Default
Allowed values
Recommended values
Specific to the device you wish to prevent from claiming.
DESCRIPTION
This tunable specifies the PCI Vendor ID and/or Device ID of a graphics device that the HP graphics driver should not claim.
The graphics driver was designed to be a general purpose driver for all PCI graphics cards. As a result, the driver will attempt to claim
any PCI graphics display device found on the system. This can be a problem for graphics device developers who need their own graphics
driver to claim their own graphics device.
The value of will specify a PCI Vendor ID and/or Device ID of a graphics card that the gvid graphics driver should not claim. It is a 32
bit number, with the upper 16 bits containing the PCI Vendor ID and the lower 16 bits containing the PCI Device ID. Either the Vendor ID
or Device ID can use a wildcard value of
For example, if is set to the value the driver will ignore graphics devices with a PCI Vendor ID of and a Device ID of If is set to the
driver will not claim any graphics cards with a Vendor ID of regardless of the Device ID.
Who Is Expected to Change This Tunable?
Anyone who wishes the graphics driver to ignore a specific graphics device. This will typically be someone writing their own graphics
driver for their own hardware.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
Tunable Kernel Parameters gvid_no_claim_dev(5)