home.social

#hifive — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #hifive, aggregated by home.social.

  1. Hi-Five's "I Like the Way (The Kissing Game)" hit number one on the Billboard Hot 100 on May 18, 1991.

    #Music, #HiFive, #90s, #90sMusic, #1990s, #1990sMusic

  2. Hi-Five's "I Like the Way (The Kissing Game)" hit number one on the Billboard Hot 100 on May 18, 1991.

    #Music, #HiFive, #90s, #90sMusic, #1990s, #1990sMusic

  3. Hi-Five's "I Like the Way (The Kissing Game)" hit number one on the Billboard Hot 100 on May 18, 1991.

    #Music, #HiFive, #90s, #90sMusic, #1990s, #1990sMusic

  4. Hi-Five's "I Like the Way (The Kissing Game)" hit number one on the Billboard Hot 100 on May 18, 1991.

    #Music, #HiFive, #90s, #90sMusic, #1990s, #1990sMusic

  5. Hi-Five's "I Like the Way (The Kissing Game)" hit number one on the Billboard Hot 100 on May 18, 1991.

    #Music, #HiFive, #90s, #90sMusic, #1990s, #1990sMusic

  6. We've updated our tor relay build script for #RISCV, building #openssl and #tor from source:

    code.disobey.net/EmeraldOnion/

    Notably, to get rid of this tor initialization warning:
    > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.

    With an added openssl configure target and option:
    > linux64-riscv64 enable-ec_nistp_64_gcc_128

    Our #SiFive #HiFive RISC-V 256-bits ECDH performance is synthetically boosted:

    From:
    > 256 bits ecdh (nistp256) 0.0029s 340.7

    To:
    > 256 bits ecdh (nistp256) 0.0005s 2057.1

    This is a 6x P-256 handshakes boost, so this should help speed up this Tor exit relay. We are only running one Tor daemon on this hardware to see how well it does.

  7. We've updated our tor relay build script for #RISCV, building #openssl and #tor from source:

    code.disobey.net/EmeraldOnion/

    Notably, to get rid of this tor initialization warning:
    > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.

    With an added openssl configure target and option:
    > linux64-riscv64 enable-ec_nistp_64_gcc_128

    Our #SiFive #HiFive RISC-V 256-bits ECDH performance is synthetically boosted:

    From:
    > 256 bits ecdh (nistp256) 0.0029s 340.7

    To:
    > 256 bits ecdh (nistp256) 0.0005s 2057.1

    This is a 6x P-256 handshakes boost, so this should help speed up this Tor exit relay. We are only running one Tor daemon on this hardware to see how well it does.

  8. We've updated our tor relay build script for #RISCV, building #openssl and #tor from source:

    code.disobey.net/EmeraldOnion/

    Notably, to get rid of this tor initialization warning:
    > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.

    With an added openssl configure target and option:
    > linux64-riscv64 enable-ec_nistp_64_gcc_128

    Our #SiFive #HiFive RISC-V 256-bits ECDH performance is synthetically boosted:

    From:
    > 256 bits ecdh (nistp256) 0.0029s 340.7

    To:
    > 256 bits ecdh (nistp256) 0.0005s 2057.1

    This is a 6x P-256 handshakes boost, so this should help speed up this Tor exit relay. We are only running one Tor daemon on this hardware to see how well it does.

  9. We've updated our tor relay build script for #RISCV, building #openssl and #tor from source:

    code.disobey.net/EmeraldOnion/

    Notably, to get rid of this tor initialization warning:
    > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.

    With an added openssl configure target and option:
    > linux64-riscv64 enable-ec_nistp_64_gcc_128

    Our #SiFive #HiFive RISC-V 256-bits ECDH performance is synthetically boosted:

    From:
    > 256 bits ecdh (nistp256) 0.0029s 340.7

    To:
    > 256 bits ecdh (nistp256) 0.0005s 2057.1

    This is a 6x P-256 handshakes boost, so this should help speed up this Tor exit relay. We are only running one Tor daemon on this hardware to see how well it does.

  10. We've updated our tor relay build script for #RISCV, building #openssl and #tor from source:

    code.disobey.net/EmeraldOnion/

    Notably, to get rid of this tor initialization warning:
    > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster.

    With an added openssl configure target and option:
    > linux64-riscv64 enable-ec_nistp_64_gcc_128

    Our #SiFive #HiFive RISC-V 256-bits ECDH performance is synthetically boosted:

    From:
    > 256 bits ecdh (nistp256) 0.0029s 340.7

    To:
    > 256 bits ecdh (nistp256) 0.0005s 2057.1

    This is a 6x P-256 handshakes boost, so this should help speed up this Tor exit relay. We are only running one Tor daemon on this hardware to see how well it does.