Glossary of Terms

Login

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

F

Facilities Planning

Facility Management

Facsimile Converter

Facsimile Recorder

Facsimile Transmission

Factor

Fail

Fail-Safe Operation

Failure

Failure Control

Fair Credit Billing Act of 1974 (amended 1986)

False acceptance rate (FAR)

False rejection rate (FRR[AuQ2][AuQ2])

Fan

Fandango On Core

FAQ

FAQL

FAR (false acceptance rate)

Farkled

Farming

Fault

Fault Tolerance

Faulty

FAX

FCA

Fd Leak

FDDI

FDDI-2

FDIU

FDM

Fear And Loathing

Feature

Feature Creature

FEC

Federal

Federal Computer Criminals

Federal Computer System

Federal Data Processing Centers

Federal Information Processing Standards

Federal Managers Financial Integrity Act

Federal Property And Administrative Service Act

Federal Property And Administrative Services Act Of 1949

Federal Records Act

Federal Register

Federal Telecommunications Fund

Federal Trade Commission (FTC)

Federal Wiretap Act

Feep

Feeper

Feeping Creature

Feeping Creaturism

Fence

Fencepost Error

FER

Fetch Protection

Fiber Distributed Data Interface

FidoNet

Field

Fielded Equipment

FIFO

File

File Authentication Code

File integrity checkers

File Management System

File Protection

File Transfer Protocol

File Transfer, Access, And Management

File-infector viruses

Fill

Filter

FIN

Final Evaluation Report

Financial Management Information

Financial Management System

Fine

Finger

Finger-Pointing Syndrome

Fingerprint recognition

Fingerprint Signal

Finn

FIPS

Fire Prevention And Protection

FIREFLY

Firehose Syndrome

Firewall appliances

Firewall architecture

Firewall Machine

Firmware Security

Firmy

First-In First-Out

FISA (Foreign Intelligence Surveillance Act)

FISINT

FITNR

Fix

Fixed COMSEC Facility

FIXME

Flag

Flaky

Flame

Flamer

Flap

Flat

Flatten

Flavor

Flaw

Flaw Hypothesis

Flaw Hypothesis Methodology

Flippy

Flood

Flooding DoS attacks

Flow Control Procedure

Flush

Flux

Flypage

Flytrap

FOAF

FOCI

FOI

FOIA

Follow-up report

Foonly

For Official Use Only (FOUO) Data

For The Rest Of Us

Fora

Foreign Government Information

Foreign Intelligence Service

Foreign Intelligence Surveillance Act (FISA)

Forked

Formal Access Approval

Formal Cryptographic Access (FCA)

Formal Development Methodology (FDM)

Formal Methods For Security Design

Formal Security Policy

Formal Security Policy Model

Formal Top-Level

Formal Top-Level Specification

Formal Verification

Format

Formerly Restricted Data

Fortuitous Conduction

Fortuitous Conductor

Forum

Forward Error Correction

Fossil

FOT&E

FOUO

Four-Color Glossies

Fourth Amendment

FQR

FQT

Fragile

Fragment offset

Frame

Fraud

Fraud, Waste And Abuse

FRD

Frednet

FreeBSD

Freedom Of Information Act

Freeze

Frequency Hopping

Frequency Of Major Failure

Fried

Frink

Friode

Frob

Front-End Processing

Front-End Processor

Front-End Security

Front-End Security Filter

Frotz

Frotzed

Frowney

FRR (false rejection rate)

Fry

FSD

FSRS

FSTS

FTAM

FTC (Federal Trade Commission)

FTLS

F-T-P

FTS

FUBAR

Fuel Up

Full Bit Emanation

Full Financial Disclosure

Full Maintenance

Full Monty, The

Full protocol decoding

Functional Testing

Funds

Funky

Fuzz

Fall Through

v. (n. `fallthrough', var. `fall-through') To exit a loop by exhaustion, i. e. , by having fulfilled its exit condition rather than via a break or exception condition that exits from the middle of it. This usage appears to be *really* old, dating from the 1940s and 1950s.
To fail a test that would have passed control to a subroutine or some other distant portion of code.
In C, `fall-through' occurs when the flow of execution in a switch statement reaches a `case' label other than by jumping there from the switch header, passing a point where one would normally expect to find a `break'. A trivial example switch (color) case GREEN do_green(); break; case PINK do_pink(); /* FALL THROUGH */ case RED do_red(); break; default do_blue(); break; The variant spelling `/* FALL THRU */' is also common. The effect of the above code is to `do_green()' when color is `GREEN', `do_red()' when color is `RED', `do_blue()' on any other color other than `PINK', and (and this is the important part) `do_pink()' *and then* `do_red()' when color is `PINK'. Fall-through is considered harmful by some, though there are contexts (such as the coding of state machines) in which it is natural; it is generally considered good practice to include a comment highlighting the fall-through where one would normally expect a break. See also Duff's device.