Roundtable March 2017

roundtable@muug.ca

10 participants
9 discussions

Ryzen is here
by Trevor Cordes 23 Mar '17

23 Mar '17

My suppliers just informed me the new AMD Ryzen stuff is in stock. I'm doing quick glances at the choices now. First impressions: 1. Ryzen 7-series CPUs aren't cheap! Prices I am seeing will be just a bit below $500 to $700, though these may not represent all the models. That means cost savings over Xeon might not be substantial (or existent) at the low/mid-end. 2. ECC/board weirdness: I'm already confused, the high-end Asus X370 board doesn't support ECC but the B350 at half the … [View More]

1 0

Winkler Linux User Group
by John Funk 21 Mar '17

21 Mar '17

Winkler Linux User Group Tomorrow Tuesday 2017-03-21 we will be meeting at 7:15 at the Winkler branch of South Central Regional Library. Please let anyone you know who might interested.The topic for the next meeting will be discussing security concerns and permissions with file servers. This will not be a heavy discussion.

1 0

GnuCash crash on secret payload in XML file
by Hartmut W Sager 15 Mar '17

15 Mar '17

OK, it's late at night, and I did something that Trevor likes doing. :) I went looking for trouble. But hey, I had a good reason, and had been planning this experiment for weeks already. My current accounting is still my own FoxPro concoction (started in 1992 and updated a few hundred times), and for the last few years I knew I would have to move it. Besides export/import issues, I have several extra fields of information that I need to preserve (even if not accessible outside of raw XML … [View More]

4 11

Suggestion For Improvements To Cryptographic Hashing
by Ihor Jakowec 14 Mar '17

14 Mar '17

I hope this is readable, if not please notify me. This article is also readable from google+ Keywords: Ihor Jakowec DEJA VU HASH Revised Or, copy and paste, the below link... https://drive.google.com/open?id=0BxLingfkcfkbQ3JwYUlZVVBGZGc DEJA VU HASH Abstract Described here is a self modifying cryptographic hash, that changes with every login, and/or, after an arbitrary time interval. In addition to a password, the hash uses login statistics. A hacker would would … [View More]have less time to crack a password, because the hash value could keep changing. Also, hacker would need login statistics.  TIME SENSITIVE CRYPTOGRAPHIC HASH This method is used for remote logins from computers with an operating system containing log files that hold login data and network traffic data. This method is NOT for use by “dumb” terminals, or on guest computers where data is erased upon logout. The input to the hash consists of some or all of the following: 1.) Password. 2.) Time delay, established by use either/or: - the mode and variance of several ping attempts - a truncated value common to most ping trials - or the intersection algorithm. [1] 3.) Login time. 4.) Previous or, current login duration. 5.) CPU serial number. 6.) An array that is a histogram of values of the number of packets sent and received (the interval size is arbitrary) [1] _________________ Wikipedia Contributors “Intersection Algorithm” “Wikipedia, The Free Encyclopedia” Wikipedia, The Free Encyclopedia 5 May 2014. Web. 5 May 2014. NOTE: You could use NTP (Network Time Protocol), with peer-to-peer connectivity for both the login client and the server; to increase the resolution of the above items: 2, 3, and 4. (Referring to item 4.) If the current login is used, the hash is performed at the end of the login. A different hash value can be kept for each login from a different CPU. (This could be a weakness if many different CPU’s have been used, and infrequently at that.) Therefore, using item 5. should only be considered as an option, for those who want to restrict logins to a select few computers. How these values are arranged as input to the hash is arbitrary. You could use sequential concatenation. Or, values can be hashed separately, then xored to the final hash value. Input values can also be bit shuffled. Modification: Item 6 could consist of a single array that is a histogram of differences: (number of data packets sent - number of data packets received) The arbitrary time interval is: login duration / inter login interval Both the server and the client would have records of items 1 to 6 on their respective file systems. However, for concealment, the way they are stored, and used as input to the hash can vary. Since, this method results in a different hash for every login. A hacker’s cracking time would be limited to the time interval between successive logins PSEUDO LOGIN The concept here is to use pseudo logins. This is not a full login. Only the login state tables are synchronized and the password hash value is re-hashed. The login interval can be based on information known to both the client and the server. The average of the last five logins could be used, where a fraction, or multiple, of this average is used as the pseudo login interval. Moreover, the pseudo login interval can be vary. This interval can be made slightly longer or shorter. This variation can be based on the histogram of differences previously mentioned. The histogram can be partitioned into percentiles, or an arbitrary n-tile. Lower than average values can be used to shrink the pseudo login interval, while higher than average values can be used to lengthen the interval. Optimally, the average of these intervals should be slightly shorter than the amount of time needed by the average hacker to crack a hash value. Or, it could be left up to the system adminstrator to set the length of the pseudo login interval. This would depend on the need for security in juxtaposition to system load demands. SALTING THE SALT As an added security feature, each pseudo login hash can be salted with a random number. The same value that is used by the server and the remote login. The random number generator and the seed value used, would be common to the server and the login client. The type of random number generator used would be quasi-propriatary to the system being used. That is, each random value could be cryptographically hashed with a common seed value. The resulting hash value could be used with the hash value of the previous login or previous pseudo login hash value. ================================================== DISCLAIMER Any words not defined, in this collection of documents; use the definition given to them, by the O.E.D. and/or American Webster's dictionary. It is not my intention to use double entendre: either from English or in any other language, or from pop subculture (past or present). Any words redefined by me, or phrases defined by me, are simply technical in nature. They are not intended to refer to any: group, institution, organization, person or persons. — No alternate meaning to any word or phrase is implied or intended. — My intent is NOT to: slight, insult, affront, or offend. Ihor Jakowec Tuesday 14 December 2017 =================================================== [View Less]

