alexxandergrib / passwords-crypto

:lock: Password hashing and verification library providing single interface for SHA256, SCrypt, BCrypt, Argon2 and PBKDF2 algorithms

Hi, im Alexander 👋

Website • Telegram • Перейти на Русский 🇷🇺

Projects & Areas of Expertise

• 💳 Online Finance:
  • Created libraries for payment integrations: qiwi-sdk, yoomoney-sdk, tebex
  • Studied online card payment UX and created my card form
  • Reverse-engineered 3DSecure protocol
• 💻 Low-level:
  • Developed ARP Spoofer for GTA Online
  • Created Type-safe binary serializer
  • Written and benchmarked Q_rsqrt for Node
• 🤖 Bot development:
  • OpenCV image filter bot
  • Gambling bot
  • @guardcore_bot (closed source)
• 🌐 Web Dev:
  • dicraft.net (repo) - Minecraft server website
  • superellipse.xxhax.com - Tool to generate SVG rectangles with natural curves (Wikipedia)
  • ip.xxhax.com - IP Checking service

OpenSource Contributions

• Tinkoff/taiga-ui: Better BIN detection system
• JSMonk/sweet-monads: Identity monand + rust-like unwrap()
• negezor/vk-io: Better README.md design
• LayeredStudio/whoiser: Added Typescript typings

Github Stats

passwords-crypto's Issues

Crypt.verify outputting diagnostic information

I've noticed that when I call .verify() it actually prints some diagnostic information such as the name of the adapter being used as well as the hash itself.

Is this intended behaviour? I can't seem to find any sign that either my code or the .verify() implementations would output anything.

Apologies if this is a mistake on my end.

Here's the function that calls .verify():

async function loginUser(username: string, password: string) {
    let user = await User.findOne({$or:[{username: username}, {email: username}]});

    if (user === null) {
        throw new Error("Login failed: user not found")
    }

    // Validate password

    let isPasswordCorrect = await crypt.verify(user.password, password);

    if (!isPasswordCorrect) {
        throw new Error("Login failed: incorrect password")
    }
    return user;
}