Watcha doing?

[RabbiKnife]

Long day. Up at 0400hrs, at the church at 0430hrs, began smoking 6 pork butts for our Free Community Dinner by 0500hrs.

Just don’t inhale…

[Slug1]

Long day. Up at 0400hrs, at the church at 0430hrs, began smoking 6 pork butts for our Free Community Dinner by 0500hrs.

Just don’t inhale…

LOL!!

Got an email from the church this morning. A total of 103 people were served, 47 take out and 56 dine ins. It is always a blessing to see so many smiling faces.

[Cloudwalker]

Long day. Up at 0400hrs, at the church at 0430hrs, began smoking 6 pork butts for our Free Community Dinner by 0500hrs.

I only recognize 1 4 o'clock per day and it is NOT 4 AM.

[tango]

Quick run today. The cooler temperatures make it much easier, the difference in my pace for a comparable effort is remarkable. It's also nice to get home and not take half an hour or more to stop dripping sweat. This aftenoon I plan to play with some more boards, I'll get my circular saw up in the attic and cut some things to length. Hopefully I can fit all the rest of the boards in a single hit. That would be nice.

[tango]

Long day. Up at 0400hrs, at the church at 0430hrs, began smoking 6 pork butts for our Free Community Dinner by 0500hrs.

I only recognize 1 4 o'clock per day and it is NOT 4 AM.

I think 4am is a myth built into stories to scare small children into compliance.

[Slug1]

Long day. Up at 0400hrs, at the church at 0430hrs, began smoking 6 pork butts for our Free Community Dinner by 0500hrs.

I only recognize 1 4 o'clock per day and it is NOT 4 AM.

I think 4am is a myth built into stories to scare small children into compliance.

Hahaha, that's funny.

Second guessed myself today and lost a great photo.

Raining here today and rain makes great opportunity for interesting photos for my "Moment's Through a Dirty Windshield" photo project. Took several hipshots of people walking along the storefronts as I was slowly driving by. I decided to set my camera down and as I cleared past a parked car and looked off to the right, I lost a great photo.

A family was standing at the parking meter. The son, just a head taller than the meter and standing just to the left (my perspective), was look down at it. A daughter, was standing just to the right of the meter and was looking up at it. The mom, to the left of the son was looking at her husband/dad and he was to the right of the daughter and reaching over the daughter, was putting in the money with one hand and holding an umbrella with the other hand. They were all huddled under that umbrella.

Still mentally kicking myself for not waiting till I reached the end of the street before putting the camera down.

[Cloudwalker]

Not looking forward to Friday 8/30/2024.  Scheduled to have an endoscopy.  Probably will turn into an EGD, which will be my 11th.  The next day will not be pleasant.  I usually spend the next day sleeping and vomiting.  I suspect I'm sensitive to the anesthetic they were using.  I have mentioned that to several people.

[Slug1]

Not looking forward to Friday 8/30/2024.  Scheduled to have an endoscopy.  Probably will turn into an EGD, which will be my 11th.  The next day will not be pleasant.  I usually spend the next day sleeping and vomiting.  I suspect I'm sensitive to the anesthetic they were using.  I have mentioned that to several people.

Will start lifting this in prayer tonight brother. My wife and I pray together nightly and this will be on my list.

[Cloudwalker]

Not looking forward to Friday 8/30/2024.  Scheduled to have an endoscopy.  Probably will turn into an EGD, which will be my 11th.  The next day will not be pleasant.  I usually spend the next day sleeping and vomiting.  I suspect I'm sensitive to the anesthetic they were using.  I have mentioned that to several people.

Will start lifting this in prayer tonight brother. My wife and I pray together nightly and this will be on my list.

Thanks.  I'm not overly concerned.as.this will be my 11th.  Still, the usual aftermath is unpleasant.  The last few times left me sleeping and vomiting the next day.  The prayers are still appreciated.

[tango]

Not looking forward to Friday 8/30/2024.  Scheduled to have an endoscopy.  Probably will turn into an EGD, which will be my 11th.  The next day will not be pleasant.  I usually spend the next day sleeping and vomiting.  I suspect I'm sensitive to the anesthetic they were using.  I have mentioned that to several people.

Will start lifting this in prayer tonight brother. My wife and I pray together nightly and this will be on my list.

Thanks.  I'm not overly concerned.as.this will be my 11th.  Still, the usual aftermath is unpleasant.  The last few times left me sleeping and vomiting the next day.  The prayers are still appreciated.

Sounds ugly, even if it's a known ugly. I'll send one up for you as well

[tango]

Lots of fun with an encryption library I'm trying to figure out how to use. There's very little documentation and the sample code wouldn't compile. That's never a good start.

After much digging I found I was missing a key library. That seemed odd, given I used an automated installer. Further digging indicated I was using a "lite" version and what I had (what came with the installer built into my development platform) was out of date.

So all in all it took me the best part of 90 minutes to try and trace some documentation, fail to compile a simple demo program, figure out what the problem was, and get a very basic encryption implementation working. Now I need to build it into the rest of the code to make it do something more productive than turn text into gibberish and back into text.

[ProDeo]

@tango, I am still have the source code of an old encryption util from 1998.

Syntax : zipper e|d infile outfile

e=encrypt
d=decrypt

It compiles.

I can upload if you think it's useful.

[tango]

@tango, I am still have the source code of an old encryption util from 1998.

Syntax : zipper e|d infile outfile

e=encrypt
d=decrypt

It compiles.

I can upload if you think it's useful.

I wrote a basic encryption library myself probably around that time. I codenamed it EZ-Crypt and used it in a couple of applications. Now it would need to be rewritten to force it to use standard 8-bit characters, because with string types now referring to Unicode strings it sometimes glitches and messes up the last character or two during an encrypt-decrypt verification cycle. With so much else out there I don't know that I can be bothered to update it, it's less effort to just plug in an existing unit that works.

At present I'm trying to figure the best way to maintain a local user file for a piece of software that isn't allowed network access, and so can't use anything like enterprise-grade database security, nor can it use an online database. Because everything has to be stored locally there's nothing to stop anyone from inspecting the file so all the useful data needs to be encrypted, while keeping as many keys as possible unencrypted to allow the use of at least basic SQL statements.

For good measure it also needs to incorporate at least some protection against a bad actor using a different version of the file containing compromised passwords before restoring the current version.

[ProDeo]

A trick I used in the past, since folks tend to copy instead of buying, is to store crucial information (as copy protection) as a .dll in the Windows/system32 folder, encrypting the c:/Windows/system32 path and filename.dll in the code also. Everything can be hacked but it worked fine.

[tango]

A trick I used in the past, since folks tend to copy instead of buying, is to store crucial information (as copy protection) as a .dll in the Windows/system32 folder, encrypting the c:/Windows/system32 path and filename.dll in the code also. Everything can be hacked but it worked fine.

It's not about preventing people copying the software, that's secured with all sorts of fun other stuff (it's of limited use to copy the software anyway, since it interfaces with some very specialised hardware and is more or less useless without the hardware). The problem is that a bad actor could potentially tamper with the password file and create logs that appeared to be done by someone else. In most settings that wouldn't be an issue but this particular requirement relates to audit trails and being able to tell who did what. If the password file can be compromised there's the potential for audit trails to also become compromised, which is the problem.