1 0

Re: [RndTbl] GnuCash crash on secret payload in XML file
by Dan Martin 13 Mar '17

13 Mar '17

I have used GnuCash for many years, building up huge XML files, and never had an issue until I tried some auto-entry with a program. If the file is not EXACTLY what it expects, it will fail. No problem getting data out, though it can be processor intensive to rebuild the trees. But I have not had the patience to dig into source code to be able to write to it. It would be nice to have a high level API to allow auto entry, modify reports, etc. -Dan On Mon, Mar 13, 2017 at 3:04 AM, Hartmut W … [View More]

1 0

Les.net MUUG member discount slow in coming
by Hartmut W Sager 13 Mar '17

13 Mar '17

Sorry Les, no offense intended, but 4.5 months since the first promise is a bit long, and I did ask your staff about this a while back. The facts: 1. In the Nov 2016 MUUG Newsletter, Les.net offered a 10% discount to MUUG members. 2. My inquiry about this at Les.net a few weeks later led to a pleasant conversation with Sonja, who assured me that it would be implemented "pretty soon", and that discounting would definitely be back-dated to 01 Nov 2016. So, Les, will you kindly carry through … [View More]

1 1

Looking for Proxmox support
by Gerald Brandt 10 Mar '17

10 Mar '17

Hi, I used to do consulting (about a year ago). When I stopped, I told my clients, and all was well. Well, I have an old client that called me up. He had serious issues and didn't know why. I solved the issues for him, but we are now looking for someone to move forward to continue support. The client is relatively low maintenance, but when he needs help, he needs it immediately. The configuration is 4 Proxmox 4.4 servers and two Synologys in HA configuration serving vm images under … [View More]

1 0

MUUG Meeting, Mar 14, 7:30pm -- Pi-hole and Shred
by Gilbert E. Detillieux 07 Mar '17

07 Mar '17

*** Please note the updated meeting location below *** The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting on Tuesday, March 14 (Pi Day). The meeting topic for this month is as follows: Daemon-Dash: Pi-hole Pi-hole turns your Raspberri Pi (or other supported devices) into a network-wide ad blocker, using DNS redirection. It promises to block over 100,000 ad-serving domains, improve overall network performance and reduce cellular data usage, on … [View More]

1 0

new ECC computer options
by Trevor Cordes 04 Mar '17

04 Mar '17

I'm looking for input from anyone in the club who may be knowledgable, eyeballing, or has purchased a "workstation" system recently with ECC memory. (Note, ECC is imperative!) I don't need dual-socket, crazy speed, just something like a mid-range modern i7 with modern RAM, slots, etc. (i3 speeds won't cut it.) By "workstation" I mean it has to have at least one PCIe x16 (full 16 electrical) slot so it can have a good video card installed (and handle upgrades in the future). So some "… [View More]

3 11

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Roundtable March 2017