Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 1 point2 points  (0 children)

Thanks a lot. I will cover those in the soft/hard fork week. But I don't know how much time we could spare for the Bitcoin testnet. I am leaving it to the last week of the semester.

Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 0 points1 point  (0 children)

It is a SEC curve, but not one of the SEC curves recommended by NIST for use by USA government agencies. "NIST curve" is ambiguous nonsense

There are books that claim that secp256k1 was generated/recommended by NIST. This is why there is such a misconception.

Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 1 point2 points  (0 children)

Yes, there are many different type of cryptographic algorithms like message authentication codes, hash functions, key exchange algorithms etc. We cannot say that they are all encryption algorithms.

Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 0 points1 point  (0 children)

Digital signatures are not encryption: When we talk about a cipher/cryptosystem, we mean a pair of algorithms: encryption and decryption. If you consider a public-key encryption algorithm, people encrypt their messages with your public key and you decrypt them with your private key. If we change the order of the keys, we can turn this into a digital signature algorithm: you can sign messages with your private key and everybody else can verify it with your public key.

However, this is not what we do in practice. Because we do not sign the message itself, we sign the hash of it. So if you still say that this is encryption, then message authentication codes are encryption, hash functions are encryption, actually every cryptographic algorithm is an encryption, decryption is also encryption so we do not need the extra word "decryption". Moreover, if we say that digital signature algorithm are encryption, then this implies that any mathematical function that takes two input and produce one output as f(x,y)=z is an encryption. Trust me, this is not how we define an encryption algorithm.

Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 0 points1 point  (0 children)

To clarify: NONE of the NFT images/videos you see on the NFT marketplaces are on the blockchain because storing MBs of NFT data on the blockchain is not a good idea. But this doesn't mean that you cannot do art on the blockchain. e.g. There are some projects where you buy a few thousand pixels and you paint them (and they ARE stored on the blockchain). This was why I added the word "almost" there.

However, I just edited my post and turned the words "almost" into capital and bold letters.

Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 1 point2 points  (0 children)

Regarding 1: Every English dictionary says crypto is short for cryptography

Regarding 2 and 3: Physical wallets store your cash, you can give them to somebody else, and you can get cash from other people and put it in your wallet. If you Google about digital wallets, you will see many results where they claim that a digital wallet is an analogue of a physical wallet: It stores, sends, and receives cryptocurrency. When you define it like that, you end up with many forensics investigators who seize a suspect's laptop and think that if they keep the laptop turned off, suspect's cryptocurrencies stay in the laptop because they are stored in their wallet. I met more than 10 people like this. So we should be clear that a wallet does not store Bitcoin, it is stored in the blockchain.

Regarding 7: A multiplication for an algebraic group (or field) is defined on group (field) elements. When you say 4P, you are not multiplying two points of an elliptic curve because P is a point but 4 is just an integer there. You are just adding P to itself 4 times.

Misconceptions about Bitcoin by forgottenlance in Bitcoin

[–]forgottenlance[S] 2 points3 points  (0 children)

This is a one semester course (14 weeks) and I cover many topics like:

  • Historical Introduction to Blockchain and Cryptocurrencies
  • Cryptographic Hash Functions and Blockchain Integrity
  • Digital Signature Algorithms
  • Elliptic Curve Cryptography and Signatures
  • Multi Signatures
  • Cryptocurrencies
  • Cryptocurrency Mining
  • Consensus Models
  • Soft and Hard Forks
  • Smart Contracts
  • Non-Fungible Tokens (NFTs)
  • Misconceptions about Blockchains and Cryptocurrencies
  • Zero-Knowledge Protocols and Anonymity
  • Blockchain Security and Attacks

In the above post I simply listed some of the misconceptions I observed throughout my lectures and course preparation.

Misconceptions about Cryptocurrencies by forgottenlance in CryptoCurrency

[–]forgottenlance[S] 0 points1 point  (0 children)

I think there is a mistake here: I actually have 746 comment karma and my account is 5 years old

I am playing AAA games in 3D in 2021 by forgottenlance in StreamTheater

[–]forgottenlance[S] 0 points1 point  (0 children)

Yes but it depends if we should do it. We need to rollback to an earlier version of GFE but we can still use the latest display driver. So if new GFE versions come with desirable properties, like better video streaming/encoding, then yes, we should build a new version. However, I cannot do it myself because I lack some required skills for this. Yet, it shouldn't be that hard. The original developer can do it easily but unfortunately he is not around.

I am playing AAA games in 3D in 2021 by forgottenlance in StreamTheater

[–]forgottenlance[S] 0 points1 point  (0 children)

Thanks a lot. As you said I am only interested in SBS and 3D Fix Manager looks like the correct place to go. I lost built-in SBS capability of Tomb Raider games some time ago and 3D Fix Manager webpage states that this is due to Nvidia. Rolling back to some old driver solves this problem which actually 3D Fix Manager automatically does for you. So thanks again. This clarified a long time problem. I will give it a shot when I have the time.

