Glossary

Filter:
# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z All
Return to List
U
U
U. S. Controlled Facility
U. S. -Controlled Facility
U. S. Controlled Space
U. S. -Controlled Space
U. S. Nongovernmental Source
U. S. Person
UA
UBD
UDP datagram
UDP port scanning
UID (User ID)
UIRK
UIS
UK
Umask
UN*X
Unapproved Software
Unauthorized Disclosure
Unauthorized Disclosure Of Information
Unauthorized Modification
Unauthorized User
Unavailability
Unbundling
Uncertainty Calculus
Unclassified
Unclassified Controlled Nuclear Information
Unclassified Information
Unclassified Telecommunications Security
Uncontrolled Access Area
Undefined External Reference
Under The Hood
Underlap
Undesired Signal Data Emanations
Undocumented Feature
UNICODE directory traversal attack
Uniform Encoding
Uniformed security personnel
Uninteresting
Unit Element
Unit Interval
UNIX
UNIX Brain Damage
UNIX Conspiracy
UNIX Weenie
UNIX:
Unixism
Unnecessary services
Unnumbered Command
Unnumbered Response
Unprivileged User
Unprotect
Unprotected
Unreliable
Unsuccessful Call
Unswizzle
Untrusted Applications
Untrusted Element
Untrusted network
Untrusted Process
Unwind The Stack
Unwind-Protect
Up
Up-Converter
Update
Updating
Upgrade
Upgrade Parameter
Uplink
Upload
UPP
Upthread
Uptime
Urchin
URL
URL filtering
Usable Line Length
Usage
Use policy
Useful Line
Usenet
User
User Datagram Protocol (UDP)
User ID
User ID (UID)
User Identification
User Information
User Information Bit
User Information Block
User Partnership Program
User Profile
User/process Interface
User-Obsequious
USG UNIX
Utility Program
Utility Routine
UTSL
UUCPNET
UV
Unixism
  • n. A piece of code or a coding technique that depends on the protected multi-tasking environment with relatively low process-spawn overhead that exists on virtual-memory UNIX systems. Common unixisms include gratuitous use of `fork(2)'; the assumption that certain undocumented but well-known features of UNIX libraries such as `stdio(3)' are supported elsewhere; reliance on obscure side-effects of system calls (use of `sleep(2)' with a 0 argument to clue the scheduler that you're willing to give up your time-slice, for example); the assumption that freshly allocated memory is zeroed; and the assumption that fragmentation problems won't arise from never `free()'ing memory. Compare vaxocentrism; see also New Jersey.