Roundtable

roundtable@muug.ca

2555 discussions

Laptops
by Kevin McGregor 14 Apr '17

14 Apr '17

I'm thinking of getting a new laptop for general use. Does anyone have any opinions on what to get or stay away from? What am I thinking - opinions? This group?

7 8

MWLucas & "git commit murder"
by Adam Thompson 12 Apr '17

12 Apr '17

"If Agatha Christie ran Unix cons"... Many of you already know Michael W. Lucas as the author of such excellent tomes as PAM Mastery, Networking for Systems Administrators, SSH Mastery, Cisco Routers for the Desperate, Absolute FreeBSD and, of course, Absolute OpenBSD. You may not have been aware, however, that MWL also publishes fiction, some of which is tech-related, including his latest: "git commit murder". If you've ever been to a UNIX conference, the setting of the book will feel quite familiar; on the other hand, if you've never been, the book is actually a decent introduction to what attending BSDCan is like (just to pick a *completely random* typical conference, sure). Well, minus the actual murders, of course. (*fingers crossed*) In either case, it's a funny murder mystery set in the UNIX world. MWL's fiction is broadly available as eBook from Amazon, Kobo, Nook, iBooks, and as dead tree from at least some of those. (See http://mwl.io/ for the full list.) In other news, as usual, I'll take orders for Michael's books - if you want me to pick up a (typically signed) copy of something at BSDCan in June, let me know and I'll bring it back for you. (If it's something unusual, let me know well ahead of time so I can ask him to bring a copy.) -Adam

1 0

wayland has no support for --geometry
by Trevor Cordes 07 Apr '17

07 Apr '17

Ugh (rant time)... Wayland is sounding uglier with each passing day. Long may I postpone its existence on my boxen. Now I find out that by design(!!) wayland does not support any type of --geometry option for programmatically placing windows at certain locations on screen. For instance, I have a script that opens up about 20 windows in workspaces the way I like them sized/positioned, for use after I have to reboot. Saves me a ton of time as otherwise I have to position them by hand. https://bugzilla.redhat.com/show_bug.cgi?id=1404456 This is about the 10th "deal breaker" shortcoming of wayland that I've discovered. I was optimistic once... no longer. The more I read about wayland, the more it sounds like systemd in that it appears to be designed by Windows people, not UNIX people. And windows-are-always maximized people. And take 1 step forward, 5 steps back people (whereas true UNIXers always build on the past: IIABDFI). Here's praying that, as many X/wm devs have assured me, that X will be around for a long time, alongside wayland. I have a funny feeling Linus' personal workstation (not laptop) will NOT be running wayland!

2 1

Help with Kubuntu setup
by Kunzler, Siegfried 05 Apr '17

05 Apr '17

Hi, I am a new member again; I was a Member a long time ago and am wondering if someone would be able to help set up Kubuntu on my laptop. Many years ago (early 2000) I had Kubuntu running on my computer. But at one update I lost my printer setup and have not been able to get it working again. Also all the password requests that pop up have caused some confusion. At 66 it is becoming harder to follow all the changes and perhaps my Brother printer is to new to show driver on the Brother web site. Any help would be appreciated. Thank you, Siegfried Kunzler

2 1

MUUG Meeting, Apr 11, 7:30pm -- BTRFS and RTFM: man
by Gilbert E. Detillieux 04 Apr '17

04 Apr '17

*** Please note the updated meeting location below *** The Manitoba UNIX User Group (MUUG) will be holding its next monthly meeting on Tuesday, April 11. The meeting topic for this month is as follows: BTRFS Paul Sierks will present BTRFS, the B-Tree filesystem. BTRFS is a copy-on-write filesystem that brings a number of improvements over the typical journaled filesystem and adds features previously missing such as snapshots, checksumming and pooling. RTFM: man Brad Vokey will present man(1), the UNIX manual page viewer. Additionally Brad will show how to quickly create a basic man page on your own. The group usually holds its meetings at 7:30pm on the second Tuesday of every month from September to June. (There are no meetings in July and August.) Meetings are open to the general public; you don't have to be a MUUG member to attend. ****************************************************************** Please note our *NEW* meeting location for this month: *Room 1L11* Lockhart Hall, University of Winnipeg, entrance on Ellice Ave. between Spence St. and Balmoral St. Parking is available on the surrounding streets and in the lots on nearby streets. Look for signage once you're at the building, or ask a security guard. ****************************************************************** For more information about MUUG, and its monthly meetings, check out their web server: https://muug.ca/ Help us promote this month's meeting, by putting this poster up on your workplace bulletin board or other suitable public message board: https://muug.ca/meetings/MUUGmeeting.pdf -- Manitoba UNIX User Group E-mail: <gedetil(a)muug.ca> c/o Gilbert E. Detillieux Web: http://muug.ca/ University of Manitoba Phone: (204)474-8161 Winnipeg MB CANADA R3T 2N2 Fax: (204)474-7609

1 0

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 price does? That doesn't instill confidence. I'm doing more research and when I get some final comparisons down I'll post them here. Sadly, it looks like any way I do an upgrade it won't be cheap. Anyone else doing the same research (esp with regards to ECC) post your findings here!

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 editing), so I edited a good GnuCash native XML file by adding a secret payload in one existing transaction with <mynewtag>mypayload</mynewtag>, at the same level as the other fields of that transaction. I was hoping it would be ignored on load, and restored on save. The result: GnuCrash crashed totally while opening the edited XML file! Yeah, just crashed with a crash message and self-quit after that. Is GnuCash that unstable??? BTW, a simple raw XML edit of an existing text field of a transaction works fine, and is then shown in GnuCash when the file is opened. Hartmut W Sager - Tel +1-204-339-8331

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 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 ===================================================

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 Sager <hwsager(a)marityme.net> wrote: > 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 editing), so I edited a good GnuCash native XML file by adding a > secret payload in one existing transaction with > <mynewtag>mypayload</mynewtag>, at the same level as the other fields of > that transaction. I was hoping it would be ignored on load, and restored > on save. > > The result: GnuCrash crashed totally while opening the edited XML file! > Yeah, just crashed with a crash message and self-quit after that. Is > GnuCash that unstable??? > > BTW, a simple raw XML edit of an existing text field of a transaction > works fine, and is then shown in GnuCash when the file is opened. > > Hartmut W Sager - Tel +1-204-339-8331 <(204)%20339-8331> > > > _______________________________________________ > Roundtable mailing list > Roundtable(a)muug.ca > https://muug.ca/mailman/listinfo/roundtable > >

1 0

Jump to page:

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