Skip to content

Main content

Random Nonzero Padding Byte Block

Replay seed or one advancing injected source, uniform over the explicitly stated finite support, not cryptographically secure. Generate independent uniform nonzero octets in 1..255 for a bounded padding test block; not a security protocol or cryptographic padding guarantee.

Loading tool…

Description

Generate independent uniform nonzero octets in 1..255 for a bounded padding test block; not a security protocol or cryptographic padding guarantee.

A random construction is defined by its sampling support: positions, permutations, complete tilings, proposal sequences or another explicit set. Uniform choices at one stage do not necessarily make final visible outcomes uniform. A replay seed gives a deterministic sequence; equal values can hide different sampled positions. These tools are for reproducible synthetic examples rather than cryptographic entropy.

Generate independent uniform nonzero octets in 1..255 for a bounded padding test block; not a security protocol or cryptographic padding guarantee.

When to use this tool

Use this tool to generate independent uniform nonzero octets in 1..255 for a bounded padding test block; not a security protocol or cryptographic padding guarantee.

How to use the tool and how it works

  1. Enter count, seed using the definitions below.
  2. Run the operation. Resolve input-format errors before interpreting an output.
  3. Read result.seed, result.bytes, using the stated boundary, ordering, sign and absence conventions.

Draw count independent uniform integers from 1 through 255 and return them as a byte block; count is 1–128.1

Input fieldMeaning and unitsAccepted input
countPositive number of samples/items to request, within the generator’s eligible-support bounds.Finite safe integer satisfying the stated bounds.
seedNonblank replay seed, at most 256 UTF-16 code units; an injected source overrides seeded draws.Text, at most 8,192 UTF-16 code units; narrower grammar/range rules also apply.
Output fieldInterpretation
resultObject containing the fields below.
result.seedOriginal supplied seed string; injected-source replay additionally requires that source’s state.
result.bytesGenerated/reordered byte values as integers 0–255, with narrower nonzero rules where stated.
json
{
  "input": {
    "count": 3,
    "seed": "batch56"
  },
  "output": {
    "result": {
      "seed": "batch56",
      "bytes": [
        163,
        252,
        252
      ]
    }
  }
}

Limitations and assumptions

  • The bytes deliberately exclude zero. This is synthetic padding data, not cryptographic padding or a secure entropy source.
  • A nonblank seed of at most 256 UTF-16 code units is required. With ordinary use the seed initializes one deterministic advancing source; an application-injected random source takes precedence and the seed alone then cannot replay the result. Uniformity statements assume independent uniform source draws in [0,1). Source calls are bounded and degenerate injected sources can fail a rejection budget. This is not cryptographically secure.
  • Every declared outer field is required and unknown outer fields are rejected. Strings and JSON text have size limits, lists are bounded to 128 entries, and JSON nesting/node counts are bounded. Tighter operation-specific bounds stated above take precedence.
  • Ordinary numeric outputs must be finite and within safe-integer magnitude. Exact large lengths/counts use decimal strings. Original record indexes and code-unit positions are zero-based; span ends are exclusive unless stated otherwise.

Alternative or Complementary methods

Choose a generator whose support matches the intended experiment and retain source-position provenance. Use a separate statistically justified process model or cryptographic source where those properties matter.

References

  1. Tool behavior and example: Random Nonzero Padding Byte Block — tool.io

Similar or alternative tools