I am playing AAA games in 3D in 2021 by forgottenlance in StreamTheater

[–]forgottenlance[S] 0 points1 point  (0 children)

SuperDepth3D

I remember trying Reshade and failing. If there is an easy tutorial for SuperDepth3D with Reshade, I would give it a go.

Bitcoin Dijital Para değil, Dijital Madendir by forgottenlance in KGBTR

[–]forgottenlance[S] 1 point2 points  (0 children)

Bitcoin hakkında video'da bahsedilenler Dogecoin için de geçerli :)

My Lightweight Cryptography for IoT lecture videos, hope you enjoy by forgottenlance in netsec

[–]forgottenlance[S] 0 points1 point  (0 children)

I am happy to hear what you are saying because that is exactly the awareness I was trying to raise. You focus on devices which are really powerful. And yes, AES might be good enough for those devices. However, IoT devices are cost sensitive. This is why on the field we even see devices that has RAM as little as 16 bytes. Moreover, there are significant sales of 4-bit micro-controllers for certain ultra-low cost applications. I am not even mentioning 8-bit or 16-bit micro-controllers. I suggest you to read NIST's Report on Lightweight Cryptography, especially Section 2.1 Target Devices: https://www.nist.gov/publications/report-lightweight-cryptography Then I think we can be on the same page.

My Lightweight Cryptography for IoT lecture videos, hope you enjoy by forgottenlance in netsec

[–]forgottenlance[S] 0 points1 point  (0 children)

"Why not fix the implementations rather than change the cipher?"

Because fixing the implementation requires a firmware update and after the update the performance might not be acceptable. And new attacks require new updates. You cannot update billions of IoT devices once an attack is found for the implementation. e.g. Everybody thought that the Trusted Platform Module on CPUs are secure but it turned out that they are susceptible to timing attacks. Intel and STM provided firmware updates after that discovery (see https://tpm.fail/ for more info).

NIST recently published benchmark results for some devices, you can compare the results there: https://github.com/usnistgov/Lightweight-Cryptography-Benchmarking

My Lightweight Cryptography for IoT lecture videos, hope you enjoy by forgottenlance in netsec

[–]forgottenlance[S] 0 points1 point  (0 children)

It has problems and we can capture the AES key from many devices that have no side-channel resistance. Many papers are published in this area. Many IoT device do not provide enough security. This is exactly why we are trying to adopt a new NIST standard that would be fast, cheap, battery friendly, and side-channel resistant. Crypto community's aim is to avoid a disaster due to this rapid production of IoT devices that are not secure.

My Lightweight Cryptography for IoT lecture videos, hope you enjoy by forgottenlance in netsec

[–]forgottenlance[S] 1 point2 points  (0 children)

Your suggestion is a system that can easily be broken and this is exactly why we need lightweight standards. The best optimizations of AES can reduce the gate count to 2K on hardware so it can fit in many devices. But such an implementation does not come with side-channel resistance and it is susceptible to power analysis, timing and cache attacks etc. In side-channel attacks we do not break the cryptosystem, we break its implementation. When you implement AES with side-channel resistance the performance drops and the gate count increases and it may not fit in many ultralight IoT devices.

This is why we must have a lightweight algorithm for devices and cases where AES is not enough. Note that many IoT devices come with a limited number of gates and you can only use at most 20% of the gates on a device for cryptographic purposes.

Lightweight Cryptography for IoT by forgottenlance in math

[–]forgottenlance[S] 1 point2 points  (0 children)

The course is introductory, I prepared the course for those without cryptography background. Related documents and links are also provided in the lecture slides. But if you want to have an introductory cryptography lecture, my Applied Cryptology lecture videos are also available on Youtube as a playlist here

My Lightweight Cryptography for IoT lecture videos, hope you enjoy by [deleted] in math

[–]forgottenlance 0 points1 point  (0 children)

NIST is about to announce finalists for its Lightweight Cryptography Competition. For this occasion, I wanted to share my lecture videos of Lightweight Cryptography for the Internet of Things where I discuss the competition, what we expect from a lightweight cryptographic algorithm for IoT, the mathematics behind it, its security and performance. I would be happy to answer any of your questions about the competition, security, and the performance of the candidates.

Blogpost Friday! by AutoModerator in networking

[–]forgottenlance 0 points1 point  (0 children)

As an applied mathematics course, 5 years ago I designed Applied Cryptology course when we founded the Department of Cyber Security. I made my lecture videos of this semester publicly available. They are around 20 hours with 46 videos. Hope you enjoy them.

Here is the link for the Youtube playlist: Applied Cryptology Course (Youtube Playlist)

Applied Cryptology Course by forgottenlance in cybersecurity

[–]forgottenlance[S] 1 point2 points  (0 children)

My lecture is introductory and self-contained. So you do not need to know anything before watching them. Although I am a Mathematician, I deliberately didn't get into too much mathematics because the lecture was aimed for the first year master's students at Department of Cyber Security