Me, myself & IT

Error

Contact and Feedback

Use the X.509 certificate to send S/MIME encrypted mail.

Note: email in weird format and without a proper sender name is likely to be discarded!

I dislike HTML (and even weirder formats too) in email, I prefer to receive plain text.
I also expect to see your full (real) name as sender, not your nickname.
I abhor top posts and expect inline quotes in replies.

Terms and Conditions

• The software and the documentation on this site are provided as is without any warranty, neither express nor implied.
  In no event will the author be held liable for any damage(s) arising from the use of the software or the documentation.
• Permission is granted to use the current version of the software and the current version of the documentation solely for personal private and non-commercial purposes.
  An individuals use of the software or the documentation in his or her capacity or function as an agent, (independent) contractor, employee, member or officer of a business, corporation or organisation (commercial or non-commercial) does not qualify as personal private and non-commercial purpose.
• Without written approval from the author the software or the documentation must not be used for a business, for commercial, corporate, governmental, military or organisational purposes of any kind, or in a commercial, corporate, governmental, military or organisational environment of any kind.
• Redistribution of the software and the documentation is allowed only in unmodified form of its current version and free of charge.

Notification and Disclosure Policy

• If you are a software developer or vendor but failed to provide an email address for reporting bugs, weaknesses and/or (security) vulnerabilities within your software and its documentation or failed to publish an email address on your web site I usually disclose the bugs, weaknesses and/or (security) vulnerabilities immediately.
• If the email address provided within your software and its documentation or published on your web site is invalid or reports sent to this mailbox bounce I usually disclose the bugs, weaknesses and/or (security) vulnerabilities immediately.
• If you receive a bug, weakness and/or (security) vulnerability report I expect at least an (immediate) acknowledgement of receipt and a qualified reply in the course of one week.
• If you don’t acknowledge the receipt or don’t reply within one week I usually resend the notification once, eventually with Cc: to CERT/CC.
• If you again don’t acknowledge the receipt or don’t reply within another week I usually disclose the bugs, weaknesses and/or (security) vulnerabilities then without further notice.
• If you consider a bug, weakness and/or (security) vulnerability I reported to you not as (security) vulnerability I usually disclose it immediately.
• If you decline to fix a bug, weakness and/or (security) vulnerability I reported to you I usually disclose it immediately.
• I expect that you assign or request a CVE^® identifier for every security vulnerability I report to you and notify me when done.
• I usually set a disclosure date 45 days after the initial bug, weakness and/or (security) vulnerability report.
• If you can’t meet this initial deadline and need more time to provide a fix or inform your customers I will grant an extension of the initial deadline if you provide convincing arguments to me.
• If the set deadline expires I usually disclose the bugs, weaknesses and/or (security) vulnerabilities then without further notice.
• I expect regular progress and/or status updates every other week, especially if you can’t meet the (initial or extended) deadline.
• If you don’t send progress and/or status updates on your own I will eventually request them from you.
• If you don’t reply to a progress and/or status update request within one week I usually disclose the bugs, weaknesses and/or (security) vulnerabilities then without further notice.
• I usually disclose the bugs, weaknesses and/or (security) vulnerabilities once you provide a fix or publish a (security) advisory or bulletin.

Data Protection Declaration

The web service is operated and provided by

The web service provider stores a session cookie in the web browser and records every visit of this web site with the following data in an access log on their server(s):

• the (pseudonymised) IP address;
• the date and time of the request;
• the URL of the requested web page or file;
• the Referer and User-Agent HTTP headers sent by the web browser;
• the result (success or failure) of the request;
• the amount of data received and sent.