Sponsored Content
Operating Systems OS X (Apple) If you run macOS High Sierra version 10.13.1, be sure to install today's update. Post 303008348 by drl on Thursday 30th of November 2017 12:04:38 PM
Old 11-30-2017
Hi.

The macOS box I use is not physically accessible to anyone else. I was concerned that ssh access might allow the bug, so I tried it, and I failed to gain access.

In addition, have a root password, so I was not concerned about the bug, but it leaves me a little less trusting of Apple ... cheers, drl
Code:
OS, ker|rel, machine: Apple/BSD, Darwin 17.2.0, x86_64
Distribution        : macOS 10.13.1 (17B1003), High Sierra

 

7 More Discussions You Might Find Interesting

1. Solaris

After update Solaris version, HBA driver still need to install?

Hi all I had update a server from Solaris 8 to Solaris 10 is it the HBA driver still need to reinstall? since i can get the driver info as below: root@sgerpdev # fcinfo hba-port HBA Port WWN: 21000003ba9b58a3 OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. ... (1 Reply)
Discussion started by: SmartAntz
1 Replies

2. Solaris

Install update 6 on solaris with update 3

I want to update my solaris 10 server which is currently on update 3 stage. A new application require it to be on update 6. What is the best way to make it update 6. should i just install the patch or should i go for the liveupgrade?? thanks for you help in advance (3 Replies)
Discussion started by: uxravi
3 Replies

3. UNIX for Beginners Questions & Answers

Capture power button press on MacOs High Sierra?

Hello everyone! I'm developing a MacOs Application in python and I'm having some issues trying to find information related to the power button pressed event. I know that in Ubuntu 14.04 you can find information about it on the acpi folders, but I realized that here in Mac that process is... (0 Replies)
Discussion started by: xedge
0 Replies

4. UNIX for Beginners Questions & Answers

When I run the code yesterday I am getting output,when I run same code today I am getting error?

If run the below code today its creating all directory and getting output files,I f run same code tomorrow I am getting error. can any one give suggestion to sortout this error. OSError: no such file or directory : '062518'My code looks like this import paramiko import sys import os ... (8 Replies)
Discussion started by: haribabu2229
8 Replies

5. Shell Programming and Scripting

Issue with pwd for script run by double click on script (MacOS High SIerra)

Hello, I have the following script that just archives and clears some log files. #!/bin/bash # script: archive_logs_and_clear # add date to logfile names and copy archive directory # clear logs # change to script directory cd ... (4 Replies)
Discussion started by: LMHmedchem
4 Replies

6. Shell Programming and Scripting

Terminal running bash/rsync script does not close with exit (MacOS High SIerra)

Hello, I am running a bash script to do an rsync back on a computer running MacOS High Sierra. This is the script I am using, #!/bin/bash # main backup location, trailing slash included backup_loc="/Volumes/Archive_Volume/00_macos_backup/" # generic backup function function backup {... (12 Replies)
Discussion started by: LMHmedchem
12 Replies

7. Shell Programming and Scripting

Issue with shutdown command in script (MacOS High Sierra)

Hello, I have a backup script that runs an rsync backup to an external drive. I use the script frequently on Windows and Linux and have installed it on a Mac. The script has an option to run shutdown after the backup has completed. Since backup can take hours to run, this is an option that is... (10 Replies)
Discussion started by: LMHmedchem
10 Replies
client.conf(5)							    Apple Inc.							    client.conf(5)

NAME
client.conf - client configuration file for cups DESCRIPTION
The client.conf file configures the CUPS client and is normally located in the /etc/cups and/or ~/.cups directories. Each line in the file can be a configuration directive, a blank line, or a comment. Comment lines start with the # character. Note: Starting with macOS 10.7, this file is only used by command-line and X11 applications plus the IPP backend. The ServerName directive is not supported on macOS at all. Starting with macOS 10.12, all applications can access these settings in the /Library/Prefer- ences/org.cups.PrintingPrefs.plist file instead. See the NOTES section below for more information. DIRECTIVES The following directives are understood by the client. Consult the online help for detailed descriptions: AllowAnyRoot Yes AllowAnyRoot No Specifies whether to allow TLS with certificates that have not been signed by a trusted Certificate Authority. The default is "Yes". AllowExpiredCerts Yes AllowExpiredCerts No Specifies whether to allow TLS with expired certificates. The default is "No". Encryption IfRequested Encryption Never Encryption Required Specifies the level of encryption that should be used. GSSServiceName name Specifies the Kerberos service name that is used for authentication, typically "host", "http", or "ipp". CUPS adds the remote host- name ("name@server.example.com") for you. The default name is "http". ServerName hostname-or-ip-address[:port] ServerName /domain/socket Specifies the address and optionally the port to use when connecting to the server. Note: This directive is not supported on macOS 10.7 or later. ServerName hostname-or-ip-address[:port]/version=1.1 Specifies the address and optionally the port to use when connecting to a server running CUPS 1.3.12 and earlier. SSLOptions [AllowDH] [AllowRC4] [AllowSSL3] [DenyCBC] [DenyTLS1.0] SSLOptions None Sets encryption options (only in /etc/cups/client.conf). By default, CUPS only supports encryption using TLS v1.0 or higher using known secure cipher suites. Security is reduced when Allow options are used. Security is enhanced when Deny options are used. The AllowDH option enables cipher suites using plain Diffie-Hellman key negotiation (not supported on systems using GNU TLS). The AllowRC4 option enables the 128-bit RC4 cipher suites, which are required for some older clients. The AllowSSL3 option enables SSL v3.0, which is required for some older clients that do not support TLS v1.0. The DenyCBC option disables all CBC cipher suites. The DenyTLS1.0 option disables TLS v1.0 support - this sets the minimum protocol version to TLS v1.1. TrustOnFirstUse Yes TrustOnFirstUse No Specifies whether to trust new TLS certificates by default. The default is "Yes". User name Specifies the default user name to use for requests. ValidateCerts Yes ValidateCerts No Specifies whether to only allow TLS with certificates whose common name matches the hostname. The default is "No". NOTES
The client.conf file is deprecated on macOS and will no longer be supported in a future version of CUPS. Configuration settings can instead be viewed or changed using the defaults(1) command: defaults write /Library/Preferences/org.cups.PrintingPrefs.plist Encryption Required defaults write /Library/Preferences/org.cups.PrintingPrefs.plist TrustOnFirstUse -bool NO defaults read /Library/Preferences/org.cups.PrintingPrefs.plist Encryption On Linux and other systems using GNU TLS, the /etc/cups/ssl/site.crl file, if present, provides a list of revoked X.509 certificates and is used when validating certificates. SEE ALSO
cups(1), default(1), CUPS Online Help (http://localhost:631/help) COPYRIGHT
Copyright (C) 2007-2017 by Apple Inc. 19 October 2017 CUPS client.conf(5)
All times are GMT -4. The time now is 04:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy