07-09-2004
Quote:
The SCO Security Server, an add-on product for SCO OpenServer 3 and SCO OpenServer 5, supports Kerberos V5 authentication. This product cannot be configured to be Kerberos V4 compatible; therefore, it is not vulnerable.
Found on
Cert advisory CA-1996-03
This would seem to imply that unless you have/get the add-on product, you can't do Kerberos V5(or any other) support which is why your ftp is failing.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a system here running "SCO UNIX System V/386, Release 3.2" I'm not sure if someone has changed anything, but all of the sudden I get constant scrolling errors...
"*** /etc/getty ttyr006 m (CURRENT TIME/DATE):
Cannot open line ttyr006: No such device or address (error 6)"
this... (0 Replies)
Discussion started by: PBNOSGT
0 Replies
2. UNIX for Advanced & Expert Users
Hi friends,
i am getting the following error while booting my system which has SCo UNIX .
=========================
H iinit
PANIC: srmountfun-Error 22
mounting of rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages.
Dump not completed.
safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies
3. UNIX for Dummies Questions & Answers
I am trying to start an FTP session from my UNIX PC to a PC running XP.
I aim to run a cron to manipulate remote files on the Windows M/C.
I cannot connect to the Windows M/C when i start rthe FTP session on the UNIX box. I can do it fine the other way round.
I have set entries in /etc/hosts... (2 Replies)
Discussion started by: farmacy
2 Replies
4. UNIX for Dummies Questions & Answers
Hi all.
I'm pretty new to this forum,hope a good time here.
issue is that
I have a SCO UNIX 5.0.5 installed on the virtual machine VMware. Configured the NIC and assigned 192.168.18.254 as it's IP,and the host OS windows XP 's IP is 192.168.18.8 ,both of them can PING each other... (4 Replies)
Discussion started by: blf0
4 Replies
5. UNIX for Dummies Questions & Answers
my problem is like this
while ftping locally it works,
but when users from WAN try the ftp services it doesnt comes
the message it displays is as follows "connection closed by remote host "
please help
Thanks (5 Replies)
Discussion started by: Athos19
5 Replies
6. Solaris
I'm using proftpd to manage my ftp/sftp connections but would like to use RBAC to only allow ftp/sftp connections. Has anyone done this or can point me in the right direction? This is my first experience trying to use RBAC. Thanks in advance. (2 Replies)
Discussion started by: toor13
2 Replies
7. SCO
hi,
i am working on sco unix 5.07, i have 10 individual servers networked locally in which sco os is installed. one of them is not transferring the file to other servers but accepting all files. means Server (A) can accept the file through FTP from any server but not transferring FTP its own... (9 Replies)
Discussion started by: aafflatoon
9 Replies
8. Shell Programming and Scripting
Hello,
I'm a UNIX SysAdmin at a large webhosting company and we have a vendor that provides a service which involves the ftp'ing of files from their servers to ours. They initiate FTP using a perl script with NET::FTP.
When they try to transfer files (and delete files over ftp), there is... (3 Replies)
Discussion started by: tmmgeekette
3 Replies
9. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
10. SCO
i have installed and working FTP Server With SCO 5.05.
But i need solve problem related to config, like proftpd (i not have installed proftpd)
the recomendation on client site is enable port 113 related to inetd. but i need solve it on server side, like proftpd.conf:
DefaultRoot ~... (9 Replies)
Discussion started by: Arcanisgk
9 Replies
LEARN ABOUT MOJAVE
productsign
productsign(1) BSD General Commands Manual productsign(1)
NAME
productsign -- Sign an OS X Installer product archive
SYNOPSIS
productsign [options] --sign identity input-product-path output-product-path
DESCRIPTION
productsign adds a digital signature to a product archive previously created with productbuild(1). Although you can add a digital signature
at the time you run productbuild(1), you may wish to add a signature later, once the product archive has been tested and is ready to deploy.
If you run productsign on a product archive that was previously signed, the existing signature will be replaced.
To sign a product archive, you will need to have a certificate and corresponding private key -- together called an ``identity'' -- in one of
your accessible keychains. To add a signature, specify the name of the identity using the --sign option. The identity's name is the same as
the ``Common Name'' of the certificate.
If you want to search for the identity in a specific keychain, specify the path to the keychain file using the --keychain option. Otherwise,
the default keychain search path is used.
productsign will embed the signing certificate in the product archive, as well as any intermediate certificates that are found in the key-
chain. If you need to embed additional certificates to form a chain of trust between the signing certificate and a trusted root certificate
on the system, use the --cert option to give the Common Name of the intermediate certificate. Multiple --cert options may be used to embed
multiple intermediate certificates.
The signature can optionally include a trusted timestamp. This is enabled by default when signing with a Developer ID identity, but it can be
enabled explicitly using the --timestamp option. A timestamp server must be contacted to embed a trusted timestamp. If you aren't connected
to the Internet, you can use --timestamp=none to disable timestamps, even for a Developer ID identity.
ARGUMENTS AND OPTIONS
--sign identity-name
The name of the identity to use for signing the product archive.
--keychain keychain-path
Specify a specific keychain to search for the signing identity.
--cert certificate-name
Specify an intermediate certificate to be embedded in the product archive.
--timestamp
Include a trusted timestamp with the signature.
--timestamp=none
Disable trusted timestamp, regardless of identity.
input-product-path
The product archive to be signed.
output-product-path
The path to which the signed product archive will be written. Must not be the same as input-product-path.
SEE ALSO
productbuild(1)
Mac OS September 15, 2010 Mac OS