PaX

joined 2 years ago
[–] [email protected] 31 points 7 months ago* (last edited 7 months ago) (1 children)

That's not a bit?? At least not completely?

walter-breakdown

Wtf

[–] [email protected] 10 points 7 months ago

Based cat with phone and neopronouns

meow-bounce

[–] [email protected] 4 points 7 months ago* (last edited 7 months ago)

text wall

Doug McIlroy can get a 1 out of /dev/zero.
Doug McIlroy can change file permissions using a magnet and a pin.
Doug McIlroy can read data from /dev/null.
Doug McIlroy can address 8 terabytes of RAM with only 32 bits.
Doug McIlroy can handle SIGKILL.
Doug McIlroy spawns Init.
Doug McIlroy can hard-link across devices.
Doug McIlroy can create 3-ended pipes.
Doug McIlroy dreams in binary.
Doug McIlroy eats serial ports for breakfast.
Doug McIlroy doesn't have an Erdos number; Erdos has a McIlroy number.
Doug McIlroy prototyped /dev/random with a toothpick and 4 cans of baked beans.
Doug McIlroy invented pipes.
Doug McIlroy invented diff to win a bet.
Doug McIlroy can read unbound variables.
Doug McIlroy can disprove tautologies.
Doug McIlroy's programs always terminate -- sometimes each other.
Doug McIlroy's programs don't need a garbage collector; they pick up their OWN garbage.
Doug McIlroy doesn't make system calls. System calls call Doug McIlroy.
Doug McIlroy doesn't use malloc to allocate memory. He uses his bare hands.
Doug McIlroy doesn't debug. He stares at tty0 until it fixes the problem.
Once, Doug McIlroy got mad at his terminal and smacked the keyboard. The result is called "Unix."
Alan Turing always wanted to win a McIlroy Award, but didn't qualify. No one has.
In 1984, the Department of Justice broke up AT&T because they had a monopoly. On Doug McIlroy.
Doug McIlroy supervises the hypervisor.
Doug McIlroy understands the internals of a hidden Markov model.
Doug McIlroy patented macros.
At Bell Labs, computers regularly crashed in fear when Doug McIlroy entered the room.

[–] [email protected] 6 points 7 months ago

It doesn't seem sooooo badd

Seems like all I really need is curl

What if I promise to use pledge(2) and unveil(2)?

[–] [email protected] 3 points 7 months ago (1 children)

