#Mitilena
In the Generate subproject we have added the ability to generate SegWit addresses for Bitcoin and also now private keys are available in two formats (in WIF [wallet import format] and regular).
In the Generate subproject we have added the ability to generate SegWit addresses for Bitcoin and also now private keys are available in two formats (in WIF [wallet import format] and regular).
Mitilena, Professional Crypto Wallet
#Mitilena In the Generate subproject we have added the ability to generate SegWit addresses for Bitcoin and also now private keys are available in two formats (in WIF [wallet import format] and regular).
For those who forgot or didn't know. Also for premium users all wallet data is duplicated in QR codes.
#Mitilena
We finally managed to convince Microsoft not to show a warning when running a wallet app on the Windows platform. It was a terrible experience, which shows how bad monopolism is.
We finally managed to convince Microsoft not to show a warning when running a wallet app on the Windows platform. It was a terrible experience, which shows how bad monopolism is.
#Mitilena
For premium users (those who bought the wallet) it is now available to generate private keys from their own passwords.
For example, you forgot your private key (or lost the paper with it), but remember your password, now if you enter your password when generating a private key you will always get the exact same private key and address.
This is an added convenience, but should be used with caution. Use only long passwords, otherwise someone will brute force the values and get your private key.
In the example in the screenshot, the password is ‘hello-world’ and the address received is bc1q8srpzjxwjnprexe3em87qesqqxxfel3xhafg4p3. Even after 10 years, if someone enters the password ‘hello-world’, he will again get the address bc1q8srpzjpzjxwjnprexe3em87qesqxxfel3xhafg4p3 and, accordingly, the private key for this address.
https://generate.mitilena.com
For premium users (those who bought the wallet) it is now available to generate private keys from their own passwords.
For example, you forgot your private key (or lost the paper with it), but remember your password, now if you enter your password when generating a private key you will always get the exact same private key and address.
This is an added convenience, but should be used with caution. Use only long passwords, otherwise someone will brute force the values and get your private key.
In the example in the screenshot, the password is ‘hello-world’ and the address received is bc1q8srpzjxwjnprexe3em87qesqqxxfel3xhafg4p3. Even after 10 years, if someone enters the password ‘hello-world’, he will again get the address bc1q8srpzjpzjxwjnprexe3em87qesqxxfel3xhafg4p3 and, accordingly, the private key for this address.
https://generate.mitilena.com
#security_on_the_network_is_never_existent
Microsoft has fixed a vulnerability for Windows that allowed any code to be executed on a victim's computer without the victim's knowledge. All versions with ipv6 enabled (which everyone has) since Windows Vista were vulnerable.
All a hacker had to do was simply send certain packets to the target computer and hack into it. The difficulty of using this hack was low.
In simple words: whatever antivirus you have had for the last 15 years, whatever the latest Windows updates have been installed. Anyone who knew about this hack could hack you remotely over the internet.
It's a fiasco.
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38063
Microsoft has fixed a vulnerability for Windows that allowed any code to be executed on a victim's computer without the victim's knowledge. All versions with ipv6 enabled (which everyone has) since Windows Vista were vulnerable.
All a hacker had to do was simply send certain packets to the target computer and hack into it. The difficulty of using this hack was low.
In simple words: whatever antivirus you have had for the last 15 years, whatever the latest Windows updates have been installed. Anyone who knew about this hack could hack you remotely over the internet.
It's a fiasco.
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38063
#Mitilena
For all coins on the Ethereum and Binance Smart Chain blockchain, rewriting a transaction stuck in Pending status is now available.
A small guide on how to do this is available by clicking on this link when sending a transaction.
For all coins on the Ethereum and Binance Smart Chain blockchain, rewriting a transaction stuck in Pending status is now available.
A small guide on how to do this is available by clicking on this link when sending a transaction.
#thoughts
When the blockchain first appeared, it copied data of itself to all nodes in the network. Each participant had its own copy of all transactions. This ensured data integrity. You can't fix in one place and cheat, you have to fix at each participant.
Some utopia that was shattered by trivial maths. Because each participant can't keep a copy of the blockchain if the blockchain is several years old (every citizen can't keep a state archive in his flat - it won't fit there).
Now the blockchain nodes of many blockchains are already cut down and do not contain all copies of the data (prune state). And networks are centralising.
Full copies of blockchains are now 8 terrabytes and growing every day. Servers with 8 terabytes of SSD storage are almost never widely available.
By default, the operating system does not support such drive sizes. Blockchain developers have not yet come up with mechanisms to split a folder with data into several discs.
And in principle, from what I have seen there are only two real blockchains: Bitcoin and Ethereum, the rest are copies of varying degrees of quality and variability.
The greedy desire of Ethereum and its forks (Binance Smart Chain, Matic Polygon, etc.) to take on board blockchains of any projects makes nodes up to 8 terrabytes split so quickly.
One could say that these blockchains are being devoured by their own greed.
Right now, a standard Ethereum "full" node cannot retrieve information about a transaction that is two years old. It is not stored there.
So it's a blockchain with truncated nodes.
In another 5 years, it will be like in a bank, when you go to a branch of the bank (as if it is a blockchain node), and they tell you that you have to go to the central branch with a statement (to address another blockchain node, which will occupy 70 terrabytes).
So, I predict the arrival of blockchains in which this problem would be solved.
When the blockchain first appeared, it copied data of itself to all nodes in the network. Each participant had its own copy of all transactions. This ensured data integrity. You can't fix in one place and cheat, you have to fix at each participant.
Some utopia that was shattered by trivial maths. Because each participant can't keep a copy of the blockchain if the blockchain is several years old (every citizen can't keep a state archive in his flat - it won't fit there).
Now the blockchain nodes of many blockchains are already cut down and do not contain all copies of the data (prune state). And networks are centralising.
Full copies of blockchains are now 8 terrabytes and growing every day. Servers with 8 terabytes of SSD storage are almost never widely available.
By default, the operating system does not support such drive sizes. Blockchain developers have not yet come up with mechanisms to split a folder with data into several discs.
And in principle, from what I have seen there are only two real blockchains: Bitcoin and Ethereum, the rest are copies of varying degrees of quality and variability.
The greedy desire of Ethereum and its forks (Binance Smart Chain, Matic Polygon, etc.) to take on board blockchains of any projects makes nodes up to 8 terrabytes split so quickly.
One could say that these blockchains are being devoured by their own greed.
Right now, a standard Ethereum "full" node cannot retrieve information about a transaction that is two years old. It is not stored there.
So it's a blockchain with truncated nodes.
In another 5 years, it will be like in a bank, when you go to a branch of the bank (as if it is a blockchain node), and they tell you that you have to go to the central branch with a statement (to address another blockchain node, which will occupy 70 terrabytes).
So, I predict the arrival of blockchains in which this problem would be solved.
#Mitilena
We are working on implementing offline signature directly into the main version of the wallet.
We are working on implementing offline signature directly into the main version of the wallet.
Mitilena, Professional Crypto Wallet
#Mitilena We are working on implementing offline signature directly into the main version of the wallet.
Therefore, errors may occur when signing a transaction.
#Mitilena
Due to cryptocurrencies ID change at our partner, some New addresses may have experienced sending issues. This has now been fixed.
Due to cryptocurrencies ID change at our partner, some New addresses may have experienced sending issues. This has now been fixed.
#Mitilena
Popular cryptocurrencies are now displayed with an asterisk icon to make users less confused.
Popular cryptocurrencies are now displayed with an asterisk icon to make users less confused.
#security
GitHub Enterprise have found a vulnerability that allows access to companies' account and private source code
‘In GitHub Enterprise Server instances using SAML SSO authentication with specific identity providers that apply publicly available signed federated XML metadata, an attacker could spoof a SAML response to grant or gain access to a user account with administrator privileges,’ GitHub reports.
https://www.cve.org/cverecord?id=CVE-2024-6800
GitHub Enterprise have found a vulnerability that allows access to companies' account and private source code
‘In GitHub Enterprise Server instances using SAML SSO authentication with specific identity providers that apply publicly available signed federated XML metadata, an attacker could spoof a SAML response to grant or gain access to a user account with administrator privileges,’ GitHub reports.
https://www.cve.org/cverecord?id=CVE-2024-6800
Mitilena, Professional Crypto Wallet
#security GitHub Enterprise have found a vulnerability that allows access to companies' account and private source code ‘In GitHub Enterprise Server instances using SAML SSO authentication with specific identity providers that apply publicly available signed…
I guess we'll have to leave the github. This is not the first serious vulnerability in the last few years.
The previous one was related to the fact that it was possible to access a project that had been renamed using an old URL. That was a major facepalm.
The previous one was related to the fact that it was possible to access a project that had been renamed using an old URL. That was a major facepalm.
#surveillance
In YouTube, bloggers are starting to spread information about the imminent fall of bitcoin and altcoins. This is usually seen before a global rise.
In YouTube, bloggers are starting to spread information about the imminent fall of bitcoin and altcoins. This is usually seen before a global rise.
#Mitilena
As part of a big update to the Mitilena Generate sub-project, we have implemented the ability to scan a private key as a QR code from paper or smartphone into the wallet.
As part of a big update to the Mitilena Generate sub-project, we have implemented the ability to scan a private key as a QR code from paper or smartphone into the wallet.
#Mitilena
New improvement:
At the stage of adding a new cryptocurrency address to the wallet, there is an option to scan it from a QR code.
New improvement:
At the stage of adding a new cryptocurrency address to the wallet, there is an option to scan it from a QR code.
#eth
789,533 ETH, once confiscated by the Chinese police, came into play. Possible sale on exchanges.
789,533 ETH, once confiscated by the Chinese police, came into play. Possible sale on exchanges.
While it's quiet in cryptocurrencies, let's see what's happening in the world of infosecurity:
In the US, the quick access system for pilots and flight attendants in airports and aircraft cockpits was hacked with a simple SQL injection.
‘Anyone with a basic knowledge of SQL injection could go to this site and add anyone they wanted to KCM and CASS, allowing them to both bypass security checks and gain access to the cockpits of commercial airliners,’ says the researcher.
The researcher emphasises that the vulnerability could have led to widespread security breaches, such as altering existing KCM member profiles, allowing any checks provided for new members to be circumvented.
However, after fixing the vulnerability, the U.S. Transportation Security Administration wrote a statement that there was no vulnerability. However, this statement contradicted the original statement by the U.S. Department of Homeland Security that the system was at risk and had been shut down.
In the US, the quick access system for pilots and flight attendants in airports and aircraft cockpits was hacked with a simple SQL injection.
‘Anyone with a basic knowledge of SQL injection could go to this site and add anyone they wanted to KCM and CASS, allowing them to both bypass security checks and gain access to the cockpits of commercial airliners,’ says the researcher.
The researcher emphasises that the vulnerability could have led to widespread security breaches, such as altering existing KCM member profiles, allowing any checks provided for new members to be circumvented.
However, after fixing the vulnerability, the U.S. Transportation Security Administration wrote a statement that there was no vulnerability. However, this statement contradicted the original statement by the U.S. Department of Homeland Security that the system was at risk and had been shut down.