tracker1

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

• lib/ is intended for code that can run as-is
• src/ is intended for code that needs to be manipulated before it can be used

tracker1

References on modern password policies

Below links provide source, reference link and relevant quote

Standards

NIST

https://github.com/usnistgov/800-63-3/blob/nist-pages/sp800-63b/sec5_authenticators.md

Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

Major organisations

tracker1

{
  "editor.rulers": [76, 80],
  "editor.formatOnSave": true,
  "editor.tabSize": 2,
  "files.associations": {
    "*.ssjs": "javascript",
    "*.msg": "plaintext",
    "*.ans": "plaintext",
    "*.asc": "plaintext",
    "*.rip": "plaintext",

tracker1

use std::io::{self, Read, Write};
use std::net::TcpStream;

fn get_remote_terminal_info(stream: &mut TcpStream) -> io::Result<(u16, u16, bool, bool, bool)> {
    // Send the control code to query the size of the terminal
    write!(stream, "\x1b[18t")?;
    stream.flush()?;
    // Read the response from the terminal
    let mut buf = [0u8; 32];
    let n = stream.read(&mut buf)?;

tracker1

  # after starting (docker-compose up -d)
# run docker-compose logs wireguard to view the qr-code for wireguard clients
version: "2.2"

# network required to specify ip for services
networks:
  vpnet:
    driver: bridge
    ipam:
      config:

tracker1

/*
/feature/load-component-import.js

This is used by any async loading areas of the application

import load from '../load-component-import.js';
const FooComponentAsync = load(() => import('./FooComponent'))';
*/

import React, { Suspense } from 'react';

tracker1

module.exports = () => {
  // break resolve and reject out of a promise
  let resolve, reject;
  const promise = new Promise((res, rej) => {
    resolve = res;
    reject = rej;
  });

  // return as a future
  return {

tracker1

import fclone from "fclone";

export enum LogLevel {
  Fatal = -1,
  Error = 0,
  Warn = 1,
  Info = 2,
  Debug = 3,
  Trace = 4,
}

tracker1

# RoughneckBBS Compose File
version: "3.3"
services:
  sbbs:
    container_name: sbbs
    image: bbsio/synchronet:nightly-20210314
    restart: always
    command: bash -c "sbbs-init && /sbbs/exec/sbbs w- s- m- f-"
    volumes:
      - $PWD/ctrl:/sbbs/ctrl

tracker1

import util from 'util';
import crypto from 'crypto';

const HASH_ALGO = 'sha512';

// nist recommends 10000, 10x nist, approx 83ms on i7-8650U
const HASH_ITERATIONS = 100000;

const HASH_SALT_BYTES = 16; // Exceeds NIST Minimum 32/8 (4 bytes)
const HASH_BYTES = 64; // Match Hash Algorithm lengh / bits (512 / 8);