We started producing shows as Today with a Techie on 2005-09-19, 13 years, 10 months, 11 days ago. Our shows are produced by listeners like you and can be on any topic that "are of interest to Hackers". If you listen to HPR then please consider contributing one show a year. If you record your show now it could be released in 8 days.
Please help out tagging older shows !
Before the days of the PC, application architectures were often very simple - being little more than the executable itself and any input files. The constraints of the early PC’s very limited resources required new architectures to make the most of those resources.
We now have a situation where most applications either install, or require the presence of, multiple runtime dependencies. Each dependency has an interface which allows communication between itself and the application, but every interface presents an attack surface with the potential to be exploited by a malicious 3rd party.
Modern computers do not have those same resource constraints yet we are still developing applications using the principles that applied 3 decades ago.
Re-usable functionality can be internalised through static linking at compile-time or by code inclusion (along the lines of a .h file in C/C++)
To change from using tried and tested methods is never convenient, but with concern for cyber security high and rising, has the time come to exchange convenience for simpler application architectures that should reduce vulnerabilities?
…And may a move to new (or is it old) architectures deliver a big win for open source software?
In this final episode of "Random Elements of Storytelling", Lostnbronx looks at the question of art vs. commerce.
When is a story a product? When is it a work of passion? Can it be both? In a era of interactive storytelling, what is the difference between a story teller and an audience? And where do art, commerce, creativity, and consumption intersect?
Lostnbronx wanders over hill and dale, and likely fails to adequately explain anything at all.
Hosted by Ahuka on 2019-07-19 is flagged as Clean and released under a CC-BY-SA license.
Tags: Encryption, Quantum Computing.
Listen in ogg, spx, or mp3 format.
Series: Privacy and Security | Comments (0)
The Quantum Computer is supposed to be a game changer that renders encryption useless. But is this true? We look at how quantum computing will affect encryption going forward, and show that we are already working on quantum-resistant encryption.
Welcome to the 7th Annual Hacker Public Radio New Years Show. 2018-2019
This episode is about modeling vehicle designer that can be used to design all kinds of vehicles available in the game. It relates to episode about performing research.
Two major parts about vehicle designer are components and chassis.
Components are modular pieces of vehicle that are assembled on chassis. They can, among other things, be things lie star sails, astrolabe navigators or long range sensor. Each component is defined by two values ComponentId and ComponentLevel. If you know these two values, you’ll be able to find out details of the component. ComponentId tells what component it is and ComponentLevel the general knowledge of it. When component is first discovered as a result of research, it’s just a prototype and as a such doesn’t function particularly well. Further research refines it and factories are able to produce higher quality components.
Full definition of component is show below:
data Component = Component
{ componentId :: ComponentId
, componentLevel :: ComponentLevel
, componentName :: ComponentName
, componentDescription :: ComponentDescription
, componentWeight :: Weight
, componentSlot :: ComponentSlot
, componentType :: [ ComponentPower ]
, componentCost :: RawResources ResourceCost
, componentChassisType :: ChassisType
}
deriving (Show, Read, Eq, Ord)Two particularly interesting fields are componentSlot and componentType. componentSlot has type of ComponentSlot and defines what kind of slot the component occupies in chassis. As there are limited amount of slots in each chassis, designer needs to make compromises on what components to install. componentType has type of ComponentPower, which defines what component does in general. It could be sensor or provide supplies for the vehicle for example.
Technology requirements are defined by function: componentRequirements :: ComponentId -> Maybe Technology. It defines which technology unlock a given component. Part of the definition is show below. Each and every ComponentId has to be handled.
componentRequirements ShipLongRangeSensors = Just HighSensitivitySensors
componentRequirements ShipBridge = Nothing
componentRequirements VehicleWheeledMotiveSystem = Nothing
componentRequirements VehicleHoverMotiveSystem = Just HoverCrafts
...Second major part of the designer are chassis. They’re stored in database, as I wanted a bit more flexible system than hardcoding as I did with components. Following piece of configuration is used to define database table and generated data for Haskell code. Most of the fields are probably easy enough to guess. type with type of ChassisType defines if this particular chassis is for example a land vehicle or a space ship. Various slot fields on other hand define amount of particular slots that the chassis offers.
Chassis json
name ChassisName
tonnage Weight
type ChassisType
technology Technology Maybe
armourSlots SlotAmount
innerSlots SlotAmount
outerSlots SlotAmount
sensorSlots SlotAmount
weaponSlots SlotAmount
engineSlots SlotAmount
motiveSlots SlotAmount
sailSlots SlotAmount
deriving Show Read EqNot all chassis are equal and some (probably pretty much every one of them) have some sort of requirements that has to be fulfilled when designing a vehicle. For example, space ships require a bridge for captain and star sails. Bawley, smallest of the working ships has room for two star sails, but requires only one of them to be installed in order to be a valid design. Flyboat on the other hand is smaller ship built for speed and always requires two set of sails.
This data is stored in required_component table and represented as RequiredComponent data. Both are generated from the definition show below:
RequiredComponent json
chassisId ChassisId
componentType ComponentType
level ComponentLevel
amount ComponentAmount
deriving Show Read EqWith all that data, we can now design a vehicle. Process is roughly the following:
Completed design is saved in two different tables. First one design holds info like name of the design, faction that design belongs to and used chassis. planned_component holds info about which components are planned to be installed and in what quantity.
Design json
name Text
ownerId FactionId
chassisId ChassisId
deriving Show Read Eqand
PlannedComponent json
designId DesignId
componentId ComponentId
level ComponentLevel
amount ComponentAmount
deriving Show Read EqAs a little teaser, below is an screenshot of what the vehicle designer currently looks like.
Thanks for interest. If you have questions or comments, best way to reach me nowadays is either by email or in fediverse, where I’m tuturto@mastodon.social.
Bitcorn is an idle farming game created with and played using Bitcoin tokens using the CounterParty protocol. I’ll walk you through how it all works, how to get started and what all that means.
In this episode we’ll walk through the basics of creating and submitting a Bitcorn collectible card to be included in the game, along with setting up a wallet so you can buy and sell them.
You can also use call forwarding to forward calls to your google voice number. Mint does not seem to stay connected all the time.
Welcome to the 7th Annual Hacker Public Radio New Years Show. 2018-2019
Get a full list of all our shows.