Help
RSS
API
Feed
Maltego
Contact
Domain > ewontfix.com
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2026-02-28
45.63.0.111
(
ClassC
)
Port 80
HTTP/1.1 200 OKDate: Sat, 10 Aug 2024 19:38:37 GMTAccept-Ranges: bytesCache-Control: privateContent-Security-Policy: default-src self; style-src self unsafe-inline;Server: tipidee/0.0.4.0Vary: Accept- html>head>title>EWONTFIX/title>link relalternate href/feed.rss typeapplication/rss+xml titleEWONTFIX RSS>link relshortcut icon href/favicon.ico typeimage/png>link relstylesheet href/main.css typetext/css>meta nameviewport contentwidthdevice-width, initial-scale1>/head>body>div classheader>h1>EWONTFIX/h1>ul classmenu>li>a href/>Home/a>li>a href/about>About/a>li>a href/feed.rss>RSS/a>/ul>/div>div classarticle>h2>a href19>The worst of time64 breakage/a>/h2>div classpub>15 Feb 2020 19:25:16 GMT/div>p>In preparing to release musl 1.2.0, I worked with distro maintainersfrom a hrefhttps://www.adelielinux.org/>Adélie Linux/a> anda hrefhttps://github.com/YoeDistro>Yoe/a> to find serious applicationcompatibility problems users would hit when upgrading, so that wecould have patches ready and reduce user frustration with the upgrade.Here are some of the findings./p>p>By far the most dangerous type of app compatibility issue we found wasin Berkeley DB 5.x, which defines its own wrong version of thecode>timespec/code> struct to pass to code>clock_gettime/code>:/p>pre>code>typedef struct { time_t tv_sec; /* seconds */#ifdef HAVE_MIXED_SIZE_ADDRESSING int32_t tv_nsec;#else long tv_nsec; /* nanoseconds */#endif} db_timespec;/code>/pre>p>The type of code>tv_sec/code> in their redefinition was right (code>time_t/code>), usingthe libc type for code>time_t/code>. However, the layout of the rest of thestruct failed to match. The libc code>timespec/code> struct is (prettified andremoving conditionals):/p>pre>code>struct timespec { time_t tv_sec; long tv_nsec; long :32;};/code>/pre>p>with the padding and code>tv_nsec/code> swapped for big-endian archs, so as toline up with the low bits of a 64-bit field. However the paddingmatters even on little-endian archs, since otherwise the structure maybe only 12 bytes long instead of 16 bytes (on archs that dont impose8-byte alignment). This includes i386, sh, or1k, m68k, and others. So,when Berkeley DB declared its own version without the padding, it
Port 443
HTTP/1.1 200 OKDate: Sat, 10 Aug 2024 19:38:38 GMTAccept-Ranges: bytesCache-Control: privateContent-Security-Policy: default-src self; style-src self unsafe-inline;Server: tipidee/0.0.4.0Vary: Accept- html>head>title>EWONTFIX/title>link relalternate href/feed.rss typeapplication/rss+xml titleEWONTFIX RSS>link relshortcut icon href/favicon.ico typeimage/png>link relstylesheet href/main.css typetext/css>meta nameviewport contentwidthdevice-width, initial-scale1>/head>body>div classheader>h1>EWONTFIX/h1>ul classmenu>li>a href/>Home/a>li>a href/about>About/a>li>a href/feed.rss>RSS/a>/ul>/div>div classarticle>h2>a href19>The worst of time64 breakage/a>/h2>div classpub>15 Feb 2020 19:25:16 GMT/div>p>In preparing to release musl 1.2.0, I worked with distro maintainersfrom a hrefhttps://www.adelielinux.org/>Adélie Linux/a> anda hrefhttps://github.com/YoeDistro>Yoe/a> to find serious applicationcompatibility problems users would hit when upgrading, so that wecould have patches ready and reduce user frustration with the upgrade.Here are some of the findings./p>p>By far the most dangerous type of app compatibility issue we found wasin Berkeley DB 5.x, which defines its own wrong version of thecode>timespec/code> struct to pass to code>clock_gettime/code>:/p>pre>code>typedef struct { time_t tv_sec; /* seconds */#ifdef HAVE_MIXED_SIZE_ADDRESSING int32_t tv_nsec;#else long tv_nsec; /* nanoseconds */#endif} db_timespec;/code>/pre>p>The type of code>tv_sec/code> in their redefinition was right (code>time_t/code>), usingthe libc type for code>time_t/code>. However, the layout of the rest of thestruct failed to match. The libc code>timespec/code> struct is (prettified andremoving conditionals):/p>pre>code>struct timespec { time_t tv_sec; long tv_nsec; long :32;};/code>/pre>p>with the padding and code>tv_nsec/code> swapped for big-endian archs, so as toline up with the low bits of a 64-bit field. However the paddingmatters even on little-endian archs, since otherwise the structure maybe only 12 bytes long instead of 16 bytes (on archs that dont impose8-byte alignment). This includes i386, sh, or1k, m68k, and others. So,when Berkeley DB declared its own version without the padding, it
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]