Same :(

Let's make it a mutual disengage?

Hope you feel better soon

[–] [email protected] 4 points 7 months ago* (last edited 7 months ago) (3 children)

Greater rant: people who fucking care about opsec, this isn't an op and your sec is already compromised or meaningless if you think posting here is dangerous you're wrong

People have been doxxed and threatened with death over less sans-shrug

In this case, I just don't want to make it easier for Google to track anyone here when all it takes is deleting a few characters from a link

[–] [email protected] 10 points 7 months ago (2 children)

Bit idea: writing a lemmy bot in C

............. but what if it wasn't a bit?

[–] [email protected] 4 points 7 months ago* (last edited 7 months ago) (8 children)

It's still kinda there... I meant you should remove everything after the question mark, including the question mark, sorry

It's just concerning cuz Google uses this to group people together and find out where people are sharing their links

Maybe I should write a bot that points this out and prints the link without any tracking components

[–] [email protected] 4 points 7 months ago (10 children)

You don't see this on your end?

[–] [email protected] 6 points 7 months ago (12 children)

Can you take off the tracking part of the link? It's everything starting with "?"

[–] [email protected] 16 points 7 months ago (1 children)
 

Edit: the server is live at byond://157.230.217.31:9999 !

Brief instructions:

Get the BYOND client, make an account, and log in.

Click "Space Station 13" in the game list.

Click this gear icon in the top right of the window:

Click open location and paste in the link at the top of the post starting with "byond://" and press OK. Then you should connect!


Me and @[email protected] have been talking about running a Hexbear SS13 server for a bit and we just now got it in a working state for testing.

Around 4 PM US EST / 7 PM UTC I'll edit this post with the IP address so anyone who wants to play can join. It's okay if you haven't played before.

All you need to play is the BYOND client from here:

https://www.byond.com/

Come join us in running/blowing up our space station!

There may be a few technical problems we haven't foreseen yet but we'll deal with them if it happens.

Here is our Discord discussion group if you're interested:

https://discord.gg/Qcy6enC2h5

We are gonna replace it with something more secure and private sometime. Didn't we have a Matrix server once?

 

He called us very sweet and said our vegans are well-meaning but very aggressive

Hehehehe

That was a shock hearing Hexbear's name lmao

 

Me and @[email protected] were discussing practical aspects of hosting a Space Station 13 server. In particular, we were concerned about the risks of running internet services out of our home internet connections. It pretty much advertises the locality you live in and connects any other services/activity at the same IP address to your Hexbear identity. The usual alternative is to buy some server time from someone else with an internet connection but the costs can add up to a lot if everyone is buying server time individually for their services.

Initally, we were discussing buying some server time for our own use to proxy connections to our home network to run our game server but we thought it might be more efficient and helpful for the community to make this available to everyone here who wants to run an internet service.

Basically, the idea is that instead of exposing a service on your home IP address for everyone on the internet to see, you connect to our server and it accepts connections on its own IP address for you and proxies the traffic back to your home network. So, if you want to tell someone how to access your service, all you need to give them is our server's IP address and a port.

Of course, this has little to no effect on people with a grand ability to surveil internet traffic (fedposting) but it would expose a lot less information to other bad actors and make running internet services easier.

There would also need to be trust between the maintainers of this proxying service (who could collect the network information and traffic of the users, for example) and the users (who could use the proxy to forward malicious traffic, for example) so we thought it would be most useful if it were a community project. Maybe some of the risks could be minimized by restrictive firewall rules like not allowing users to send traffic out to the public internet unless it were a response to incoming traffic but maybe that is a feature we want?

Anyway, what does everyone think about this idea? Is it worth exploring and implementing or is it a bad idea? Sorry if I was a bit vague because I'm still thinking about the best way to implement this idea.

 

https://sovietmodernism.com/

"Hotel Cosmos"

"National Library of Kosova, Pristina"

"House of Unions, Minsk, Belarus"

"Ministry of Roads Building, Tbilisi, Georgia"

"Culture Palace of Railway Workers, Chisinau, Moldova"

 

On this day in 1983, a patent was granted to MIT for a new cryptographic algorithm: RSA. "RSA" stands for the names of its creators Rivest, Shamir, and Adlemen. RSA is a "public-key" cryptosystem. Prior to the creation of RSA, public-key cryptography was not in wide use.

Public-key cryptography

Cryptography is the study and practice of secure communication. Throughout most of its historical use, cryptographic techniques were entirely dependent on the involved parties already sharing a secret that could be used to reverse an encryption process. In early cryptography, the secret was itself the encryption process (for example, a Caesar cipher that substitutes letters in a secret message with letters a fixed number of steps down the alphabet). As cryptography became more systematic and widespread in use, it became necessary to separate cryptographic secrets from the cryptographic techniques themselves because the techniques could become known by the enemy (as well as static cryptographic schemes being more vulnerable to cryptanalysis). Regardless, there is still the issue of needing to share secrets between the communicating parties securely. This has taken many forms over the years, from word of mouth to systems of secure distribution of codebooks. But this kind of cryptography always requires an initial secure channel of communication to exchange secrets before an insecure channel can be made secure by the use of cryptography. And there is the risk of an enemy capturing keys and making the entire system worthless.

Only relatively recently has this fundamental problem been addressed in the form of public-key cryptography. In the late 20th century, it was proposed that a form of cryptography could exist where the 2 parties, seeking to communicate securely, could exchange some non-secret information (a "public" key) derived from privately held secret information (a "private" key), and use a mathematical function (a "trap-door" function) that is easy to compute in one direction (encryption) but hard to reverse without special information (decryption) to encipher messages to each other, using each other's respective public keys, that can't be easily decrypted without the corresponding private key. In other words, it should be easy to encipher messages to each other using a public key but hard to decrypt messages without the related private key. At the time this idea was proposed there was no known computationally-hard trap-door function that could make this possible in practice. Shortly after, several candidates and cryptosystems based upon them were described publicly 👁, including one that is still with us today...

RSA

Ron Rivest, Adi Shamir, and Leonard Adleman at MIT had made many attempts to find a suitably secure trap-door function for creating a public-key cryptosystem over a year leading up to the publication of their famous paper in 1978. Rivest and Shamir, the computer scientists of the group, would create a candidate trap-door function while Adleman, the mathematician, would try to find a way to easily reverse the function without any other information (like a public key). Supposedly, it took them 42 attempts before they created a promising new trap-door function.

As described in their 1978 paper "A method for obtaining digital signatures and public-key cryptosystems", RSA is based upon the principle that factoring very large numbers is computationally difficult (for now!). The paper is a great read, if you're interested in these topics. The impact of RSA can't be understated. The security of communications on the internet have been dependent on RSA and other public-key cryptosystems since the very beginning. If you check your browser's connection info right now, you'll see that the cryptographic signature attached to Hexbear's certificate is based on RSA! In the past, even the exchange of symmetric cipher keys between your web browser and the web server would have been conducted with RSA but there has been a move away from that to ensure the compromise of either side's RSA private keys would not compromise all communications that ever happened.

The future of RSA?

In 1994, a mathematician named Peter Shor, developed an algorithm for quantum computers that would be capable of factoring the large integers used in the RSA scheme. In spite of this, RSA has seen widespead and increasing use in securing communications on the internet. Until recently, the creation of a large enough quantum computer to run Shor's algorithm at sufficient scale was seen as very far off. With advances in practical quantum computers though, RSA is on its way out. Although current quantum computers are still a very long way off from being able to break RSA, it's looking more and more plausable that someone could eventually build one that is capable of cracking RSA. A competition being held by the US National Institute of Standards and Technology, similar to the one that selected the Advanced Encryption Algorithm, is already underway to select standard cryptographic algorithms that can survive attacks from quantum computers.

Megathreads and spaces to hang out:

reminders:

  • 💚 You nerds can join specific comms to see posts about all sorts of topics
  • 💙 Hexbear’s algorithm prioritizes comments over upbears
  • 💜 Sorting by new you nerd
  • 🌈 If you ever want to make your own megathread, you can reserve a spot here nerd
  • 🐶 Join the unofficial Hexbear-adjacent Mastodon instance toots.matapacos.dog

Links To Resources (Aid and Theory):

Aid:

Theory:

 

cross-posted from: https://hexbear.net/post/621898

In this photo, you can see how much the on-die cache has expanded compared to its predecessors and other contemporary embedded microprocessors. Really foreshadowing the kind of optimizations that would become commonplace today. In addition to its very large (for the time) 4-way set associative 256kb on-die secondary cache, it featured a 16k primary instruction cache and 16k primary data cache. It was fabricated at a 250 nanometer feature size and could be clocked up to 263 MHz. With its dual-issue superscalar 5-stage pipeline, it could achieve a Dhrystone score of 450 DMIPS at 263 MHz, a impressive score for embedded microprocessors of the time, although this benchmark really doesn't show off its cache performance.

Anyway, hope you like the pretty die shot of this forgotten microprocessor.

 

Inspired by this comment: https://hexbear.net/comment/3962687

Ideally this card should destroy itself when the conditions for the first effect no longer exist but I wasn't sure how to word that without making the language over-complicated or repeating myself.

The card art is AI-generated.

9
deleted by creator (hexbear.net)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 
1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

This is kinda an unorganized post, so sorry for that.

Recently, I've been thinking about creating a computer in the form factor of the "Handheld PCs" that were around during the 1990s. It's mainly just for me but I wouldn't mind selling a few to the small community of nerds who like those things. I'm trying to avoid making another PC or ARM device like someone would normally do just because I'm not really a fan of either of those architectures or the monopoly they represent.

I've been considering the MIPS-compatible X2000 from the Chinese semiconductor firm Ingenic but unfortunately that chip doesn't have an external memory controller so you're limited to just the 128M/256M of DRAM in the package which is less than ideal.

So, has anyone heard of any weird chips lately? Idk where else to ask. I don't know where people who make computers discuss things like this.

(Btw if you're interested in this topic you may enjoy www.greenarraychips.com. It's Charles H. Moore's outfit, the guy who invented Forth. They make cute little chips with many independent stack machines on them. Not useful for this project but still pretty cool. This is not an ad, I just like weird computers.)

view more: ‹ prev next ›