The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,262 other subscribers

Archive for November, 2017

« Previous Entries

The ##Netherlands saw a big I.T. project meant to deliver a new citizen regis…

Posted by jpluimers on 2017/11/30

Interesting: https://github.com/MinBZK/OperatieBRP

[WayBack] The Netherlands saw a big I.T. project meant to deliver a new citizen registry system fail. So they did one thing right. All the source code is now on github… – Jan Wildeboer – Google+

It includes both documentation and source code.

A bit of browsing reveals at least some of the technologies used:

Most of the SQL code seems to be generated.

There are truckloads of .XML configuration files, typical for a Java environment. Some configuration is in .properties files.

–jeroen

Posted in ActiveMQ, Development, Java, Java Platform, MQ Message Queueing/Queuing, Open Source, PostgreSQL, Software Development | Leave a Comment »

SuSEconfig is dead…

Posted by jpluimers on 2017/11/30

SuSEconfig has been dead for a while, but still indexed at quite a few of the official sites stressing the importance to use it.

It used to apply the configuration in /etc/sysconfig to the system.

The rationale for removal was simple:

Let’s remove all SuSEconfig scripts since only YaST calls SuSEconfig but other tools like rpm and zypper do not call it.

If scripts are needed, they need to be invoked as part of the postinstall.

Now most services either know to directly handle the configuration data there (and apply it during reload/restart/start of the service), or have a tool (like postfix now has /usr/sbin/config.postfix) to apply the settings.

–jeroen

References:

 

 

Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »

Getting rid of [dcc32 Warning] W1029 Duplicate constructor ‘ClassName.ConstructorName’ with identical parameters will be inacessible from C++

Posted by jpluimers on 2017/11/30

Note that the below solution works for any project raising the W1029 warning (not just from projects using Delphi Mocks) like

[dcc32 Warning] W1029 Duplicate constructor 'ClassName.ConstructorName' with identical parameters will be inacessible from C++

From my original text at [WayBack] Get rid of W1029 warning in Delphi compile mode · Issue #106 · VSoftTechnologies/Delphi-Mocks · GitHub:

By default the compiler will emit warnings like these for projects when using either of the Delphi.Mocks.Behavior or Delphi.Mocks.Expectation directly or indirectly:

[dcc32 Warning] W1029 Duplicate constructor 'TExpectation.CreateOnceWhen' with identical parameters will be inacessible from C++

They’re harmless as DUnitX doesn’t support C++. This particular warning type cannot be disabled on the unit or source line level which means you have to disable it on the project level by either:

  1. adding {$WARN DUPLICATE_CTOR_DTOR OFF} anywhere to your .dpr project file
  2. modifying the the Project Options for your project (easiest is in the All configurations - All platforms target):
    1. follow the path Delphi Compiler, Hints and Warnings in the treeview on the left
    2. expand the Output warnings node in the listview on the right
    3. set Duplicate constructor/destructor with identical parameters will be inacessible from C++ to Error

A screenshot of the second option is below.

Note that the spelling mistake in Duplicate constructor/destructor with identical parameters will be inacessible from C++ is how it is in the IDE, but that as Google search string it will give limited results, so here are some back-ground references:

Screenshot of the Project Options

Read the rest of this entry »

Posted in Delphi, Delphi 10 Seattle, Delphi 10.1 Berlin (BigBen), Delphi 2007, Delphi 2009, Delphi 2010, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Delphi XE6, Delphi XE7, Delphi XE8, Development, Software Development | Leave a Comment »

Objective-See: the Mac OS X / MacOS / Mac OS 10 root password issue tracked down

Posted by jpluimers on 2017/11/29

[WayBack] Objective-See: tracking down the cause a serious authentication flaw in Mac OS X / MacOS / Mac OS 10: resetting the root password by just clicking OK.

Via: [WayBack] How the MacOS High Sierra ##IAmRoot bug actually works. ##insightful … TL;DR the return value of the verify password function is interpreted wrong. Fix looks trivial. But this IS a serious bug. – Jan Wildeboer – Google+

Note the bug was already revealed two weeks ago: [WayBack] … after updating to High Sierra, the two admin accounts on this machine are all of a sudden standard accounts …

Via: [Archive.is] Mike Myers‏ @fristle: Perhaps nobody noticed two weeks ago when the root login vulnerability in macOS High Sierra was shared as a helpful tip on Apple’s own Developer forums. https://forums.developer.apple.com/thread/79235

The bug has already been fixed: [WayBack] About the security content of Security Update 2017-001 – Apple Support

Via: [WayBack] That was reasonably fast! ##Apple has released the fix for the embarrassing ##IAmRoot bug. https://support.apple.com/en-us/HT208315 – Jan Wildeboer – Google+

–jeroen

Read the rest of this entry »

Posted in Apple, Mac OS X / OS X / MacOS, macOS 10.12 Sierra, Power User | Leave a Comment »

QA frustrations: waiting  almost a year for a resolution

Posted by jpluimers on 2017/11/29

A frustrating part of reporting issues to many companies is the time it takes to get a response at all or a response “maybe in the far future”.

Below is just an example, but I see this regularly, for instance another example (scheduled in a later security related post) a company that responds to a “welcome in the 21st century” complaint on enforcing a 16 character password limit by responding “maybe we are going to extend it in the 22nd century”.

[WayBack] why are the parameters in a reverse order.

–jeroen

Posted in Development, Quality Assurance, Software Development | Leave a Comment »

« Previous Entries