Security Newsletter

Thread Tools Search this Thread
Special Forums Cybersecurity Security Newsletter
# 1  
Old 10-01-2001
Security Newsletter

Bruce Schneier has released a special edition of his monthly Crypto-Gram security newsletter. This issue discusses security & technology topics relating to the September 11th attack. It is not strictly Unix related, but I think it is well worth the read as it contains a lot of well-though out, interesting information.
Recommended reading for anyone interested in techology. (it is long: approx 18 pages)

Those of you in the US, if nothing else read the last section entitled "How to Help". A quote from the article:

"We have less than 100 hours before Congress acts on legislation that will (a) significantly expand the use of Carnivore, (b) make computer hacking a form of terrorism, (c) expand electronic surveillance in routine criminal investigations, and (d) reduce government accountability."

Check it out, and post your comments here.
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Newsletter email block.

I currently built a website and tested the newsletter with like 20 emails from the same provider ( since its the only provider i'm targeting with the newsletter. The automated message from the newsletter contains a link that usually blocks after a small period of time... (0 Replies)
Discussion started by: galford
0 Replies
Login or Register to Ask a Question
deallocate(1)															     deallocate(1)

deallocate - device deallocation SYNOPSIS
deallocate [-s] device deallocate [-s] [-F] device deallocate [-s] -I The deallocate utility deallocates a device allocated to the evoking user. device can be a device defined in device_allocate(4) or one of the device special files associated with the device. It resets the ownership and the permission on all device special files associated with device, disabling the user's access to that device. This option can be used by an authorized user to remove access to the device by another user. The required authorization is solaris.device.allocate. When deallocation or forced deallocation is performed, the appropriate device cleaning program is executed, based on the contents of device_allocate(4). These cleaning programs are normally stored in /etc/security/lib. The following options are supported: device Deallocate the device associated with the device special file specified by device. -s Silent. Suppresses any diagnostic output. -F device Forces deallocation of the device associated with the file specified by device. Only a user with the solaris.device.revoke authorization is permitted to use this option. -I Forces deallocation of all allocatable devices. Only a user with the solaris.device.revoke authorization is permitted to use this option. This option should only be used at system initialization. The following exit values are returned: non--zero An error occurred. /etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /etc/security/lib/* See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ allocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. 28 Mar 2005 deallocate(1)